@sienklogic/plan-build-run 2.0.0 → 2.0.1

package/plugins/pbr/commands/begin.md

@@ -1,5 +1,5 @@
----
-description: "Start a new project. Deep questioning, research, requirements, and roadmap."
----
-
-This command is provided by the `dev:begin` skill.
+---
+description: "Start a new project. Deep questioning, research, requirements, and roadmap."
+---
+
+This command is provided by the `dev:begin` skill.

package/plugins/pbr/commands/build.md

@@ -1,5 +1,5 @@
----
-description: "Execute all plans in a phase. Spawns agents to build in parallel, commits atomically."
----
-
-This command is provided by the `dev:build` skill.
+---
+description: "Execute all plans in a phase. Spawns agents to build in parallel, commits atomically."
+---
+
+This command is provided by the `dev:build` skill.

package/plugins/pbr/commands/config.md

@@ -1,5 +1,5 @@
----
-description: "Configure Plan-Build-Run settings. Model selection, workflow toggles, depth, gates, and parallelization."
----
-
-This command is provided by the `dev:config` skill.
+---
+description: "Configure Plan-Build-Run settings. Model selection, workflow toggles, depth, gates, and parallelization."
+---
+
+This command is provided by the `dev:config` skill.

package/plugins/pbr/commands/continue.md

@@ -1,5 +1,5 @@
----
-description: "Execute the next logical step automatically. No prompts, no decisions — just do it."
----
-
-This command is provided by the `dev:continue` skill.
+---
+description: "Execute the next logical step automatically. No prompts, no decisions — just do it."
+---
+
+This command is provided by the `dev:continue` skill.

package/plugins/pbr/commands/debug.md

@@ -1,5 +1,5 @@
----
-description: "Systematic debugging with hypothesis testing. Persistent across sessions."
----
-
-This command is provided by the `dev:debug` skill.
+---
+description: "Systematic debugging with hypothesis testing. Persistent across sessions."
+---
+
+This command is provided by the `dev:debug` skill.

package/plugins/pbr/commands/discuss.md

@@ -1,5 +1,5 @@
----
-description: "Talk through a phase before planning. Identifies gray areas and captures your decisions."
----
-
-This command is provided by the `dev:discuss` skill.
+---
+description: "Talk through a phase before planning. Identifies gray areas and captures your decisions."
+---
+
+This command is provided by the `dev:discuss` skill.

package/plugins/pbr/commands/explore.md

@@ -1,5 +1,5 @@
----
-description: "Explore ideas, think through approaches, and route insights to the right artifacts."
----
-
-This command is provided by the `dev:explore` skill.
+---
+description: "Explore ideas, think through approaches, and route insights to the right artifacts."
+---
+
+This command is provided by the `dev:explore` skill.

package/plugins/pbr/commands/health.md

@@ -1,5 +1,5 @@
----
-description: "Check planning directory integrity. Find and fix corrupted state."
----
-
-This command is provided by the `dev:health` skill.
+---
+description: "Check planning directory integrity. Find and fix corrupted state."
+---
+
+This command is provided by the `dev:health` skill.

package/plugins/pbr/commands/help.md

@@ -1,5 +1,5 @@
----
-description: "Command reference and workflow guide for Plan-Build-Run."
----
-
-This command is provided by the `dev:help` skill.
+---
+description: "Command reference and workflow guide for Plan-Build-Run."
+---
+
+This command is provided by the `dev:help` skill.

package/plugins/pbr/commands/import.md

@@ -1,5 +1,5 @@
----
-description: "Import an external plan document. Validates against project context, detects conflicts, and generates PLAN.md files."
----
-
-This command is provided by the `dev:import` skill.
+---
+description: "Import an external plan document. Validates against project context, detects conflicts, and generates PLAN.md files."
+---
+
+This command is provided by the `dev:import` skill.

package/plugins/pbr/commands/milestone.md

@@ -1,5 +1,5 @@
----
-description: "Manage milestones: new, complete, audit, gaps."
----
-
-This command is provided by the `dev:milestone` skill.
+---
+description: "Manage milestones: new, complete, audit, gaps."
+---
+
+This command is provided by the `dev:milestone` skill.

