@sienklogic/plan-build-run 2.18.1 → 2.19.1

package/plugins/cursor-pbr/skills/config/SKILL.md

@@ -1,252 +0,0 @@
----
-name: config
-description: "Configure settings: depth, model profiles, features, git, and gates."
----
-
-## Step 0 — Immediate Output
-
-**Before ANY tool calls**, display this banner:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PLAN-BUILD-RUN ► CONFIGURATION                              ║
-╚══════════════════════════════════════════════════════════════╝
-```
-
-Then proceed to Step 1.
-
-# /pbr:config — Configure Plan-Build-Run
-
-## Overview
-
-Reads and writes `.planning/config.json`. Interactive configuration with AskUserQuestion.
-
-## References
-
-- `references/planning-config.md` — Full config.json schema (54 fields, 16 feature toggles, validation rules)
-- `references/model-profiles.md` — Model selection guide for agent spawning
-
-## Flow
-
-### 1. Load Current Config
-
-Read `.planning/config.json`. If it doesn't exist, display:
-```
-╔══════════════════════════════════════════════════════════════╗
-║  ERROR                                                       ║
-╚══════════════════════════════════════════════════════════════╝
-
-No Plan-Build-Run project found.
-
-**To fix:** Run `/pbr:begin` first.
-```
-
-### 2. Parse Arguments
-
-If `$ARGUMENTS` is provided, handle direct setting:
-- `depth quick|standard|comprehensive` — set depth directly
-- `model <agent> <model>` — set model for specific agent (e.g., `model executor sonnet`)
-- `model-profile quality|balanced|budget|adaptive` — set all models at once using a preset
-- `gate <gate-name> on|off` — toggle a gate
-- `feature <feature-name> on|off` — toggle a feature (e.g., `feature auto_continue on`). When the user specifies a feature name without the `features.` prefix, automatically prepend `features.` before writing to config.
-- `git branching none|phase|milestone|disabled` — set branching strategy
-- `git mode disabled` — disable git integration entirely
-- `show` — display current config (default when no args)
-
-### 3. Interactive Mode (no arguments or just `show`)
-
-Display current configuration in a readable format:
-
-```
-Plan-Build-Run Configuration
-=====================
-
-Workflow:
-  Depth: standard (balanced)
-    Research: on   Plan-check: on   Verify: on
-    Scan mappers: 4   Debug rounds: 5   Inline verify: off
-  Mode: interactive
-  Context Strategy: aggressive
-
-Features:
-  ✓ Structured planning    ✓ Goal verification
-  ✓ Context isolation       ✓ Atomic commits
-  ✓ Session persistence     ✓ Research phase
-  ✓ Plan checking           ✗ TDD mode
-  ✓ Status line             ✗ Auto-continue
-  ✗ Auto-advance           ✗ Team discussions
-
-Models:
-  Researcher: sonnet    Planner: inherit     Executor: inherit
-  Verifier: sonnet      Int-Checker: sonnet  Debugger: inherit
-  Mapper: sonnet        Synthesizer: haiku
-
-Parallelization:
-  Enabled: true    Max concurrent: 3
-  Plan-level: true  Task-level: false
-  Use Teams: false
-
-Git:
-  Mode: enabled      Branching: none
-  Commit docs: true
-  Commit format: {type}({phase}-{plan}): {description}
-
-Gates:
-  ✓ Confirm project   ✓ Confirm roadmap   ✓ Confirm plan
-  ✗ Confirm execute    ✓ Confirm transition ✓ Issues review
-
-Status Line:
-  Sections: [phase, plan, status, context]
-  Brand: PLAN-BUILD-RUN
-  Context bar: 20 chars, green<50%, yellow<80%
-
-Spinner Tips: (none configured — using defaults)
-```
-
-Then present the configuration menu using the **settings-category-select** pattern (see `skills/shared/gate-prompts.md`):
-
-Use AskUserQuestion:
-  question: "What would you like to configure?"
-  header: "Configure"
-  options:
-    - label: "Depth"          description: "quick/standard/comprehensive"
-    - label: "Model profile"  description: "quality/balanced/budget/adaptive"
-    - label: "Features"       description: "Toggle workflow features, gates, status line"
-    - label: "Git settings"   description: "branching strategy, commit mode"
-  multiSelect: false
-
-Note: The original 7 categories are condensed to 4. "Models" (per-agent) is accessible through "Model profile" with a follow-up option. "Gates", "Parallelization", and "Status Line" are grouped under "Features".
-
-**Follow-up based on selection:**
-
-If user selects "Depth":
-Use AskUserQuestion:
-  question: "Select workflow depth"
-  header: "Depth"
-  options:
-    - label: "Quick"           description: "Budget mode: skip research/plan-check/verifier, 2 scan mappers, ~1-3 fewer spawns per phase"
-    - label: "Standard"        description: "Balanced mode: conditional research, full plan-check and verification, 4 scan mappers (default)"
-    - label: "Comprehensive"   description: "Thorough mode: always research, always verify, inline verification, 4 scan mappers"
-  multiSelect: false
-
-After setting depth, the profile is automatically resolved. Show the user the effective settings:
-  "Depth set to {value}. Effective profile:"
-  Then display the profile summary (research, plan-check, verify, scan mappers, debug rounds, inline verify).
-
-To resolve the profile, run: `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js config resolve-depth`
-
-If the user wants to override a specific profile setting, they can set `depth_profiles.{depth}.{key}` directly.
-For example: to use quick mode but keep plan-checking, the user would set depth to quick and then override:
-  `/pbr:config` -> Features -> Plan checking -> Enable
-This writes `depth_profiles.quick.features.plan_checking: true` to config.json.
-
-If user selects "Model profile":
-Use the **model-profile-select** pattern:
-Use AskUserQuestion:
-  question: "Select model profile"
-  header: "Profile"
-  options:
-    - label: "Quality"    description: "opus for all agents (highest cost)"
-    - label: "Balanced"   description: "sonnet/inherit mix (default)"
-    - label: "Budget"     description: "haiku for all agents (lowest cost)"
-    - label: "Adaptive"   description: "sonnet planning, haiku execution"
-  multiSelect: false
-
-If user asks for per-agent model selection (typed "models" or "per-agent"), present individual agent selection as plain text: list the agents and ask which one to change, then ask for the model. This is a freeform flow because agent names are dynamic.
-
-If user selects "Features":
-List all features and gates with current status, then use the **toggle-confirm** pattern for each change.
-**Feature name normalization:** When toggling a feature, if the user specifies a bare name (e.g., `inline_verify`), normalize it to `features.inline_verify` before writing to config. All feature flags live under the `features.*` namespace in config.json.
-Use AskUserQuestion:
-  question: "Enable {feature_name}?"
-  header: "Toggle"
-  options:
-    - label: "Enable"   description: "Turn this feature on"
-    - label: "Disable"  description: "Turn this feature off"
-  multiSelect: false
-
-Repeat for each feature the user wants to change. Show updated status after each toggle.
-
-If user selects "Git settings":
-Use AskUserQuestion:
-  question: "Select branching strategy"
-  header: "Branching"
-  options:
-    - label: "None"        description: "All work on current branch"
-    - label: "Phase"       description: "New branch per phase"
-    - label: "Milestone"   description: "New branch per milestone"
-    - label: "Disabled"    description: "No git integration"
-  multiSelect: false
-
-If user types something else (freeform): interpret as a direct setting command and handle via Step 2 argument parsing logic.
-
-### 4. Apply Changes
-
-Update config.json with new values. Show what changed with a branded completion:
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PLAN-BUILD-RUN ► CONFIG UPDATED ✓                           ║
-╚══════════════════════════════════════════════════════════════╝
-
-Updated:
-  depth: standard → quick
-  models.executor: inherit → sonnet
-
-
-╔══════════════════════════════════════════════════════════════╗
-║  ▶ NEXT UP                                                   ║
-╚══════════════════════════════════════════════════════════════╝
-
-**Continue your workflow** — settings saved
-
-`/pbr:status`
-
-<sub>`/clear` first → fresh context window</sub>
-
-
-**Also available:**
-- `/pbr:continue` — execute next logical step
-- `/pbr:config` — change more settings
-
-```
-
-## Config Schema
-
-See `skills/begin/templates/config.json.tmpl` for the full schema with defaults.
-
-### Version Migration
-
-If config `version` is older than current (2), run migration:
-- v1 → v2: Add missing fields with defaults, rename `model_profile` → per-agent `models` object
-
-## Model Profile Presets
-
-The `model-profile` command sets all agent models at once:
-
-| Profile | researcher | planner | executor | verifier | int-checker | debugger | mapper | synthesizer |
-|---------|-----------|---------|----------|----------|-------------|----------|--------|-------------|
-| `quality` | opus | opus | opus | opus | sonnet | opus | sonnet | sonnet |
-| `balanced` | sonnet | inherit | inherit | sonnet | sonnet | inherit | sonnet | haiku |
-| `budget` | haiku | haiku | haiku | haiku | haiku | haiku | haiku | haiku |
-| `adaptive` | sonnet | sonnet | inherit | sonnet | haiku | inherit | haiku | haiku |
-
-`balanced` is the default and matches the initial config template. `adaptive` front-loads intelligence in research/planning and uses lighter models for mechanical work.
-
-## Feature Reference
-
-| Feature | Key | Default | Description |
-|---------|-----|---------|-------------|
-| Auto-continue | `features.auto_continue` | `false` | Automatically spawn continuation agents without user prompt |
-| Auto-advance | `features.auto_advance` | `false` | Chain build→review→plan automatically in autonomous mode |
-| Team discussions | `features.team_discussions` | `false` | Enable team-based discussion workflows |
-
-**Team boundaries**: Teams are NEVER used for execution, planning, or verification. Teams are only for discussion and brainstorming workflows. All execution, planning, and verification use single-agent Task() spawns with proper subagent types.
-
-## Validation
-
-- `depth` must be one of: quick, standard, comprehensive
-- `models.*` must be one of: sonnet, inherit, haiku, opus
-- `context_strategy` must be one of: aggressive, balanced, minimal
-- `git.branching` must be one of: none, phase, milestone, disabled
-- `git.mode` must be one of: enabled, disabled. When `disabled`, no git commands are run (no commits, no branching). Useful for prototyping or non-git projects.
-- Boolean fields must be true/false

