finalize-spec-pm
Move a finalized spec's backlog cards to shipped through the pm-sync-core approval flow once its record is merged and main is green, or report that PM sync is pending when the product layer is not installed
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- finalize-spec-pm
- description
- Move a finalized spec's backlog cards to shipped through the pm-sync-core approval flow once its record is merged and main is green, or report that PM sync is pending when the product layer is not installed
- argument-hint
- <spec-name>
03 SKILL.md 正文
Finalize Spec — Backlog Sync
Step 6 of /finalize-spec. The backlog in product/ records what shipped. Agents never write it directly: pm-sync-core drafts the change and files it for a maintainer's signed approval.
Input
$ARGUMENTS: the spec name. The spec is in specs/done/ on origin/main, and /finalize-spec-verify-ci reported green.
Invocation contexts
- Slash command: invokes
pm-sync-coreand reports its lines, including the maintainer's approve commands. - Model-invoked: the same.
- Non-interactive: the same.
pm-sync-coreonly files approval requests, which need no pre-approval; the backlog itself changes only when a maintainer approves. This skill never waits for that approval.
Steps
- Is the product layer installed? In the main checkout,
test -f .claude/skills/pm-sync-core/SKILL.md && test -f scripts/pm/pm.py. When either is missing, reportPM sync: pending (pm-sync-core is not installed)and stop without error: the finalize is complete, and the card is synced when the layer lands. - Sync. Invoke
pm-sync-corewith the Skill tool,args="<spec> --to shipped". It finds the spec's cards, holds any card that names another unshipped spec atimplementingwith a half-shipped note, and files one approval request per changed product file. - Relay its report lines verbatim, and the request ids with the maintainer's commands. A
droppedcard, or any escalationpm-sync-coreraises, is reported as its own line and does not undo the finalize.
Output
pm-sync-core's lines (PM sync: MH-<n> → shipped (requests <ids>), ... skipped ..., ... held at implementing ...), or PM sync: skipped (no card names <spec>), or PM sync: pending (<reason>).
04 同仓库更多 Skills
mythhelm-deliver-backlog
Coordinate a MYTHHELM backlog run with the shared stage checks and maintainer checkpoints.
mythhelm-bootstrap
Orient a Grok Build session in the MYTHHELM repository before task or spec work.
vendor-consult
Run one advisory stage consult (premise-ground, spec-validate, task-review, change-review, stuck-oracle, dossier) with an optional external vendor, then adjudicate the answer at its anchors
update-docs
Bring README, docs/, knowledge/, WORKFLOW.md and CLAUDE.md in line with what a shipped spec or a merged change actually did — find every statement the change made stale, fix it where readers look, and add only the new facts they need
triage
Score an idea or a GitHub issue against the master spec's stages, gates and commitments, check it for duplicates, and recommend whether it becomes a backlog card; read-only
test-driven-development
Red-green-refactor for Go — use when implementing any feature, bug fix or behaviour change, before writing implementation code