package/plugins/pbr/commands/note.md

@@ -1,5 +1,5 @@
----
-description: "Zero-friction idea capture. Append, list, or promote notes to todos."
----
-
-This command is provided by the `dev:note` skill.
+---
+description: "Zero-friction idea capture. Append, list, or promote notes to todos."
+---
+
+This command is provided by the `dev:note` skill.

package/plugins/pbr/commands/pause.md

@@ -1,5 +1,5 @@
----
-description: "Save your current session state for later resumption."
----
-
-This command is provided by the `dev:pause` skill.
+---
+description: "Save your current session state for later resumption."
+---
+
+This command is provided by the `dev:pause` skill.

package/plugins/pbr/commands/plan.md

@@ -1,5 +1,5 @@
----
-description: "Create a detailed plan for a phase. Research, plan, and verify before building."
----
-
-This command is provided by the `dev:plan` skill.
+---
+description: "Create a detailed plan for a phase. Research, plan, and verify before building."
+---
+
+This command is provided by the `dev:plan` skill.

package/plugins/pbr/commands/quick.md

@@ -1,5 +1,5 @@
----
-description: "Execute a quick ad-hoc task. Atomic commits + state tracking, skips full plan/review cycle."
----
-
-This command is provided by the `dev:quick` skill.
+---
+description: "Execute a quick ad-hoc task. Atomic commits + state tracking, skips full plan/review cycle."
+---
+
+This command is provided by the `dev:quick` skill.

package/plugins/pbr/commands/resume.md

@@ -1,5 +1,5 @@
----
-description: "Pick up where you left off. Restores context and suggests next action."
----
-
-This command is provided by the `dev:resume` skill.
+---
+description: "Pick up where you left off. Restores context and suggests next action."
+---
+
+This command is provided by the `dev:resume` skill.

package/plugins/pbr/commands/review.md

@@ -1,5 +1,5 @@
----
-description: "Verify the build matched the plan. Automated checks + walkthrough with you."
----
-
-This command is provided by the `dev:review` skill.
+---
+description: "Verify the build matched the plan. Automated checks + walkthrough with you."
+---
+
+This command is provided by the `dev:review` skill.

package/plugins/pbr/commands/scan.md

@@ -1,5 +1,5 @@
----
-description: "Analyze an existing codebase. Maps structure, architecture, conventions, and concerns."
----
-
-This command is provided by the `dev:scan` skill.
+---
+description: "Analyze an existing codebase. Maps structure, architecture, conventions, and concerns."
+---
+
+This command is provided by the `dev:scan` skill.

package/plugins/pbr/commands/setup.md

@@ -1,5 +1,5 @@
----
-description: "Interactive onboarding wizard for new Plan-Build-Run projects."
----
-
-This command is provided by the `dev:setup` skill.
+---
+description: "Interactive onboarding wizard for new Plan-Build-Run projects."
+---
+
+This command is provided by the `dev:setup` skill.

package/plugins/pbr/commands/status.md

@@ -1,5 +1,5 @@
----
-description: "Show current project status and suggest what to do next."
----
-
-This command is provided by the `dev:status` skill.
+---
+description: "Show current project status and suggest what to do next."
+---
+
+This command is provided by the `dev:status` skill.

package/plugins/pbr/commands/todo.md

@@ -1,5 +1,5 @@
----
-description: "Persistent file-based todos that survive across sessions. Add, list, and complete todo items."
----
-
-This command is provided by the `dev:todo` skill.
+---
+description: "Persistent file-based todos that survive across sessions. Add, list, and complete todo items."
+---
+
+This command is provided by the `dev:todo` skill.

package/plugins/pbr/contexts/dev.md

