@sienklogic/plan-build-run 2.0.0 → 2.0.2

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

@@ -1,181 +1,198 @@
----
-name: todo
-description: "File-based persistent todos. Add, list, complete — survives sessions."
-allowed-tools: Read, Write, Bash, Glob, Grep
-argument-hint: "add <description> | list [theme] | done <NNN>"
----
-
-# /pbr:todo — Persistent File-Based Todos
-
-## Why File-Based
-
-Native Claude Code Tasks are session-scoped — they vanish when the conversation ends. Plan-Build-Run todos are individual `.md` files in `.planning/todos/` that persist across sessions, context resets, and compactions.
-
-## Subcommands
-
-Parse `$ARGUMENTS` to determine the subcommand:
-
-### `add <description>`
-
-1. Ensure `.planning/todos/pending/` directory exists
-2. Generate NNN: scan **both** `.planning/todos/pending/` and `.planning/todos/done/` for the highest existing number, then increment by 1 (zero-padded to 3 digits)
-3. Generate slug: take the first ~4 meaningful words from the description, lowercase, hyphen-separated (e.g., "Add rate limiting to login" → `add-rate-limiting-login`)
-4. Infer theme from description (e.g., "auth" → security, "test" → testing, "UI" → frontend, "refactor" → quality)
-5. Check for duplicates — read existing pending todos, if a similar one exists, ask user via AskUserQuestion
-6. Create `.planning/todos/pending/{NNN}-{slug}.md`:
-
-```yaml
----
-title: "{description}"
-status: pending
-priority: P2
-source: conversation
-created: {YYYY-MM-DD}
-theme: {inferred-theme}
----
-
-## Goal
-
-{description expanded into a clear goal statement}
-
-## Scope
-
-{any relevant context from the current conversation, or bullet points of what's in/out of scope}
-
-## Acceptance Criteria
-
-- [ ] {primary acceptance criterion derived from description}
-```
-
-7. Update STATE.md Pending Todos section
-
-   If the Write fails, display:
-   ```
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  ERROR                                                       ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   Failed to write todo file.
-
-   **To fix:** Check that `.planning/todos/pending/` exists and is writable.
-   ```
-
-8. Confirm with branded output:
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► TODO ADDED ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-**Todo {NNN}:** {description}
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Work on it now** or see your task list
-
-`/pbr:quick`
-
-<sub>`/clear` first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- `/pbr:todo list` — see all pending todos
-- `/pbr:status` — see project status
-
-───────────────────────────────────────────────────────────────
-```
-
-### `list [theme]`
-
-1. Read all files in `.planning/todos/pending/`
-2. Parse frontmatter from each
-3. If theme filter provided, filter by theme
-4. Display as table:
-
-```
-Pending Todos:
-| # | Title | Priority | Theme | Created |
-|---|-------|----------|-------|---------|
-| 074 | Status-line customization options | P2 | capability | 2026-02-10 |
-| 075 | Add WebSearch/WebFetch/Context7 to researcher | P2 | capability | 2026-02-10 |
-```
-
-5. Offer actions with branded routing:
-```
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Pick a todo** — mark one done or start working
-
-`/pbr:todo done <NNN>`
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- `/pbr:quick` — work on one now
-- `/pbr:status` — see project status
-
-───────────────────────────────────────────────────────────────
-```
-
-### `done <NNN>`
-
-1. Find `.planning/todos/pending/{NNN}-*.md` (match by number prefix)
-2. If not found, display:
-```
-╔══════════════════════════════════════════════════════════════╗
-║  ERROR                                                       ║
-╚══════════════════════════════════════════════════════════════╝
-
-Todo {NNN} not found in pending todos.
-
-**To fix:** Run `/pbr:todo list` to see available numbers.
-```
-3. Move file to `.planning/todos/done/{NNN}-{slug}.md`
-4. Update frontmatter: set `status: done` and add `completed: {YYYY-MM-DD}`
-5. Update STATE.md
-6. Confirm with branded output:
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► TODO COMPLETED ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-**Todo {NNN}:** {title}
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**See remaining tasks**
-
-`/pbr:todo list`
-
-<sub>`/clear` first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- `/pbr:continue` — execute next logical step
-- `/pbr:status` — see project status
-
-───────────────────────────────────────────────────────────────
-```
-
-### No arguments
-
-Show a brief summary: count of pending todos, grouped by theme, plus usage hint.
-
-## State Integration
-
-After any todo operation, update the "Pending Todos" section of STATE.md with the current count and list.
-
-## Git Integration
-
-Reference: `skills/shared/commit-planning-docs.md` for the standard commit pattern.
-
-If `planning.commit_docs: true` in config, commit todo changes:
-- `docs(planning): add todo {NNN}`
-- `docs(planning): complete todo {NNN}`
+---
+name: todo
+description: "File-based persistent todos. Add, list, complete — survives sessions."
+allowed-tools: Read, Write, Bash, Glob, Grep
+argument-hint: "add <description> | list [theme] | done <NNN>"
+---
+
+**STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 tokens. Begin executing Step 1 immediately.**
+
+## Step 0 — Immediate Output
+
+**Before ANY tool calls**, display this banner:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PLAN-BUILD-RUN ► TODO
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+Then proceed to Step 1.
+
+# /pbr:todo — Persistent File-Based Todos
+
+## Why File-Based
+
+Native Claude Code Tasks are session-scoped — they vanish when the conversation ends. Plan-Build-Run todos are individual `.md` files in `.planning/todos/` that persist across sessions, context resets, and compactions.
+
+## Subcommands
+
+Parse `$ARGUMENTS` to determine the subcommand:
+
+### `add <description>`
+
+1. Ensure `.planning/todos/pending/` directory exists
+2. Generate NNN: scan **both** `.planning/todos/pending/` and `.planning/todos/done/` for the highest existing number, then increment by 1 (zero-padded to 3 digits)
+3. Generate slug: take the first ~4 meaningful words from the description, lowercase, hyphen-separated (e.g., "Add rate limiting to login" → `add-rate-limiting-login`)
+4. Infer theme from description (e.g., "auth" → security, "test" → testing, "UI" → frontend, "refactor" → quality)
+5. Check for duplicates — read existing pending todos, if a similar one exists, ask user via AskUserQuestion
+6. Create `.planning/todos/pending/{NNN}-{slug}.md`:
+
+```yaml
+---
+title: "{description}"
+status: pending
+priority: P2
+source: conversation
+created: {YYYY-MM-DD}
+theme: {inferred-theme}
+---
+
+## Goal
+
+{description expanded into a clear goal statement}
+
+## Scope
+
+{any relevant context from the current conversation, or bullet points of what's in/out of scope}
+
+## Acceptance Criteria
+
+- [ ] {primary acceptance criterion derived from description}
+```
+
+7. Update STATE.md Pending Todos section
+
+   If the Write fails, display:
+   ```
+   ╔══════════════════════════════════════════════════════════════╗
+   ║  ERROR                                                       ║
+   ╚══════════════════════════════════════════════════════════════╝
+
+   Failed to write todo file.
+
+   **To fix:** Check that `.planning/todos/pending/` exists and is writable.
+   ```
+
+8. Confirm with branded output:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PLAN-BUILD-RUN ► TODO ADDED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Todo {NNN}:** {description}
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Work on it now** or see your task list
+
+`/pbr:quick`
+
+<sub>`/clear` first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- `/pbr:todo list` — see all pending todos
+- `/pbr:status` — see project status
+
+───────────────────────────────────────────────────────────────
+```
+
+### `list [theme]`
+
+1. Read all files in `.planning/todos/pending/`
+2. Parse frontmatter from each
+3. If theme filter provided, filter by theme
+4. Display as table:
+
+```
+Pending Todos:
+| # | Title | Priority | Theme | Created |
+|---|-------|----------|-------|---------|
+| 074 | Status-line customization options | P2 | capability | 2026-02-10 |
+| 075 | Add WebSearch/WebFetch/Context7 to researcher | P2 | capability | 2026-02-10 |
+```
+
+5. Offer actions with branded routing:
+```
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Pick a todo** — mark one done or start working
+
+`/pbr:todo done <NNN>`
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- `/pbr:quick` — work on one now
+- `/pbr:status` — see project status
+
+───────────────────────────────────────────────────────────────
+```
+
+### `done <NNN>`
+
+1. Find `.planning/todos/pending/{NNN}-*.md` (match by number prefix)
+2. If not found, display:
+```
+╔══════════════════════════════════════════════════════════════╗
+║  ERROR                                                       ║
+╚══════════════════════════════════════════════════════════════╝
+
+Todo {NNN} not found in pending todos.
+
+**To fix:** Run `/pbr:todo list` to see available numbers.
+```
+3. Ensure `.planning/todos/done/` directory exists (create if needed)
+4. Read the pending file content
+5. Update frontmatter in the content: set `status: done` and add `completed: {YYYY-MM-DD}`
+6. Write the updated content to `.planning/todos/done/{NNN}-{slug}.md`
+7. Delete the original file from `.planning/todos/pending/` (use `rm` via Bash)
+8. Update STATE.md
+9. Confirm with branded output:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PLAN-BUILD-RUN ► TODO COMPLETED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Todo {NNN}:** {title}
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**See remaining tasks**
+
+`/pbr:todo list`
+
+<sub>`/clear` first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- `/pbr:continue` — execute next logical step
+- `/pbr:status` — see project status
+
+───────────────────────────────────────────────────────────────
+```
+
+### No arguments
+
+Show a brief summary: count of pending todos, grouped by theme, plus usage hint.
+
+## State Integration
+
+After any todo operation, update the "Pending Todos" section of STATE.md with the current count and list.
+
+## Git Integration
+
+Reference: `skills/shared/commit-planning-docs.md` for the standard commit pattern.
+
+If `planning.commit_docs: true` in config, commit todo changes:
+- `docs(planning): add todo {NNN}`
+- `docs(planning): complete todo {NNN}`

