@sienklogic/plan-build-run 2.0.0 → 2.0.1

package/plugins/pbr/skills/plan/decimal-phase-calc.md

@@ -1,98 +1,98 @@
-# Decimal Phase Numbering
-
-Rules for calculating decimal phase numbers when inserting phases into an existing roadmap.
-
----
-
-## Core Rule
-
-Inserted phases get decimal numbers based on their insertion position. The integer part indicates where in the sequence the phase falls, and the decimal part indicates it was inserted.
-
----
-
-## Calculation
-
-### Insert at position N
-
-```
-1. Find phase N in the roadmap
-2. Check if N.1 already exists
-3. If not: new phase is N.1
-4. If yes: check N.2, N.3, etc. until an unused number is found
-```
-
-### Examples
-
-**Insert between Phase 3 and Phase 4:**
-```
-Before: Phase 1, Phase 2, Phase 3, Phase 4, Phase 5
-After:  Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 4, Phase 5
-```
-
-**Insert another between Phase 3 and Phase 4:**
-```
-Before: Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 4, Phase 5
-After:  Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 3.2, Phase 4, Phase 5
-```
-
-**Insert between Phase 3.1 and Phase 3.2:**
-This is NOT supported. Maximum one level of decimal insertion. If you need to insert between decimal phases, renumber the entire sequence first.
-
----
-
-## Directory Naming
-
-```
-Phase 3   → .planning/phases/03-{slug}/
-Phase 3.1 → .planning/phases/03.1-{slug}/
-Phase 3.2 → .planning/phases/03.2-{slug}/
-```
-
----
-
-## Plan ID Format
-
-Plans in decimal phases use the decimal in their ID:
-
-```
-Phase 3.1, Plan 01 → Plan ID: 3.1-01
-Phase 3.1, Plan 02 → Plan ID: 3.1-02
-```
-
----
-
-## Execution Order
-
-Decimal phases execute AFTER their integer parent and BEFORE the next integer:
-
-```
-Execution order: 1, 2, 3, 3.1, 3.2, 4, 5
-```
-
-Dependencies:
-- Decimal phases inherit the dependencies of their integer parent by default
-- Additional dependencies can be declared explicitly
-- A decimal phase at N.M depends on phase N unless overridden
-
----
-
-## Renumbering After Remove
-
-When a phase is removed, subsequent phases are renumbered:
-
-```
-Before: Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 4
-Remove Phase 2:
-After:  Phase 1, Phase 2 (was 3), Phase 2.1 (was 3.1), Phase 3 (was 4)
-```
-
-All internal references (depends_on, plan IDs, directory names) must be updated during renumbering.
-
----
-
-## Constraints
-
-1. Maximum one level of decimal numbering (no 3.1.1)
-2. Decimal part is always a single digit (3.1 through 3.9)
-3. Maximum 9 insertions at any position (3.1 through 3.9)
-4. If 9 insertions are needed, renumber the entire roadmap instead
+# Decimal Phase Numbering
+
+Rules for calculating decimal phase numbers when inserting phases into an existing roadmap.
+
+---
+
+## Core Rule
+
+Inserted phases get decimal numbers based on their insertion position. The integer part indicates where in the sequence the phase falls, and the decimal part indicates it was inserted.
+
+---
+
+## Calculation
+
+### Insert at position N
+
+```
+1. Find phase N in the roadmap
+2. Check if N.1 already exists
+3. If not: new phase is N.1
+4. If yes: check N.2, N.3, etc. until an unused number is found
+```
+
+### Examples
+
+**Insert between Phase 3 and Phase 4:**
+```
+Before: Phase 1, Phase 2, Phase 3, Phase 4, Phase 5
+After:  Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 4, Phase 5
+```
+
+**Insert another between Phase 3 and Phase 4:**
+```
+Before: Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 4, Phase 5
+After:  Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 3.2, Phase 4, Phase 5
+```
+
+**Insert between Phase 3.1 and Phase 3.2:**
+This is NOT supported. Maximum one level of decimal insertion. If you need to insert between decimal phases, renumber the entire sequence first.
+
+---
+
+## Directory Naming
+
+```
+Phase 3   → .planning/phases/03-{slug}/
+Phase 3.1 → .planning/phases/03.1-{slug}/
+Phase 3.2 → .planning/phases/03.2-{slug}/
+```
+
+---
+
+## Plan ID Format
+
+Plans in decimal phases use the decimal in their ID:
+
+```
+Phase 3.1, Plan 01 → Plan ID: 3.1-01
+Phase 3.1, Plan 02 → Plan ID: 3.1-02
+```
+
+---
+
+## Execution Order
+
+Decimal phases execute AFTER their integer parent and BEFORE the next integer:
+
+```
+Execution order: 1, 2, 3, 3.1, 3.2, 4, 5
+```
+
+Dependencies:
+- Decimal phases inherit the dependencies of their integer parent by default
+- Additional dependencies can be declared explicitly
+- A decimal phase at N.M depends on phase N unless overridden
+
+---
+
+## Renumbering After Remove
+
+When a phase is removed, subsequent phases are renumbered:
+
+```
+Before: Phase 1, Phase 2, Phase 3, Phase 3.1, Phase 4
+Remove Phase 2:
+After:  Phase 1, Phase 2 (was 3), Phase 2.1 (was 3.1), Phase 3 (was 4)
+```
+
+All internal references (depends_on, plan IDs, directory names) must be updated during renumbering.
+
+---
+
+## Constraints
+
+1. Maximum one level of decimal numbering (no 3.1.1)
+2. Decimal part is always a single digit (3.1 through 3.9)
+3. Maximum 9 insertions at any position (3.1 through 3.9)
+4. If 9 insertions are needed, renumber the entire roadmap instead