package/plugins/cursor-pbr/skills/continue/SKILL.md

@@ -1,159 +0,0 @@
----
-name: continue
-description: "Execute the next logical step automatically. No prompts, no decisions — just do it."
----
-
-# /pbr:continue — Action-Oriented Resumption
-
-You are running the **continue** skill. Unlike `/pbr:resume` which shows status and suggests actions, `/pbr:continue` determines and EXECUTES the next logical step automatically.
-
-This skill runs **inline** and may delegate to other skills via agent invocation.
-
----
-
-## Step 0 — Immediate Output
-
-**Before ANY tool calls**, display this banner:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PLAN-BUILD-RUN ► NEXT STEP                                  ║
-╚══════════════════════════════════════════════════════════════╝
-```
-
-Then proceed to Step 1.
-
-## Context Budget
-
-Reference: `skills/shared/context-budget.md` for the universal orchestrator rules.
-
-Additionally for this skill:
-- **Minimize** state reads — read only STATE.md lines 1-20 to determine next action
-- **Delegate** execution to the appropriate skill
-
----
-
-## Core Principle
-
-**Do, don't ask.** Read STATE.md, determine the next action, and execute it. The user wants hands-off forward progress.
-
----
-
-## Flow
-
-### Step 1: Read State
-
-Read `.planning/STATE.md` and determine current position:
-- Current phase number and name
-- Current plan progress
-- Phase status (planning, building, reviewing, complete)
-
-If STATE.md doesn't exist, display:
-```
-ERROR
-
-No project state found.
-
-**To fix:** Run `/pbr:begin` first.
-```
-
-#### Context Budget Guard
-
-Before proceeding to priority evaluation, check for runaway continue chains:
-
-1. Read `last_command` from STATE.md. **If `last_command` is missing, empty, or the field does not exist, skip directly to the fallback detection** — do NOT error or warn.
-2. If `last_command` is present and equals `/pbr:continue`, this is a chained continue. Check session context for consecutive `/pbr:continue` invocations.
-3. **Fallback detection** — if `last_command` is not available or not present in STATE.md:
-   - Check `.planning/.active-skill` file — if it contains `continue`, treat as a chained continue
-   - Check STATE.md `last_action` field — if it contains `continue`, treat as a chained continue
-   - If neither source is available, assume this is the first invocation (do not warn)
-4. **If this is the 3rd consecutive `/pbr:continue` in a row**, display:
-
-```
-WARNING: Context budget warning: 3 consecutive auto-continues detected.
-Recommend running /pbr:pause then resuming in a fresh session.
-```
-
-Then present the user with a choice:
-- **"Continue"** — proceed with the next action
-- **"Pause"** — run `/pbr:pause` logic to save state and stop
-
-This prevents runaway chains that fill the context window without a human checkpoint.
-
-### Step 2: Scan for Priority Items
-
-Check the resumption priority hierarchy (same as /pbr:resume):
-
-1. **UAT Blockers**: VERIFICATION.md with `status: gaps_found` -> Execute `/pbr:plan {N} --gaps`
-2. **Checkpoint pending**: `.checkpoint-manifest.json` with pending items -> Resume the build
-3. **Continue-here file**: `.continue-here.md` exists -> Follow its next step
-4. **Incomplete build**: PLAN.md files without SUMMARY.md -> Execute `/pbr:build {N}`
-5. **Unverified phase**: All plans complete, no VERIFICATION.md -> Execute `/pbr:review {N}`
-6. **Phase complete, more phases exist**: Verification passed -> Execute `/pbr:plan {N+1}`
-7. **All phases complete**: Verification passed on final phase, no more phases in ROADMAP.md -> Stop. Display: "All phases are complete. Run `/pbr:milestone audit` to verify cross-phase integration, or `/pbr:milestone complete` to archive this milestone."
-
-### Step 3: Execute
-
-Based on the determined action, display the delegation indicator to the user:
-```
-Delegating to /pbr:{skill} {args}...
-```
-
-Then invoke the appropriate skill. **NEVER read SKILL.md files into your context** — this wastes the main context budget with 500+ lines of instructions. Instead, invoke the skill directly:
-
-| Situation | Action | Skill to invoke |
-|-----------|--------|-----|
-| Gaps need closure | Plan gap closure | `/pbr:plan {N} --gaps` |
-| Build incomplete | Continue build | `/pbr:build {N}` |
-| Review needed | Run review | `/pbr:review {N}` |
-| Next phase needed | Plan next phase | `/pbr:plan {N+1}` |
-| Project not started | Plan phase 1 | `/pbr:plan 1` |
-
-Where `{N}` is the current phase number determined from STATE.md in Step 1.
-
-### Step 4: Report and Chain
-
-After execution completes, display a branded completion:
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PLAN-BUILD-RUN ► STEP COMPLETE                              ║
-╚══════════════════════════════════════════════════════════════╝
-
-Completed: {what was done}
-
----
-
-## Next Up
-
-**{Next action description}**
-
-`/pbr:continue` or `{specific command}`
-
----
-```
-
-**If `features.auto_advance` is `true` AND `mode` is `autonomous`:**
-After the delegated skill completes, immediately re-run Step 1-3 to determine and execute the NEXT action. Continue chaining until a hard stop is reached. This enables hands-free phase cycling: build->review->plan->build->...
-
----
-
-## Hard Stops
-
-Do NOT auto-continue when:
-- `config.mode` is NOT `autonomous` and a gate confirmation is needed
-- A checkpoint requires human input (decision, verify, action)
-- An error occurred during execution
-- The milestone is complete
-- Verification found gaps (need user review before advancing)
-
-In these cases, explain why auto-continue stopped and what the user needs to do.
-
----
-
-## Anti-Patterns
-
-1. **DO NOT** ask the user what to do — determine it from state
-2. **DO NOT** skip error handling — if something fails, stop and report
-3. **DO NOT** continue past checkpoints that need human input
-4. **DO NOT** auto-continue into a new milestone — that needs user initiation
-5. **DO NOT** modify STATE.md directly — let the delegated skill handle it

