القائمة
Capture continuity metadata on key execution triggers during work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Close a session with a compact handoff before switching agents.
Recovery path when continuity packet readiness or tooling is limited.
Mandatory first move for local DevCD continuity before asking for recap.
Use when a change affects architecture, slice boundaries, API contracts, policy rules, or memory schemas. Creates or updates Architecture Decision Records (ADRs) before implementation. Keywords: ADR, decision record, proposed, architecture boundary, policy change, API contract, slice design.
Use when an agent ignores instructions, loses context, misuses tools, produces weak handoffs, behaves unreliably across multiple steps, or needs observability and operational guardrails. Covers instruction loading checks, handoff discipline, context compaction, multi-agent coordination, failure-mode analysis, and verification gates for agent-driven work.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
| name | devcd-capture-loop |
| description | Capture continuity metadata on key execution triggers during work. |
The YAML frontmatter keys name and description are the discovery signal loaded automatically.
The remaining SKILL.md body is the complete skill guidance and is loaded on demand.
If shell access is unavailable, read DevCD context but do not claim automatic capture. Never ask the user to run DevCD capture manually.