package/plugins/pbr/skills/plan/templates/checker-prompt.md.tmpl

@@ -1,21 +1,21 @@
-<!-- Source: plan/SKILL.md | Purpose: Prompt template for spawning plan checker agent -->
-<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
-
-You are the plan-checker agent.
-
-<plans_to_check>
-Read and check each of these plan files:
-
-| Plan | File Path |
-|------|-----------|
-{For each PLAN.md file in .planning/phases/{NN}-{slug}/:}
-| {plan_id} | {absolute path to PLAN.md} |
-
-Read each plan file using the Read tool. Verify all 7 dimensions against each plan.
-</plans_to_check>
-
-<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
-<!-- Omit <prior_work> -- checker only needs plans and context -->
-
-Run all 7 verification dimensions on these plans. Return your structured report.
-Do NOT write any files. Return your findings as your response text.
+<!-- Source: plan/SKILL.md | Purpose: Prompt template for spawning plan checker agent -->
+<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
+
+You are the plan-checker agent.
+
+<plans_to_check>
+Read and check each of these plan files:
+
+| Plan | File Path |
+|------|-----------|
+{For each PLAN.md file in .planning/phases/{NN}-{slug}/:}
+| {plan_id} | {absolute path to PLAN.md} |
+
+Read each plan file using the Read tool. Verify all 7 dimensions against each plan.
+</plans_to_check>
+
+<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
+<!-- Omit <prior_work> -- checker only needs plans and context -->
+
+Run all 7 verification dimensions on these plans. Return your structured report.
+Do NOT write any files. Return your findings as your response text.

package/plugins/pbr/skills/plan/templates/gap-closure-prompt.md.tmpl

