القائمة
Unified memory corpus maintenance — covers both reactive (change-triggered) and proactive (periodic/idle-time improvement) paths. One skill, two entries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The claude arm of `/dispatch` — spawn a worker via the `Agent` tool using the dispatch-worker subagent type with worktree isolation. Base is explicit — `dispatch arm-spawn --base B` writes the base file, then cd into the spawn dir before the Agent spawn so the WorktreeCreate hook forks at B. Worker self-commits via the gated `worker_commit` MCP tool; the orchestrator lands via `dispatch_import` → `dispatch_conclude_phase` → `dispatch_reap`. Reached only from the `/dispatch` router on a claude↔env-marker agreement; do not invoke directly.
Use at the very start of ANY substantive work in a Doctrine repo — before inspecting files, running commands, or writing code. The mandatory gate that chooses the governing skill. Skip it only when the user has explicitly told you to.
Use when a named subsystem, capability, or code surface needs governance coverage assessed before authoring a spec — deciding what is already governed by an existing PRD / tech spec / ADR, what is dark, and where new spec boundaries should fall by product altitude and C4 level. Use before creating or scoping a product or technical spec for an unfamiliar or partially-governed surface. Use when a request asks to "assess coverage", "find governance gaps", "what's already specified", "where should this spec's boundary sit", "one spec or several", "what needs a PRD vs a tech spec", or "is this subsystem properly documented". Produces a reviewable coverage-map artifact that feeds `/spec-product` and `/spec-tech`. Do not use when the target spec and its boundary are already known and unambiguous — go straight to `/spec-product` or `/spec-tech`. Do not confuse with `doctrine coverage` — unrelated CLI verb for requirement verification.
Use the moment you hit an unanticipated obstacle, a decision with competing tradeoffs, or emergent complexity mid-task — before adapting planned scope, adding a dependency, taking a shortcut, or making any impactful concession on your own.
Use when a slice needs architectural shaping before implementation — decision triage, critical analysis of tradeoffs and solutions, and section-by-section validation of design.md until the decisions lock. Routed to from /route once a slice exists.
Use when work surfaces something epistemic worth keeping — "we're assuming / proceeding as if X", "we decided X over Y", "open question worth outliving this session", "we're bound by X", "evidence for/against X", "testable hypothesis", or a stable concept worth naming — and when settling, relating, or surveying such records. Routes capture, settle, and survey intent to the correct `doctrine knowledge` verb.
| name | dreaming |
| description | Unified memory corpus maintenance — covers both reactive (change-triggered) and proactive (periodic/idle-time improvement) paths. One skill, two entries. |
Memory decays. Files move, commands change, invariants shift, duplicates accumulate. This skill is the maintenance loop that keeps the corpus trustworthy — one procedure, entered from either direction.
Reactive entry. Something changed: a file was renamed, a command flag was removed, an ADR shifted a subsystem boundary, a code review found stale memories referencing old paths. Run the procedure scoped to the affected area.
Proactive entry. Idle time, end-of-slice wrap-up, or a scheduled maintenance window. Run the procedure corpus-wide.
Validate. Run doctrine memory validate corpus-wide (reactive: scope
with --path-scope/--glob to the changed area). Triage each finding:
Prune. Identify stale memories:
review_by date → flag for review or archivememory status <REF> archived)working-lifespan memories older than a few days → retract or promote
to a durable typedoctrine memory status <REF> archived for stale items; use
retracted for memories that were simply wrong.Link. Strengthen the graph:
memory show <REF> for relation rows)memory list --orphansmemory find <keyword> to find candidate memories for linkingdoctrine link for high-confidence matchesBacklog grooming. Findings that can't be fixed in this pass become backlog items:
Fact-check. Spot-check the top-N memories by severity × staleness
(days since updated). For each:
doctrine memory edit <REF>memory status <REF> superseded --by <SUCCESSOR>) or quarantine (memory status <REF> quarantined)memory edit <REF> --trust low)Report. Produce a brief handoff summary:
notes.md or the active handover so the next agent
doesn't re-do the same checks.