package/plugins/pbr/templates/CONTEXT.md.tmpl

@@ -1,52 +1,52 @@
-# CONTEXT.md Template
-
-> Referenced by: begin skill (Step 9c), discuss skill, plan skill
-> Created during /pbr:begin. Updated by /pbr:discuss and /pbr:plan --assumptions.
-
-## Structure
-
-```markdown
-# Project Context
-
-## Locked Decisions
-
-{Technology choices, architecture decisions, and constraints that are NON-NEGOTIABLE.
- These MUST be honored by every plan and executor — no exceptions.}
-
-| Decision | Rationale | Locked By |
-|----------|-----------|-----------|
-| {e.g., "Use TypeScript"} | {User preference, team skill} | User |
-| {e.g., "PostgreSQL via Supabase"} | {Existing infrastructure} | User |
-
-## User Constraints
-
-{Budget, timeline, skill level, hosting, team size — factors that shape planning}
-
-- {e.g., "Solo developer, no team"}
-- {e.g., "Deploy to Hetzner VPS"}
-- {e.g., "Must work offline"}
-
-## Deferred Ideas
-
-{Features explicitly moved to v2 or out-of-scope. Plans MUST NOT include these.}
-
-| Idea | Reason Deferred |
-|------|----------------|
-| {feature} | {reason} |
-
-## Claude's Discretion Areas
-
-{Areas where the planner can make implementation choices without asking the user.
- Document the choice made and rationale when exercised.}
-
-| Area | Choice Made | Rationale |
-|------|------------|-----------|
-| {e.g., "State management library"} | {e.g., "Zustand"} | {e.g., "Lightweight, fits project size"} |
-```
-
-## Rules
-
-- Locked decisions are immutable once set — only the user can change them
-- Deferred ideas must NEVER appear in plans
-- Discretion areas are documented when the planner exercises choice
-- Phase-level CONTEXT.md files (in phase directories) override project-level for that phase
+# CONTEXT.md Template
+
+> Referenced by: begin skill (Step 9c), discuss skill, plan skill
+> Created during /pbr:begin. Updated by /pbr:discuss and /pbr:plan --assumptions.
+
+## Structure
+
+```markdown
+# Project Context
+
+## Locked Decisions
+
+{Technology choices, architecture decisions, and constraints that are NON-NEGOTIABLE.
+ These MUST be honored by every plan and executor — no exceptions.}
+
+| Decision | Rationale | Locked By |
+|----------|-----------|-----------|
+| {e.g., "Use TypeScript"} | {User preference, team skill} | User |
+| {e.g., "PostgreSQL via Supabase"} | {Existing infrastructure} | User |
+
+## User Constraints
+
+{Budget, timeline, skill level, hosting, team size — factors that shape planning}
+
+- {e.g., "Solo developer, no team"}
+- {e.g., "Deploy to Hetzner VPS"}
+- {e.g., "Must work offline"}
+
+## Deferred Ideas
+
+{Features explicitly moved to v2 or out-of-scope. Plans MUST NOT include these.}
+
+| Idea | Reason Deferred |
+|------|----------------|
+| {feature} | {reason} |
+
+## Claude's Discretion Areas
+
+{Areas where the planner can make implementation choices without asking the user.
+ Document the choice made and rationale when exercised.}
+
+| Area | Choice Made | Rationale |
+|------|------------|-----------|
+| {e.g., "State management library"} | {e.g., "Zustand"} | {e.g., "Lightweight, fits project size"} |
+```
+
+## Rules
+
+- Locked decisions are immutable once set — only the user can change them
+- Deferred ideas must NEVER appear in plans
+- Discretion areas are documented when the planner exercises choice
+- Phase-level CONTEXT.md files (in phase directories) override project-level for that phase