@sienklogic/plan-build-run 2.0.0 → 2.0.2

package/plugins/pbr/skills/shared/state-update.md

@@ -1,161 +1,161 @@
-# STATE.md Update Pattern
-
-Standard pattern for updating `.planning/STATE.md`. Include this fragment in skills that modify project state.
-
----
-
-## When to Update STATE.md
-
-| Event | What to Update |
-|-------|---------------|
-| Phase status changes (planned, building, verified) | Current Position section |
-| Plan completes or fails | Plan counter, status, last activity |
-| New decision made | Accumulated Context > Decisions |
-| Blocker discovered or resolved | Accumulated Context > Blockers/Concerns |
-| Session starts or ends | Session Continuity section |
-| Milestone boundary | Milestone section |
-
----
-
-## Section Format
-
-STATE.md has 5 sections. Always preserve this order:
-
-### 1. Project Reference (lines 4-7)
-```
-## Project Reference
-See: .planning/PROJECT.md (updated {date})
-**Core value:** {one-liner from PROJECT.md}
-**Current focus:** Phase {N} - {name}
-```
-Update `Current focus` when phase changes.
-
-### 2. Current Position (lines 9-14)
-```
-## Current Position
-Phase: {N} of {total} ({Phase name})
-Plan: {completed} of {total_plans} in current phase
-Status: {Ready to plan | Planning | Building | Reviewing | Verified}
-Last activity: {YYYY-MM-DD} -- {brief description}
-Progress: [{progress_bar}] {percent}%
-```
-
-**Progress bar format:** 20 characters using `█` (done) and `░` (remaining).
-```
-Phase 3 of 10 = 20% → [████░░░░░░░░░░░░░░░░] 20%
-Phase 7 of 10 = 70% → [██████████████░░░░░░] 70%
-```
-Calculation: `filled = Math.round((completed_phases / total_phases) * 20)`
-
-### 3. Accumulated Context (lines 16-25)
-```
-## Accumulated Context
-
-### Decisions
-{Active decisions relevant to current work}
-
-### Pending Todos
-{Outstanding items, or "None"}
-
-### Blockers/Concerns
-{Active blockers, or "None"}
-```
-
-### 4. Milestone (lines 27-30)
-```
-## Milestone
-Current: {project_name} {version}
-Phases: {start}-{end}
-Status: {In progress | Complete}
-```
-
-### 5. Session Continuity (lines 32-35)
-```
-## Session Continuity
-Last session: {ISO timestamp}
-Stopped at: {brief description of last action}
-Resume file: {path or "None"}
-```
-
----
-
-## Size Limit Enforcement
-
-**Hard limit: 150 lines.** After every STATE.md write, check the line count. If over 150 lines, compact:
-
-1. **Collapse completed phase entries** to one-liners:
-   ```
-   Phase 1: verified 2026-02-08
-   Phase 2: verified 2026-02-09
-   ```
-2. **Remove decisions already captured in CONTEXT.md** — avoid duplication between STATE.md and phase CONTEXT.md files
-3. **Remove old session entries** — keep only the current session's continuity data
-4. **Keep these always:** current phase detail, active blockers, core value statement, milestone info
-
-If still over 150 lines after compaction, the Accumulated Context section has grown too large. Move non-critical decisions to the phase's CONTEXT.md file.
-
----
-
-## HISTORY.md Archival
-
-When a milestone completes or a phase is verified, archive historical context to `.planning/HISTORY.md` to keep STATE.md lean:
-
-### What to Archive
-
-| Trigger | What moves to HISTORY.md |
-|---------|-------------------------|
-| Phase verified | One-liner summary: "Phase {N} ({name}): verified {date}" |
-| Milestone complete | Full milestone record: name, phases covered, key decisions |
-| Accumulated Context > 20 lines | Decisions from completed phases (keep only current-phase decisions in STATE.md) |
-
-### How to Archive
-
-Use `pbr-tools.js history append`:
-```
-node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js history append phase "Phase 3 (Auth)" "Verified 2026-02-10. Key decisions: JWT + httpOnly cookies, Discord OAuth."
-node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js history append milestone "v1.0 User Auth" "Phases 1-4. All verified. Core auth flow complete."
-```
-
-### After Archiving
-
-Remove the archived content from STATE.md. The Accumulated Context section should contain ONLY:
-- Decisions relevant to the **current** phase
-- Active (unresolved) blockers
-- Pending todos for the current milestone
-
-Historical decisions live in HISTORY.md and per-phase SUMMARY.md files.
-
----
-
-## Common Update Scenarios
-
-### After build completes
-```
-Plan: {N} of {total} in current phase
-Status: Building → Reviewing (if all plans done) or Building (if more plans remain)
-Last activity: {date} -- Built plan {plan_id}
-```
-
-### After review/verification passes
-```
-Status: Verified
-Last activity: {date} -- Phase {N} verified
-Progress: [{updated bar}] {new percent}%
-```
-Also update **Current focus** to point to the next phase.
-
-### After pause
-```
-## Session Continuity
-Last session: {timestamp}
-Stopped at: {what was in progress}
-Resume file: .planning/.pause-state.json
-```
-
-### After milestone completion
-```
-## Milestone
-Current: {project_name} {next_version}
-Phases: {new_start}-{new_end}
-Status: In progress
-```
+# STATE.md Update Pattern
+
+Standard pattern for updating `.planning/STATE.md`. Include this fragment in skills that modify project state.
+
+---
+
+## When to Update STATE.md
+
+| Event | What to Update |
+|-------|---------------|
+| Phase status changes (planned, building, verified) | Current Position section |
+| Plan completes or fails | Plan counter, status, last activity |
+| New decision made | Accumulated Context > Decisions |
+| Blocker discovered or resolved | Accumulated Context > Blockers/Concerns |
+| Session starts or ends | Session Continuity section |
+| Milestone boundary | Milestone section |
+
+---
+
+## Section Format
+
+STATE.md has 5 sections. Always preserve this order:
+
+### 1. Project Reference (lines 4-7)
+```
+## Project Reference
+See: .planning/PROJECT.md (updated {date})
+**Core value:** {one-liner from PROJECT.md}
+**Current focus:** Phase {N} - {name}
+```
+Update `Current focus` when phase changes.
+
+### 2. Current Position (lines 9-14)
+```
+## Current Position
+Phase: {N} of {total} ({Phase name})
+Plan: {completed} of {total_plans} in current phase
+Status: {Ready to plan | Planning | Building | Reviewing | Verified}
+Last activity: {YYYY-MM-DD} -- {brief description}
+Progress: [{progress_bar}] {percent}%
+```
+
+**Progress bar format:** 20 characters using `█` (done) and `░` (remaining).
+```
+Phase 3 of 10 = 20% → [████░░░░░░░░░░░░░░░░] 20%
+Phase 7 of 10 = 70% → [██████████████░░░░░░] 70%
+```
+Calculation: `filled = Math.round((completed_phases / total_phases) * 20)`
+
+### 3. Accumulated Context (lines 16-25)
+```
+## Accumulated Context
+
+### Decisions
+{Active decisions relevant to current work}
+
+### Pending Todos
+{Outstanding items, or "None"}
+
+### Blockers/Concerns
+{Active blockers, or "None"}
+```
+
+### 4. Milestone (lines 27-30)
+```
+## Milestone
+Current: {project_name} {version}
+Phases: {start}-{end}
+Status: {In progress | Complete}
+```
+
+### 5. Session Continuity (lines 32-35)
+```
+## Session Continuity
+Last session: {ISO timestamp}
+Stopped at: {brief description of last action}
+Resume file: {path or "None"}
+```
+
+---
+
+## Size Limit Enforcement
+
+**Hard limit: 150 lines.** After every STATE.md write, check the line count. If over 150 lines, compact:
+
+1. **Collapse completed phase entries** to one-liners:
+   ```
+   Phase 1: verified 2026-02-08
+   Phase 2: verified 2026-02-09
+   ```
+2. **Remove decisions already captured in CONTEXT.md** — avoid duplication between STATE.md and phase CONTEXT.md files
+3. **Remove old session entries** — keep only the current session's continuity data
+4. **Keep these always:** current phase detail, active blockers, core value statement, milestone info
+
+If still over 150 lines after compaction, the Accumulated Context section has grown too large. Move non-critical decisions to the phase's CONTEXT.md file.
+
+---
+
+## HISTORY.md Archival
+
+When a milestone completes or a phase is verified, archive historical context to `.planning/HISTORY.md` to keep STATE.md lean:
+
+### What to Archive
+
+| Trigger | What moves to HISTORY.md |
+|---------|-------------------------|
+| Phase verified | One-liner summary: "Phase {N} ({name}): verified {date}" |
+| Milestone complete | Full milestone record: name, phases covered, key decisions |
+| Accumulated Context > 20 lines | Decisions from completed phases (keep only current-phase decisions in STATE.md) |
+
+### How to Archive
+
+Use `pbr-tools.js history append`:
+```
+node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js history append phase "Phase 3 (Auth)" "Verified 2026-02-10. Key decisions: JWT + httpOnly cookies, Discord OAuth."
+node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js history append milestone "v1.0 User Auth" "Phases 1-4. All verified. Core auth flow complete."
+```
+
+### After Archiving
+
+Remove the archived content from STATE.md. The Accumulated Context section should contain ONLY:
+- Decisions relevant to the **current** phase
+- Active (unresolved) blockers
+- Pending todos for the current milestone
+
+Historical decisions live in HISTORY.md and per-phase SUMMARY.md files.
+
+---
+
+## Common Update Scenarios
+
+### After build completes
+```
+Plan: {N} of {total} in current phase
+Status: Building → Reviewing (if all plans done) or Building (if more plans remain)
+Last activity: {date} -- Built plan {plan_id}
+```
+
+### After review/verification passes
+```
+Status: Verified
+Last activity: {date} -- Phase {N} verified
+Progress: [{updated bar}] {new percent}%
+```
+Also update **Current focus** to point to the next phase.
+
+### After pause
+```
+## Session Continuity
+Last session: {timestamp}
+Stopped at: {what was in progress}
+Resume file: .planning/.pause-state.json
+```
+
+### After milestone completion
+```
+## Milestone
+Current: {project_name} {next_version}
+Phases: {new_start}-{new_end}
+Status: In progress
+```