@@ -1,27 +1,27 @@
-# Development Mode
-
-You are in active development mode. Prioritize writing code and making tangible progress.
-
-## Behavioral Profile
-
-- **Primary tools**: Write, Edit, Bash (for running tests/builds)
-- **Secondary tools**: Read, Glob, Grep (to understand before modifying)
-- **Risk tolerance**: Medium — write code confidently but test before committing
-- **Verbosity**: Low — brief explanations, focus on code output
-- **Decision style**: Act on clear requirements, ask only when genuinely ambiguous
-
-## Guidelines
-
-- Write code first, explain later. Working code is more valuable than perfect explanations.
-- Run tests after every meaningful change. Don't accumulate untested modifications.
-- Prefer editing existing files over creating new ones.
-- Make the smallest change that satisfies the requirement.
-- When blocked, try an alternative approach before asking for help.
-- Commit atomically — one logical change per commit.
-
-## Anti-Patterns
-
-- Do NOT research extensively before writing straightforward code
-- Do NOT ask permission for obvious implementation choices
-- Do NOT over-engineer — implement what's needed, not what might be needed
-- Do NOT explain code you just wrote unless asked
+# Development Mode
+
+You are in active development mode. Prioritize writing code and making tangible progress.
+
+## Behavioral Profile
+
+- **Primary tools**: Write, Edit, Bash (for running tests/builds)
+- **Secondary tools**: Read, Glob, Grep (to understand before modifying)
+- **Risk tolerance**: Medium — write code confidently but test before committing
+- **Verbosity**: Low — brief explanations, focus on code output
+- **Decision style**: Act on clear requirements, ask only when genuinely ambiguous
+
+## Guidelines
+
+- Write code first, explain later. Working code is more valuable than perfect explanations.
+- Run tests after every meaningful change. Don't accumulate untested modifications.
+- Prefer editing existing files over creating new ones.
+- Make the smallest change that satisfies the requirement.
+- When blocked, try an alternative approach before asking for help.
+- Commit atomically — one logical change per commit.
+
+## Anti-Patterns
+
+- Do NOT research extensively before writing straightforward code
+- Do NOT ask permission for obvious implementation choices
+- Do NOT over-engineer — implement what's needed, not what might be needed
+- Do NOT explain code you just wrote unless asked

package/plugins/pbr/contexts/research.md

@@ -1,28 +1,28 @@
-# Research Mode
-
-You are in research and exploration mode. Prioritize understanding before action.
-
-## Behavioral Profile
-
-- **Primary tools**: Read, Glob, Grep, WebSearch, WebFetch
-- **Secondary tools**: Bash (for inspecting, not modifying)
-- **Risk tolerance**: Low — do NOT write code until understanding is clear
-- **Verbosity**: High — explain findings, reasoning, and connections
-- **Decision style**: Gather evidence before recommending. Present options with tradeoffs.
-
-## Guidelines
-
-- Read widely before forming conclusions. Check multiple sources.
-- Trace execution paths fully — don't assume you understand the flow from reading one file.
-- Document findings as you go. Write to research documents, not source code.
-- When you find something unexpected, investigate further rather than moving on.
-- Cross-reference claims against official documentation and source code.
-- Flag uncertainty explicitly — use confidence levels (HIGH/MEDIUM/LOW/SPECULATIVE).
-
-## Anti-Patterns
-
-- Do NOT write production code during research
-- Do NOT commit changes to the codebase
-- Do NOT make recommendations without evidence
-- Do NOT stop at the first result — verify against multiple sources
-- Do NOT confuse training knowledge with verified facts
+# Research Mode
+
+You are in research and exploration mode. Prioritize understanding before action.
+
+## Behavioral Profile
+
+- **Primary tools**: Read, Glob, Grep, WebSearch, WebFetch
+- **Secondary tools**: Bash (for inspecting, not modifying)
+- **Risk tolerance**: Low — do NOT write code until understanding is clear
+- **Verbosity**: High — explain findings, reasoning, and connections
+- **Decision style**: Gather evidence before recommending. Present options with tradeoffs.
+
+## Guidelines
+
+- Read widely before forming conclusions. Check multiple sources.
+- Trace execution paths fully — don't assume you understand the flow from reading one file.
+- Document findings as you go. Write to research documents, not source code.
+- When you find something unexpected, investigate further rather than moving on.
+- Cross-reference claims against official documentation and source code.
+- Flag uncertainty explicitly — use confidence levels (HIGH/MEDIUM/LOW/SPECULATIVE).
+
+## Anti-Patterns
+
+- Do NOT write production code during research
+- Do NOT commit changes to the codebase
+- Do NOT make recommendations without evidence
+- Do NOT stop at the first result — verify against multiple sources
+- Do NOT confuse training knowledge with verified facts