@@ -1,32 +1,32 @@
-<!-- Source: plan/SKILL.md | Purpose: Prompt template for planner gap closure mode -->
-
-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>
-
-<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>
-
-<project_context>
-{If CONTEXT.md exists:}
-Project context (locked decisions, constraints): {absolute path to CONTEXT.md}
-Read this file for locked decisions that must be honored in gap-closure plans.
-{If not: "No CONTEXT.md found."}
-</project_context>
-
-<gap_closure_instructions>
-Read the verification report and create targeted plans to close each gap.
-Follow your Gap Closure Mode instructions.
-Number new plans starting after the last existing plan number.
-Set gap_closure: true in the frontmatter of each new plan.
-Write gap-closure plan files to: .planning/phases/{NN}-{slug}/
-</gap_closure_instructions>
+<!-- Source: plan/SKILL.md | Purpose: Prompt template for planner gap closure mode -->
+
+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>
+
+<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>
+
+<project_context>
+{If CONTEXT.md exists:}
+Project context (locked decisions, constraints): {absolute path to CONTEXT.md}
+Read this file for locked decisions that must be honored in gap-closure plans.
+{If not: "No CONTEXT.md found."}
+</project_context>
+
+<gap_closure_instructions>
+Read the verification report and create targeted plans to close each gap.
+Follow your Gap Closure Mode instructions.
+Number new plans starting after the last existing plan number.
+Set gap_closure: true in the frontmatter of each new plan.
+Write gap-closure plan files to: .planning/phases/{NN}-{slug}/
+</gap_closure_instructions>

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

@@ -1,38 +1,38 @@
-<!-- Source: plan/SKILL.md | Purpose: Prompt template for spawning planner agent during phase planning -->
-<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
-
-You are the planner agent operating in Standard Planning mode.
-
-<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
-<!-- Include all 3 blocks: phase_context, project_context, prior_work -->
-
-<research>
-{If RESEARCH.md exists:}
-Phase research available at: {absolute path to RESEARCH.md}
-Read this file for technology recommendations, implementation patterns, and pitfalls.
-{If not: "No phase-specific research conducted."}
-{If research SUMMARY.md exists:}
-Research summary available at: {absolute path to research SUMMARY.md}
-</research>
-
-<config>
-Max tasks per plan: {from config.json}
-Parallelization enabled: {from config.json}
-TDD mode: {from config.json}
-</config>
-
-<planning_instructions>
-Create executable plans for this phase following your Standard Planning mode instructions.
-
-Key rules:
-1. Apply goal-backward methodology — derive must-haves first
-2. 2-3 tasks per plan, 5-8 files per plan maximum
-3. Assign wave numbers for parallel execution
-4. Every task needs all 5 elements: name, files, action, verify, done
-5. Honor all locked decisions from CONTEXT.md
-6. Do NOT include deferred ideas
-7. Write plan files to: .planning/phases/{NN}-{slug}/{phase}-{plan_num}-PLAN.md
-8. If any task requires env vars, API keys, or external service setup, note it in the task's <action> — the executor will generate USER-SETUP.md automatically
-
-Use the Write tool to create each plan file.
-</planning_instructions>
+<!-- Source: plan/SKILL.md | Purpose: Prompt template for spawning planner agent during phase planning -->
+<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
+
+You are the planner agent operating in Standard Planning mode.
+
+<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
+<!-- Include all 3 blocks: phase_context, project_context, prior_work -->
+
+<research>
+{If RESEARCH.md exists:}
+Phase research available at: {absolute path to RESEARCH.md}
+Read this file for technology recommendations, implementation patterns, and pitfalls.
+{If not: "No phase-specific research conducted."}
+{If research SUMMARY.md exists:}
+Research summary available at: {absolute path to research SUMMARY.md}
+</research>
+
+<config>
+Max tasks per plan: {from config.json}
+Parallelization enabled: {from config.json}
+TDD mode: {from config.json}
+</config>
+
+<planning_instructions>
+Create executable plans for this phase following your Standard Planning mode instructions.
+
+Key rules:
+1. Apply goal-backward methodology — derive must-haves first
+2. 2-3 tasks per plan, 5-8 files per plan maximum
+3. Assign wave numbers for parallel execution
+4. Every task needs all 5 elements: name, files, action, verify, done
+5. Honor all locked decisions from CONTEXT.md
+6. Do NOT include deferred ideas
+7. Write plan files to: .planning/phases/{NN}-{slug}/{phase}-{plan_num}-PLAN.md
+8. If any task requires env vars, API keys, or external service setup, note it in the task's <action> — the executor will generate USER-SETUP.md automatically
+
+Use the Write tool to create each plan file.
+</planning_instructions>

