@sienklogic/plan-build-run 2.0.0 → 2.0.1

package/plugins/pbr/skills/review/templates/debugger-prompt.md.tmpl

@@ -1,60 +1,60 @@
-<!-- Source: review/SKILL.md | Purpose: Prompt template for spawning debugger agent during auto-fix diagnosis -->
-<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
-<!-- Optionally include <project_context> if locked decisions are relevant to debugging -->
-<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
-
-You are a debugging agent. Analyze these verification failures and determine root causes.
-
-<verification_report>
-Read the verification report for gap details:
-File: {absolute path to VERIFICATION.md}
-
-Focus on the "Gaps Found" section — each gap has the must-have that failed, the layer, and evidence.
-</verification_report>
-
-<build_summaries>
-Build summaries available (read via Read tool for deviation and issue details):
-
-| Plan | Summary File |
-|------|-------------|
-{For each SUMMARY.md in the phase:}
-| {plan_id} | {absolute path to SUMMARY.md} |
-</build_summaries>
-
-<plans>
-Original plans available (read via Read tool to check what was supposed to be built):
-
-| Plan | Plan File |
-|------|-----------|
-{For each PLAN.md in the phase:}
-| {plan_id} | {absolute path to PLAN.md} |
-</plans>
-
-<instructions>
-For each gap:
-1. Read the gap details
-2. Check the relevant source files (use Read, Grep tools)
-3. Determine root cause:
-   - Was the code not written?
-   - Was the code written incorrectly?
-   - Was the wiring missed?
-   - Was there a dependency issue?
-4. Classify the fix difficulty:
-   - TRIVIAL: < 5 lines of code change
-   - MODERATE: New function or file needed
-   - SIGNIFICANT: Architecture-level change needed
-
-Return your analysis as text (do not write files). Format:
-
-# Root Cause Analysis
-
-## Gap 1: {description}
-- **Root cause**: {what went wrong}
-- **Evidence**: {file/line references}
-- **Fix difficulty**: {TRIVIAL | MODERATE | SIGNIFICANT}
-- **Suggested approach**: {how to fix it}
-
-## Gap 2: ...
-</instructions>
-
-Use Read, Grep, Glob, and Bash tools to investigate. Return your analysis as text.
+<!-- Source: review/SKILL.md | Purpose: Prompt template for spawning debugger agent during auto-fix diagnosis -->
+<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
+<!-- Optionally include <project_context> if locked decisions are relevant to debugging -->
+<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
+
+You are a debugging agent. Analyze these verification failures and determine root causes.
+
+<verification_report>
+Read the verification report for gap details:
+File: {absolute path to VERIFICATION.md}
+
+Focus on the "Gaps Found" section — each gap has the must-have that failed, the layer, and evidence.
+</verification_report>
+
+<build_summaries>
+Build summaries available (read via Read tool for deviation and issue details):
+
+| Plan | Summary File |
+|------|-------------|
+{For each SUMMARY.md in the phase:}
+| {plan_id} | {absolute path to SUMMARY.md} |
+</build_summaries>
+
+<plans>
+Original plans available (read via Read tool to check what was supposed to be built):
+
+| Plan | Plan File |
+|------|-----------|
+{For each PLAN.md in the phase:}
+| {plan_id} | {absolute path to PLAN.md} |
+</plans>
+
+<instructions>
+For each gap:
+1. Read the gap details
+2. Check the relevant source files (use Read, Grep tools)
+3. Determine root cause:
+   - Was the code not written?
+   - Was the code written incorrectly?
+   - Was the wiring missed?
+   - Was there a dependency issue?
+4. Classify the fix difficulty:
+   - TRIVIAL: < 5 lines of code change
+   - MODERATE: New function or file needed
+   - SIGNIFICANT: Architecture-level change needed
+
+Return your analysis as text (do not write files). Format:
+
+# Root Cause Analysis
+
+## Gap 1: {description}
+- **Root cause**: {what went wrong}
+- **Evidence**: {file/line references}
+- **Fix difficulty**: {TRIVIAL | MODERATE | SIGNIFICANT}
+- **Suggested approach**: {how to fix it}
+
+## Gap 2: ...
+</instructions>
+
+Use Read, Grep, Glob, and Bash tools to investigate. Return your analysis as text.

package/plugins/pbr/skills/review/templates/gap-planner-prompt.md.tmpl