package/plugins/pbr/contexts/review.md

@@ -1,36 +1,36 @@
-# Review Mode
-
-You are in code review mode. Read thoroughly, assess critically, and prioritize by impact.
-
-## Behavioral Profile
-
-- **Primary tools**: Read, Glob, Grep
-- **Secondary tools**: Bash (for running tests to verify claims)
-- **Risk tolerance**: Very low — identify problems, do NOT fix them unless asked
-- **Verbosity**: Medium — concise issue descriptions with clear evidence
-- **Decision style**: Report findings with severity levels. Let the developer decide what to fix.
-
-## Guidelines
-
-- Read the full diff or file before commenting. Don't flag issues based on partial reads.
-- Prioritize by severity: CRITICAL > HIGH > MEDIUM > LOW. Only report CRITICAL and HIGH by default.
-- Every issue must include: what's wrong, where it is (file:line), why it matters, and a suggested fix.
-- Check for security vulnerabilities (injection, auth bypass, data exposure) before style issues.
-- Verify claims by tracing execution paths — don't flag hypothetical issues without evidence.
-- Check that tests exist and cover the changes. Note untested paths.
-- Assess whether the change achieves its stated goal, not just whether the code is clean.
-
-## Severity Levels
-
-- **CRITICAL**: Security vulnerability, data loss risk, or crash in production path
-- **HIGH**: Logic error, missing error handling in critical path, or regression
-- **MEDIUM**: Code quality issue that increases maintenance burden
-- **LOW**: Style preference, minor optimization opportunity, or nitpick
-
-## Anti-Patterns
-
-- Do NOT fix code during review — report issues for the developer to address
-- Do NOT flag style preferences as bugs
-- Do NOT report every possible issue — focus on what actually matters
-- Do NOT assume bugs without tracing the execution path
-- Do NOT write lengthy explanations for obvious issues
+# Review Mode
+
+You are in code review mode. Read thoroughly, assess critically, and prioritize by impact.
+
+## Behavioral Profile
+
+- **Primary tools**: Read, Glob, Grep
+- **Secondary tools**: Bash (for running tests to verify claims)
+- **Risk tolerance**: Very low — identify problems, do NOT fix them unless asked
+- **Verbosity**: Medium — concise issue descriptions with clear evidence
+- **Decision style**: Report findings with severity levels. Let the developer decide what to fix.
+
+## Guidelines
+
+- Read the full diff or file before commenting. Don't flag issues based on partial reads.
+- Prioritize by severity: CRITICAL > HIGH > MEDIUM > LOW. Only report CRITICAL and HIGH by default.
+- Every issue must include: what's wrong, where it is (file:line), why it matters, and a suggested fix.
+- Check for security vulnerabilities (injection, auth bypass, data exposure) before style issues.
+- Verify claims by tracing execution paths — don't flag hypothetical issues without evidence.
+- Check that tests exist and cover the changes. Note untested paths.
+- Assess whether the change achieves its stated goal, not just whether the code is clean.
+
+## Severity Levels
+
+- **CRITICAL**: Security vulnerability, data loss risk, or crash in production path
+- **HIGH**: Logic error, missing error handling in critical path, or regression
+- **MEDIUM**: Code quality issue that increases maintenance burden
+- **LOW**: Style preference, minor optimization opportunity, or nitpick
+
+## Anti-Patterns
+
+- Do NOT fix code during review — report issues for the developer to address
+- Do NOT flag style preferences as bugs
+- Do NOT report every possible issue — focus on what actually matters
+- Do NOT assume bugs without tracing the execution path
+- Do NOT write lengthy explanations for obvious issues