package/plugins/cursor-pbr/skills/dashboard/SKILL.md

@@ -1,44 +0,0 @@
----
-name: dashboard
-description: "Launch the PBR web dashboard for the current project."
-argument-hint: "[--port N]"
----
-
-## Step 0 — Immediate Output
-
-**Before ANY tool calls**, display this banner:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PLAN-BUILD-RUN ► DASHBOARD                                  ║
-╚══════════════════════════════════════════════════════════════╝
-```
-
-Then proceed to Step 1.
-
-## Behavior
-
-1. **Parse arguments**: Extract `--port N` from the user's input. Default to `3000`.
-
-2. **Locate dashboard**: The dashboard lives at `../../dashboard/` relative to this plugin's root directory (i.e. two levels up from `plugins/cursor-pbr/`). Resolve the absolute path.
-
-3. **Check dependencies**: Check if `node_modules/` exists in the dashboard directory. If not, run:
-   ```
-   npm install --prefix <dashboard-dir>
-   ```
-
-4. **Launch dashboard**: Run in background:
-   ```
-   node <dashboard-dir>/bin/cli.js --dir <cwd> --port <port> &
-   ```
-
-5. **Output to user**:
-   ```
-   Dashboard running at http://localhost:<port>
-   Open this URL in your browser to view your project's planning state.
-   ```
-
-## Notes
-
-- If the port is already in use, the dashboard will fail to start — suggest the user try a different port with `--port`.
-- The dashboard watches `.planning/` for live updates via SSE.