메뉴
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명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| 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.
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.