package/plugins/pbr/skills/shared/universal-anti-patterns.md

@@ -1,33 +1,33 @@
-# Universal Anti-Patterns
-
-Rules that apply to ALL skills. Individual skills may have additional skill-specific anti-patterns listed in their own SKILL.md.
-
-> Referenced by: all skills with Context Budget or Anti-Patterns sections
-
----
-
-## Context Budget Rules (apply to every skill)
-
-These rules prevent context rot -- quality degradation as the context window fills up.
-
-1. **Never** read agent definition files (`agents/*.md`) -- `subagent_type` auto-loads them. Reading agent definitions into the orchestrator wastes main context for content that is automatically injected into subagent sessions.
-2. **Never** inline large files into Task() prompts -- tell agents to read files from disk instead. Agents have their own 200k token context windows.
-3. **Minimize** reading subagent output into main context -- read only frontmatter, status fields, or summaries. Never read full SUMMARY.md, VERIFICATION.md, or RESEARCH.md bodies into the orchestrator unless specifically needed for inline presentation.
-4. **Delegate** heavy work to Task() subagents -- the orchestrator routes, it does not build, analyze, research, investigate, or verify.
-5. **Proactive pause warning**: If you have already consumed significant context (large file reads, multiple subagent results), warn the user: "Context budget is getting heavy. Consider running `/pbr:pause` to checkpoint progress." Suggest pause proactively rather than waiting for compaction.
-
-## File Reading Rules (apply to every skill)
-
-6. **Never** read full SUMMARY.md bodies from prior phases -- read frontmatter only (unless the skill specifically requires body content for presentation).
-7. **Never** read full PLAN.md files from other phases -- only current phase plans.
-8. **Never** read `.planning/logs/` files -- only the health skill reads these.
-9. **Do not** re-read full file contents when frontmatter is sufficient -- frontmatter contains status, key_files, commits, and provides fields.
-
-## Behavioral Rules (apply to every skill)
-
-10. **Do not** re-litigate decisions that are already locked in CONTEXT.md -- respect locked decisions unconditionally.
-11. **Do not** create artifacts the user did not approve -- always confirm before writing new planning documents.
-12. **Do not** modify files outside the skill's stated scope -- check the "Files Created/Modified" table in each skill.
-13. **Do not** suggest multiple next actions without clear priority -- one primary suggestion, alternatives listed secondary.
-14. **Do not** use `git add .` or `git add -A` -- stage specific files only.
-15. **Do not** include sensitive information (API keys, passwords, tokens) in planning documents or commits.
+# Universal Anti-Patterns
+
+Rules that apply to ALL skills. Individual skills may have additional skill-specific anti-patterns listed in their own SKILL.md.
+
+> Referenced by: all skills with Context Budget or Anti-Patterns sections
+
+---
+
+## Context Budget Rules (apply to every skill)
+
+These rules prevent context rot -- quality degradation as the context window fills up.
+
+1. **Never** read agent definition files (`agents/*.md`) -- `subagent_type` auto-loads them. Reading agent definitions into the orchestrator wastes main context for content that is automatically injected into subagent sessions.
+2. **Never** inline large files into Task() prompts -- tell agents to read files from disk instead. Agents have their own 200k token context windows.
+3. **Minimize** reading subagent output into main context -- read only frontmatter, status fields, or summaries. Never read full SUMMARY.md, VERIFICATION.md, or RESEARCH.md bodies into the orchestrator unless specifically needed for inline presentation.
+4. **Delegate** heavy work to Task() subagents -- the orchestrator routes, it does not build, analyze, research, investigate, or verify.
+5. **Proactive pause warning**: If you have already consumed significant context (large file reads, multiple subagent results), warn the user: "Context budget is getting heavy. Consider running `/pbr:pause` to checkpoint progress." Suggest pause proactively rather than waiting for compaction.
+
+## File Reading Rules (apply to every skill)
+
+6. **Never** read full SUMMARY.md bodies from prior phases -- read frontmatter only (unless the skill specifically requires body content for presentation).
+7. **Never** read full PLAN.md files from other phases -- only current phase plans.
+8. **Never** read `.planning/logs/` files -- only the health skill reads these.
+9. **Do not** re-read full file contents when frontmatter is sufficient -- frontmatter contains status, key_files, commits, and provides fields.
+
+## Behavioral Rules (apply to every skill)
+
+10. **Do not** re-litigate decisions that are already locked in CONTEXT.md -- respect locked decisions unconditionally.
+11. **Do not** create artifacts the user did not approve -- always confirm before writing new planning documents.
+12. **Do not** modify files outside the skill's stated scope -- check the "Files Created/Modified" table in each skill.
+13. **Do not** suggest multiple next actions without clear priority -- one primary suggestion, alternatives listed secondary.
+14. **Do not** use `git add .` or `git add -A` -- stage specific files only.
+15. **Do not** include sensitive information (API keys, passwords, tokens) in planning documents or commits.