القائمة
Sync all relevant documents based on the active phase's history log. Activates when the user invokes /sync-docs or asks momentum to run the sync-docs recipe.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Begin a new implementation phase. Activates when the user invokes /start-phase or asks momentum to run the start-phase recipe.
Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.
Record a new backlog item (bug, feature, tech debt, or enhancement) when you discover work that needs tracking. Activates when the session identifies unplanned work that should be tracked in the backlog.
Check spec structure health of the momentum project. Activates when the user runs `/validate`, asks for a health check, or when spec changes need verification before phase completion.
>-
Drive a single repo through its phase as part of a swarm. Activates when spawned by the conductor (the user's primary session) with a spawn directive. State lives in files; the conductor reads board.json between turns. Loads on the swarm-supervisor invocation only — not invoked directly by the user.
استنادا إلى تصنيف SOC المهني
| name | sync-docs |
| description | Sync all relevant documents based on the active phase's history log. Activates when the user invokes /sync-docs or asks momentum to run the sync-docs recipe. |
Sync all relevant documents based on the active phase's history log. Token-efficient: reads history + 2 tiny indexes first, then only targeted files.
specs/status.md → identify active phasespecs/phases/<active-phase>/history.md → extract all entriesspecs/phases/index.json (~2KB)specs/decisions/impact-map.json (~3KB)For each history entry:
specs/architecture/
(constitution — never auto-synced, only amended via formal process)Affects-specs: path starting with ../ (or otherwise outside this repo),
add it to a separate "cross-repo" list. NEVER edit those files — you only
own this repo's docs.Present to user: "Based on phase history, I will check and potentially update:
If any cross-repo entries were partitioned out in Step 2: also show them
under a "Cross-repo impact (NOT touching — sync the other repo manually)"
heading, listing each Affects-specs: ../... path. Tell the user which repo
they need to edit and which entries pointed there. Do NOT prompt for approval
on cross-repo paths — they're informational only.
If user says no → stop.
For each file in the list:
For each file that needs updating:
If any [SCOPE_CHANGE] entries exist:
specs/phases/index.json for the active phase's topic listgit add <all modified spec files>
git commit -m "docs(phase-N): sync specs from phase history"
"Spec sync complete. Updated N files:
specs/architecture/ (monorepo only — constitution is read-only)../) — you only own this repo's docs. Flag cross-repo entries to the user instead.