メニュー
Reconcile PRD requirements with a story-audit drift report. Use when marking PRD entries implemented/partial/missing, or promoting code-only stories into the PRD.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-story-reconcileコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
SKILL.md を表示中
SOC 職業分類に基づく
| created | "2026-04-25T00:00:00.000Z" |
| modified | "2026-07-05T00:00:00.000Z" |
| reviewed | "2026-04-25T00:00:00.000Z" |
| description | Reconcile PRD requirements with a story-audit drift report. Use when marking PRD entries implemented/partial/missing, or promoting code-only stories into the PRD. |
| args | [--audit <path>] [--prd <path>] [--apply-all] [--dry-run] |
| argument-hint | --audit docs/blueprint/audits/2026-04-25-story-audit.md (defaults to latest) |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion |
| model | opus |
| name | blueprint-story-reconcile |
Apply the drift findings from /blueprint:story-audit back to the PRDs. Adds status markers, a Known Drift section, and (with consent) promotes candidate stories. Does not delete unimplemented requirements — they remain the roadmap.
Usage: /blueprint:story-reconcile [--audit <path>] [--prd <path>] [--apply-all] [--dry-run]
| Use this skill when... | Use alternative when... |
|---|---|
| Marking PRD requirements as implemented / partial / missing after an audit | Producing the audit itself (/blueprint:story-audit) |
| Adding a "Known Drift" section to a PRD | Generating PRDs from scratch (/blueprint:derive-plans) |
| Promoting a single candidate story into the PRD with user consent | Bulk-rewriting PRDs (this skill is deliberately conservative) |
This skill only edits PRDs. Code changes belong to /blueprint:work-order. Audit re-runs belong to /blueprint:story-audit.
find . -path '*/docs/blueprint/audits/*' -maxdepth 4 -name '*-story-audit.md'find . -path '*/docs/prds' -maxdepth 2 -type dfind . -path '*/docs/prds/*' -maxdepth 3 -name '*.md'find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json'git branch --show-currentgit status --porcelain=v2 --branchParse $ARGUMENTS:
--audit <path>: Path to the audit artifact. Default: most-recent file matching docs/blueprint/audits/*-story-audit.md (sort lexically — date-stamped names sort correctly).--prd <path>: Limit edits to a single PRD. Default: every PRD referenced by the audit's drift table.--apply-all: Skip per-row prompts and apply every drift entry as an edit. Use only when the audit was reviewed elsewhere.--dry-run: Show the planned edits as unified diffs without writing.Before any closing AskUserQuestion menu, resolve the automation config:
bash "${CLAUDE_SKILL_DIR}/../../scripts/get-automation-config.sh"
When EFFECTIVE_INTERACTION_MODE=quiet and this invocation was
automation-initiated (autopilot, session bookend, drift-nudge follow-up — not
a slash command the user typed), skip closing navigation menus ("what next?" /
"create another?" style): apply the safe default and end with a one-line
receipt instead. Quiet mode never skips confirmation gates that guard writes —
only navigation menus. A direct user invocation always behaves fully
interactively (explicit intent overrides quiet; see ADR-0020).
Execute this PRD-reconciliation workflow.
--audit <path> provided, read that file.docs/blueprint/audits/*-story-audit.md, pick the lexicographically last one (date-stamped names sort correctly)./blueprint:story-audit first."Read the audit's Drift Report section (Section 4 in the canonical template). Extract every row into a structured list:
{ status: ✅|⚠️|❌|🆕, prd_ref: <id-or-null>, capability: <name>, evidence: <text> }
Skip ✅ implemented rows — they're informational; reconcile only adds value for ⚠️, ❌, and 🆕.
If the audit also has a Story Inventory → Candidate section, merge those rows into the 🆕 group with their entry-point evidence.
For each non-✅ drift entry, determine the target PRD:
| Status | Target PRD |
|---|---|
| ⚠️ partial / ❌ missing | The PRD whose prd_ref matches the entry (e.g. FR-2.3 → docs/prds/PRD-002.md) |
| 🆕 candidate | Ask the user which PRD to promote into; if no PRD covers the area, suggest creating a stub via /blueprint:derive-plans |
If --prd <path> is set, drop entries whose target PRD doesn't match.
For each target PRD, plan two kinds of edit:
A. Inline status markers for ⚠️ and ❌ entries — locate the line containing the requirement (search by prd_ref or substring of capability) and prepend the marker to the requirement line:
- FR-2.3 OCR support → server runs tesseract over uploads
becomes
- ❌ FR-2.3 OCR support → server runs tesseract over uploads (drift: dep declared but never imported)
B. A "Known Drift" appendix at the bottom of the PRD, in this exact format (idempotent — replace the section if it already exists):
## Known Drift
> Tracked by audit: `docs/blueprint/audits/<YYYY-MM-DD>-story-audit.md`
| Status | Requirement | Evidence | Action |
|--------|-------------|----------|--------|
| ❌ | FR-2.3 OCR support | dep `tesseract` declared but never imported | <work-order id or "open"> |
| ⚠️ | FR-1.4 deskew on import | implemented but only for landscape orientation | open |
For 🆕 candidate entries (Step 3 mapped them to a PRD): append a new requirement row at the end of the relevant FR section, with explicit text:
- FR-N.M (candidate, promoted from audit <YYYY-MM-DD>): <verbatim capability name>
Evidence: <entry-point file:line>
Do not renumber existing FRs — append at the end.
Skip this step when --apply-all is set.
For each PRD, show the planned edits as a unified diff and ask via AskUserQuestion:
If --dry-run is set, print the diffs and exit without prompting.
For each accepted edit, use the Edit tool to modify the PRD. Keep edits idempotent: re-running this skill against the same audit + same PRD must produce no further changes (the inline marker is already there; the Known Drift table already reflects the same rows).
After all PRD edits land:
git status --porcelain=v2 docs/prds/
If any non-PRD file shows up as modified → abort and report. This skill must only touch PRDs.
Update the task registry entry:
jq --arg now "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
--arg result "${RECONCILE_RESULT:-success}" \
--argjson edits "${EDITS_APPLIED:-0}" \
--argjson prds "${PRDS_TOUCHED:-0}" \
'.task_registry["story-reconcile"].last_completed_at = $now |
.task_registry["story-reconcile"].last_result = $result |
.task_registry["story-reconcile"].stats.runs_total = ((.task_registry["story-reconcile"].stats.runs_total // 0) + 1) |
.task_registry["story-reconcile"].stats.items_processed = $edits |
.task_registry["story-reconcile"].stats.prds_touched = $prds' \
docs/blueprint/manifest.json > docs/blueprint/manifest.json.tmp \
&& mv docs/blueprint/manifest.json.tmp docs/blueprint/manifest.json
Print the suggested commit message but do not commit automatically — the user owns the commit boundary:
docs(<scope>): reconcile PRD with story-audit <YYYY-MM-DD>
Refs docs/blueprint/audits/<YYYY-MM-DD>-story-audit.md
- Marked <N> drift entries (✅ <a> ⚠️ <b> ❌ <c>)
- Promoted <N> candidate stories
- Touched: <list of PRD paths>
Choose <scope> as the PRD prefix shared by edits (e.g. prd-001) or omit if multiple PRDs were touched.
Use AskUserQuestion to surface the obvious follow-on:
/blueprint:work-order per Tier-3 row (a user-invocable command — surface it for the user to run, don't invoke it via the Skill tool)/blueprint:story-audit| Off-limits | Why |
|---|---|
| Edit source code | Code changes go through /blueprint:work-order so the change has a TDD packet behind it |
| Delete unimplemented requirements | They are the roadmap. ❌ is a tracked status, not a delete signal. |
| Auto-create GitHub issues for drift | Audit + reconcile are local artifacts; issue filing is an explicit user action |
| Renumber FRs to "tidy up" | FR numbers are referenced from tests, commits, and other PRDs — renumbering is an unsafe, non-idempotent edit |
| Commit changes | Commit boundaries are the user's decision; this skill prints the suggested message and stops |
Re-running this skill against the same audit + same PRDs must be a no-op. The two mechanisms:
⚠️ , ❌ , 🆕 ) are detected before insertion. If the requirement line already starts with the right marker, skip.## Known Drift section is replaced wholesale by the new content, never appended.If a re-run produces changes, that is a bug — file it.
| Context | Command |
|---|---|
| Find latest audit | find docs/blueprint/audits -maxdepth 1 -name '*-story-audit.md' |
| Show audit drift section | awk '/^## 4\. Drift Report/,/^## 5\. /' <audit-path> |
| Detect existing Known Drift | grep -c '^## Known Drift' docs/prds/*.md |
| Locate FR by id | grep -n 'FR-2\.3' docs/prds/*.md |
| Count PRD files | find docs/prds -maxdepth 1 -name '*.md' |
| Verify only-PRDs touched | git status --porcelain=v2 docs/prds/ |
For drift-marker conventions, the full Known-Drift section format, and idempotency edge cases, see REFERENCE.md.