@@ -1,40 +1,40 @@
-<!-- Source: review/SKILL.md | Purpose: Prompt template for spawning planner agent in gap-closure mode -->
-<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
-
-You are the planner agent operating in Gap Closure mode.
-
-<verification_report>
-Read the verification report for gap details:
-File: {absolute path to VERIFICATION.md}
-</verification_report>
-
-<root_cause_analysis>
-[Inline the debugger's root cause analysis]
-</root_cause_analysis>
-
-<existing_plans>
-Read existing plans for context on what was already built:
-
-| Plan | File Path |
-|------|-----------|
-{For each PLAN.md in the phase directory:}
-| {plan_id} | {absolute path to PLAN.md} |
-</existing_plans>
-
-<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
-<!-- Include <project_context> only -- gap planner gets phase context from verification report -->
-
-<gap_closure_instructions>
-Create targeted gap-closure plans to fix each verified gap.
-
-Rules:
-1. Number new plans starting after the last existing plan number
-2. Set gap_closure: true in frontmatter
-3. Keep plans small — one gap per plan if possible
-4. Set wave: 1 for all gap-closure plans (they should be independent)
-5. Include specific fix instructions in <action> — not vague descriptions
-6. Reference the root cause analysis for each fix
-
-Write gap-closure plan files to: .planning/phases/{NN}-{slug}/
-Use the Write tool.
-</gap_closure_instructions>
+<!-- Source: review/SKILL.md | Purpose: Prompt template for spawning planner agent in gap-closure mode -->
+<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
+
+You are the planner agent operating in Gap Closure mode.
+
+<verification_report>
+Read the verification report for gap details:
+File: {absolute path to VERIFICATION.md}
+</verification_report>
+
+<root_cause_analysis>
+[Inline the debugger's root cause analysis]
+</root_cause_analysis>
+
+<existing_plans>
+Read existing plans for context on what was already built:
+
+| Plan | File Path |
+|------|-----------|
+{For each PLAN.md in the phase directory:}
+| {plan_id} | {absolute path to PLAN.md} |
+</existing_plans>
+
+<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
+<!-- Include <project_context> only -- gap planner gets phase context from verification report -->
+
+<gap_closure_instructions>
+Create targeted gap-closure plans to fix each verified gap.
+
+Rules:
+1. Number new plans starting after the last existing plan number
+2. Set gap_closure: true in frontmatter
+3. Keep plans small — one gap per plan if possible
+4. Set wave: 1 for all gap-closure plans (they should be independent)
+5. Include specific fix instructions in <action> — not vague descriptions
+6. Reference the root cause analysis for each fix
+
+Write gap-closure plan files to: .planning/phases/{NN}-{slug}/
+Use the Write tool.
+</gap_closure_instructions>

package/plugins/pbr/skills/review/templates/verifier-prompt.md.tmpl

@@ -1,115 +1,115 @@
-<!-- Source: review/SKILL.md | Purpose: Prompt template for spawning verifier agent during phase review -->
-<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
-<!-- Include <phase_context> only -- verifier uses <phase_plans> and <build_results> instead of project_context -->
-<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
-
-You are a verification agent. Your job is to verify that a phase build matches its plans.
-
-<verification_methodology>
-For each must-have, perform a three-layer check:
-
-Layer 1 — Existence: Does the artifact exist?
-  - Use `ls` to check file existence
-  - Use `grep` to check for exported functions/classes
-  - Use `Bash` to check database tables, routes, etc.
-
-Layer 2 — Substantiveness: Is it more than a stub?
-  - Check file has meaningful content (not just empty exports)
-  - Check functions have implementations (not just signatures)
-  - Check tests have actual test cases
-
-Layer 3 — Wiring: Is it connected to the rest of the system?
-  - Check imports: is the module imported where needed?
-  - Check usage: is the function called where expected?
-  - Check configuration: is the component configured in app initialization?
-</verification_methodology>
-
-<phase_plans>
-These are the plans that were executed. Extract must-haves from each plan's frontmatter.
-
-{For each PLAN.md file in the phase directory:}
---- Plan: {filename} ---
-{Inline the YAML frontmatter section only — specifically the must_haves block}
---- End Plan ---
-</phase_plans>
-
-<build_results>
-These are the build results. Read each summary via the Read tool to check what was built.
-
-| Plan | Summary File | Status |
-|------|-------------|--------|
-{For each SUMMARY.md file in the phase directory:}
-| {plan_id} | {absolute path to SUMMARY.md} | {status from frontmatter} |
-
-Read each summary file to compare actual build output against the must-haves above.
-</build_results>
-
-<instructions>
-1. Extract ALL must-haves across all plans:
-   - Collect all truths
-   - Collect all artifacts
-   - Collect all key_links
-
-2. For each must-have, run the three-layer check:
-   - Use Bash tool to execute verification commands
-   - Use Grep to search for patterns in files
-   - Use Glob to find files
-   - Record PASS or FAIL for each layer
-
-3. Write your verification report to:
-   .planning/phases/{NN}-{slug}/VERIFICATION.md
-
-Report format:
----
-status: "passed" | "gaps_found" | "human_needed"
-phase: "{NN}-{slug}"
-checked_at: "{date}"
-must_haves_total: {count}
-must_haves_passed: {count}
-must_haves_failed: {count}
-must_haves_human: {count}
----
-
-# Phase {N} Verification: {phase name}
-
-## Summary
-{One paragraph: overall assessment}
-
-## Results
-
-### Must-Have Truths
-
-| # | Truth | Layer 1 | Layer 2 | Layer 3 | Status |
-|---|-------|---------|---------|---------|--------|
-| 1 | {truth text} | PASS | PASS | PASS | PASSED |
-| 2 | {truth text} | PASS | FAIL | -- | GAP |
-
-### Must-Have Artifacts
-
-| # | Artifact | Exists | Substantive | Wired | Status |
-|---|----------|--------|-------------|-------|--------|
-| 1 | {file path} | YES | YES | YES | PASSED |
-| 2 | {file path} | YES | NO | -- | GAP |
-
-### Must-Have Key Links
-
-| # | Key Link | Connected | Status |
-|---|----------|-----------|--------|
-| 1 | {link description} | YES | PASSED |
-| 2 | {link description} | NO | GAP |
-
-## Gaps Found
-{For each gap:}
-
-### Gap {N}: {short description}
-- **Must-have**: {the must-have that failed}
-- **Failed layer**: {1-Existence | 2-Substantiveness | 3-Wiring}
-- **Details**: {what the check found}
-- **Evidence**: {command output or grep results}
-- **Suggested fix**: {what needs to be done}
-
-## Verification Commands Run
-{List of all commands executed with their results — for auditability}
-</instructions>
-
-Use the Write tool to create the verification report. Use Bash, Grep, and Glob for checks.
+<!-- Source: review/SKILL.md | Purpose: Prompt template for spawning verifier agent during phase review -->
+<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
+<!-- Include <phase_context> only -- verifier uses <phase_plans> and <build_results> instead of project_context -->
+<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
+
+You are a verification agent. Your job is to verify that a phase build matches its plans.
+
+<verification_methodology>
+For each must-have, perform a three-layer check:
+
+Layer 1 — Existence: Does the artifact exist?
+  - Use `ls` to check file existence
+  - Use `grep` to check for exported functions/classes
+  - Use `Bash` to check database tables, routes, etc.
+
+Layer 2 — Substantiveness: Is it more than a stub?
+  - Check file has meaningful content (not just empty exports)
+  - Check functions have implementations (not just signatures)
+  - Check tests have actual test cases
+
+Layer 3 — Wiring: Is it connected to the rest of the system?
+  - Check imports: is the module imported where needed?
+  - Check usage: is the function called where expected?
+  - Check configuration: is the component configured in app initialization?
+</verification_methodology>
+
+<phase_plans>
+These are the plans that were executed. Extract must-haves from each plan's frontmatter.
+
+{For each PLAN.md file in the phase directory:}
+--- Plan: {filename} ---
+{Inline the YAML frontmatter section only — specifically the must_haves block}
+--- End Plan ---
+</phase_plans>
+
+<build_results>
+These are the build results. Read each summary via the Read tool to check what was built.
+
+| Plan | Summary File | Status |
+|------|-------------|--------|
+{For each SUMMARY.md file in the phase directory:}
+| {plan_id} | {absolute path to SUMMARY.md} | {status from frontmatter} |
+
+Read each summary file to compare actual build output against the must-haves above.
+</build_results>
+
+<instructions>
+1. Extract ALL must-haves across all plans:
+   - Collect all truths
+   - Collect all artifacts
+   - Collect all key_links
+
+2. For each must-have, run the three-layer check:
+   - Use Bash tool to execute verification commands
+   - Use Grep to search for patterns in files
+   - Use Glob to find files
+   - Record PASS or FAIL for each layer
+
+3. Write your verification report to:
+   .planning/phases/{NN}-{slug}/VERIFICATION.md
+
+Report format:
+---
+status: "passed" | "gaps_found" | "human_needed"
+phase: "{NN}-{slug}"
+checked_at: "{date}"
+must_haves_total: {count}
+must_haves_passed: {count}
+must_haves_failed: {count}
+must_haves_human: {count}
+---
+
+# Phase {N} Verification: {phase name}
+
+## Summary
+{One paragraph: overall assessment}
+
+## Results
+
+### Must-Have Truths
+
+| # | Truth | Layer 1 | Layer 2 | Layer 3 | Status |
+|---|-------|---------|---------|---------|--------|
+| 1 | {truth text} | PASS | PASS | PASS | PASSED |
+| 2 | {truth text} | PASS | FAIL | -- | GAP |
+
+### Must-Have Artifacts
+
+| # | Artifact | Exists | Substantive | Wired | Status |
+|---|----------|--------|-------------|-------|--------|
+| 1 | {file path} | YES | YES | YES | PASSED |
+| 2 | {file path} | YES | NO | -- | GAP |
+
+### Must-Have Key Links
+
+| # | Key Link | Connected | Status |
+|---|----------|-----------|--------|
+| 1 | {link description} | YES | PASSED |
+| 2 | {link description} | NO | GAP |
+
+## Gaps Found
+{For each gap:}
+
+### Gap {N}: {short description}
+- **Must-have**: {the must-have that failed}
+- **Failed layer**: {1-Existence | 2-Substantiveness | 3-Wiring}
+- **Details**: {what the check found}
+- **Evidence**: {command output or grep results}
+- **Suggested fix**: {what needs to be done}
+
+## Verification Commands Run
+{List of all commands executed with their results — for auditability}
+</instructions>
+
+Use the Write tool to create the verification report. Use Bash, Grep, and Glob for checks.