package/plugins/pbr/skills/plan/templates/researcher-prompt.md.tmpl

@@ -1,19 +1,19 @@
-<!-- Source: plan/SKILL.md | Purpose: Prompt template for spawning researcher agent during phase planning -->
-<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
-
-You are the researcher agent operating in Phase Research mode.
-
-<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
-<!-- Include the filled <phase_context> and <project_context> blocks here. -->
-<!-- Omit <prior_work> and deferred ideas -- researcher doesn't need them -->
-
-<research_questions>
-Research these specific questions for this phase:
-1. What is the best implementation approach for {phase goal}?
-2. What libraries/packages are needed?
-3. What are the common pitfalls for this type of work?
-4. What configuration is needed?
-5. How does this integrate with what's already been built?
-</research_questions>
-
-Write your findings to .planning/phases/{NN}-{slug}/RESEARCH.md using the Phase Research output format. Use the Write tool.
+<!-- Source: plan/SKILL.md | Purpose: Prompt template for spawning researcher agent during phase planning -->
+<!-- Depends on: templates/prompt-partials/phase-project-context.md.tmpl -->
+
+You are the researcher agent operating in Phase Research mode.
+
+<!-- Context blocks: Read and fill templates/prompt-partials/phase-project-context.md.tmpl -->
+<!-- Include the filled <phase_context> and <project_context> blocks here. -->
+<!-- Omit <prior_work> and deferred ideas -- researcher doesn't need them -->
+
+<research_questions>
+Research these specific questions for this phase:
+1. What is the best implementation approach for {phase goal}?
+2. What libraries/packages are needed?
+3. What are the common pitfalls for this type of work?
+4. What configuration is needed?
+5. How does this integrate with what's already been built?
+</research_questions>
+
+Write your findings to .planning/phases/{NN}-{slug}/RESEARCH.md using the Phase Research output format. Use the Write tool.

package/plugins/pbr/skills/plan/templates/revision-prompt.md.tmpl

@@ -1,23 +1,23 @@
-<!-- Source: plan/SKILL.md | Purpose: Prompt template for planner revision mode when checker finds issues -->
-
-You are the planner agent operating in Revision Mode.
-
-<original_plans>
-Read the current plan files that need revision:
-
-| Plan | File Path |
-|------|-----------|
-{For each PLAN.md in the phase directory:}
-| {plan_id} | {absolute path to PLAN.md} |
-
-Read each plan file using the Read tool before revising.
-</original_plans>
-
-<checker_feedback>
-[Inline the checker's issue report]
-</checker_feedback>
-
-<revision_instructions>
-Revise the plans to address all BLOCKER and WARNING issues. Follow your Revision Mode instructions.
-Preserve task IDs that don't need changes. Write updated plan files to the same paths.
-</revision_instructions>
+<!-- Source: plan/SKILL.md | Purpose: Prompt template for planner revision mode when checker finds issues -->
+
+You are the planner agent operating in Revision Mode.
+
+<original_plans>
+Read the current plan files that need revision:
+
+| Plan | File Path |
+|------|-----------|
+{For each PLAN.md in the phase directory:}
+| {plan_id} | {absolute path to PLAN.md} |
+
+Read each plan file using the Read tool before revising.
+</original_plans>
+
+<checker_feedback>
+[Inline the checker's issue report]
+</checker_feedback>
+
+<revision_instructions>
+Revise the plans to address all BLOCKER and WARNING issues. Follow your Revision Mode instructions.
+Preserve task IDs that don't need changes. Write updated plan files to the same paths.
+</revision_instructions>