@sienklogic/plan-build-run 2.51.0 → 2.52.0

package/plugins/pbr/skills/plan/SKILL.md

@@ -116,7 +116,7 @@ Reference: `skills/shared/config-loading.md` for the tooling shortcut (`state lo
 
 1. Parse `$ARGUMENTS` for phase number and flags
 2. Read `.planning/config.json` for settings (see config-loading.md for field reference)
-   **CRITICAL: Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
+   **CRITICAL (hook-enforced): Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
 3. Resolve depth profile: run `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js config resolve-depth` to get the effective feature/gate settings for the current depth. Store the result for use in later gating decisions.
 4. Validate:
    - Phase exists in ROADMAP.md
@@ -210,7 +210,7 @@ Read `skills/plan/templates/researcher-prompt.md.tmpl` and use it as the prompt
 **Prepend this block to the researcher prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/ROADMAP.md — phase goals, dependencies, and structure
 2. .planning/REQUIREMENTS.md — scoped requirements for this phase (if exists)
 </files_to_read>
@@ -333,7 +333,7 @@ Read `skills/plan/templates/planner-prompt.md.tmpl` and use it as the prompt tem
 
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/CONTEXT.md — locked decisions and constraints (if exists)
 2. .planning/ROADMAP.md — phase goals, dependencies, and structure
 3. .planning/phases/{NN}-{slug}/RESEARCH.md — research findings (if exists)
@@ -355,7 +355,7 @@ Where `{N}` is the number of PLAN.md files written and `{M}` is the number of di
 
 ### Step 5b: Spot-Check Planner Output
 
-CRITICAL: Verify planner output before proceeding.
+CRITICAL (no hook): Verify planner output before proceeding.
 
 1. **PLAN files exist**: Check `.planning/phases/{NN}-{slug}/PLAN-*.md` files exist on disk
 2. **Valid frontmatter**: Read first 20 lines of each PLAN file — verify `depends_on`, `files_modified`, `must_haves` fields present
@@ -400,7 +400,7 @@ Read `skills/plan/templates/checker-prompt.md.tmpl` and use it as the prompt tem
 **Prepend this block to the checker prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/PLAN-*.md — plan files to validate
 2. .planning/CONTEXT.md — locked decisions to check against (if exists)
 </files_to_read>
@@ -470,7 +470,7 @@ Use AskUserQuestion (pattern: approve-revise-abort from `skills/shared/gate-prom
   4. Update the `Plans Complete` column to `0/{N}` where N = number of plan files just created
   5. Update the `Status` column to `planned`
   6. Save the file — do NOT skip this step
-- Update STATE.md via CLI **(CRITICAL — update BOTH frontmatter AND body)**: set `status: "planned"`, `plans_total`, `last_command` in frontmatter AND update `Status:`, `Plan:` lines in body `## Current Position`
+- Update STATE.md via CLI **(CRITICAL (no hook) — update BOTH frontmatter AND body)**: set `status: "planned"`, `plans_total`, `last_command` in frontmatter AND update `Status:`, `Plan:` lines in body `## Current Position`
 
 **Tooling shortcut**: `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js state patch '{"status":"planned","last_command":"/pbr:plan {N}"}'`
 - **If `features.auto_advance` is `true` AND `mode` is `autonomous`:** Chain directly to build: `Skill({ skill: "pbr:build", args: "{N}" })`. This continues the build→review→plan→build cycle automatically.
@@ -482,7 +482,7 @@ Use AskUserQuestion (pattern: approve-revise-abort from `skills/shared/gate-prom
 
 ### Subcommand: `add`
 
-**CRITICAL: Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
+**CRITICAL (hook-enforced): Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
 
 1. Read `.planning/ROADMAP.md`
 2. Calculate next phase number (last phase + 1)
@@ -499,7 +499,7 @@ Use AskUserQuestion (pattern: approve-revise-abort from `skills/shared/gate-prom
 
 Reference: `skills/plan/decimal-phase-calc.md` for decimal numbering rules.
 
-**CRITICAL: Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
+**CRITICAL (hook-enforced): Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
 
 1. Read `.planning/ROADMAP.md`
 2. Calculate decimal phase number:
@@ -520,7 +520,7 @@ Reference: `skills/plan/decimal-phase-calc.md` for decimal numbering rules.
    - Phase must exist
    - Phase must be in `pending` or `not started` status (cannot remove completed/in-progress phases)
    - No other phases depend on this phase (or user confirms breaking dependencies)
-3. **CRITICAL: Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
+3. **CRITICAL (hook-enforced): Write .active-skill NOW.** Write the text "plan" to `.planning/.active-skill` using the Write tool.
 4. Confirm with user: "Remove Phase {N}: {name}? This will delete the phase directory and renumber subsequent phases."
 5. If confirmed:
    - Delete `.planning/phases/{NN}-{slug}/` directory

package/plugins/pbr/skills/quick/SKILL.md

@@ -94,7 +94,7 @@ If user types something else (freeform): interpret their response and proceed ac
 
 ### Step 4: Generate Slug and Task Number
 
-**CRITICAL: You MUST complete Steps 4, 5, and 6 before any executor is spawned. If you skip these steps, the quick task will have no tracking artifacts and no PLAN.md for the executor to follow. This is the #1 failure mode of this skill.**
+**CRITICAL (no hook): You MUST complete Steps 4, 5, and 6 before any executor is spawned. If you skip these steps, the quick task will have no tracking artifacts and no PLAN.md for the executor to follow. This is the #1 failure mode of this skill.**
 
 **Generate slug:**
 - Take the first 4-5 meaningful words from the description
@@ -176,7 +176,7 @@ Spawn a `Task(subagent_type: "pbr:executor")` with the following prompt:
 You are executor. Execute the following quick task plan.
 
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/quick/{NNN}-{slug}/PLAN.md — the quick task plan with task details
 2. .planning/STATE.md — current project state and progress (if exists)
 </files_to_read>
@@ -205,7 +205,7 @@ After the executor completes:
 
 ### Step 8b: Spot-Check Executor Output
 
-CRITICAL: Verify executor output before proceeding.
+CRITICAL (no hook): Verify executor output before proceeding.
 
 1. **SUMMARY.md exists**: Check `.planning/quick/{NNN}-{slug}/SUMMARY.md` exists
 2. **Key files exist**: Verify first 2 files from SUMMARY.md `key_files` frontmatter exist on disk

package/plugins/pbr/skills/review/SKILL.md

@@ -68,7 +68,7 @@ Execute these steps in order.
 
 1. Parse `$ARGUMENTS` for phase number and `--auto-fix` flag
 2. Read `.planning/config.json`
-   **CRITICAL: Write .active-skill NOW.** Write the text "review" to `.planning/.active-skill` using the Write tool.
+   **CRITICAL (hook-enforced): Write .active-skill NOW.** Write the text "review" to `.planning/.active-skill` using the Write tool.
 3. Resolve depth profile: run `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js config resolve-depth` to get the effective feature/gate settings for the current depth. Store the result for use in later gating decisions.
 4. Validate:
    - Phase directory exists at `.planning/phases/{NN}-{slug}/`
@@ -180,7 +180,7 @@ Read `skills/review/templates/verifier-prompt.md.tmpl` and use its content as th
 **Prepend this block to the verifier prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/PLAN-*.md — must-haves to verify against
 2. .planning/phases/{NN}-{slug}/SUMMARY-*.md — executor build summaries
 3. .planning/phases/{NN}-{slug}/VERIFICATION.md — prior verification results (if exists)
@@ -215,7 +215,7 @@ Then display the overall verdict (`PASSED`, `GAPS FOUND`, or `HUMAN NEEDED`) bef
 
 ### Step 3a: Spot-Check Verifier Output
 
-CRITICAL: Verify verifier output before proceeding.
+CRITICAL (no hook): Verify verifier output before proceeding.
 
 1. **VERIFICATION.md exists**: Check `.planning/phases/{NN}-{slug}/VERIFICATION.md` exists on disk
 2. **Status field present**: Read VERIFICATION.md frontmatter — verify `status` field is present and is one of: pass, fail, partial
@@ -369,7 +369,7 @@ If all automated checks and UAT items passed:
    4. Update the `Status` column to `verified`
    5. Update the `Completed` column to the current date (YYYY-MM-DD)
    6. Save the file — do NOT skip this step
-2. Update `.planning/STATE.md` **(CRITICAL — update BOTH frontmatter AND body):**
+2. Update `.planning/STATE.md` **(CRITICAL (no hook) — update BOTH frontmatter AND body):**
    - Frontmatter: `status: "verified"`, `progress_percent`, `last_activity`, `last_command`
    - Body `## Current Position`: `Status:` line, `Last activity:` line, `Progress:` bar
    - These MUST stay in sync — see `skills/shared/state-update.md`
@@ -422,7 +422,7 @@ Read `skills/review/templates/debugger-prompt.md.tmpl` and use its content as th
 **Prepend this block to the debugger prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/VERIFICATION.md — gaps and failure details
 2. .planning/phases/{NN}-{slug}/SUMMARY-*.md — what was built
 3. .planning/phases/{NN}-{slug}/PLAN-*.md — original plan must-haves
@@ -454,7 +454,7 @@ Read `skills/review/templates/gap-planner-prompt.md.tmpl` and use its content as
 **Prepend this block to the gap planner prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/VERIFICATION.md — gaps to close
 2. .planning/phases/{NN}-{slug}/PLAN-*.md — existing plans for context
 3. .planning/CONTEXT.md — locked decisions and constraints (if exists)