cursorqb-subplanner

# CursorQB Sub-Planner Decompose `Planner-docs/Main-Planing.md` into detailed per-phase sub-plans. This is planning-only work. ## Sources - Primary source: `Planner-docs/Main-Planing.md`. - Optional supporting sources: `Planner-docs/Autopsy.md`, `Planner-docs/Project-Ontology.md`, `Planner-docs/Project-Comprehension.md`, and `Planner-docs/Planing-Ledger.md`. - Reliability reference: `references/workflow-quality.md`. - Full Step 2 spec: `second-planner.md`. - Validator entrypoint: `scripts/cursorqb_launcher.py --controller planner-validator`. `Autopsy.md` is not a replacement for Main-Planing.md. Optional continuity docs enrich the plan but never override current repo evidence or explicit user intent. ## Language Contract CursorQB asks intake questions in the user's language when practical. Generated Planner-docs artifacts are English by default unless the user explicitly requests another body language. Required document headings remain English for validator stability. ## Plan-Run Contract Use Cursor Plan Mode and bind this run through the bundled deterministic Plan-Run controller: - Outcome: every main phase has a matching `Planner-docs/Faz-<n>-Plans/` folder, one or more conforming `Faz<n>.<m>-*.md` sub-plans, a complete `Planner-docs/Sub-Planing-Index.md`, and a v3 `Planner-docs/Planing-Ledger.md` with separate planning, implementation, validation, and review fields. - Files allowed to modify: only `Planner-docs/` files created or updated by Step 2. - Files forbidden to modify: source, config, tests, scripts, docs outside `Planner-docs/`, and `Planner-docs/Main-Planing.md`. - Required sources to read: Main plan, workflow quality reference, optional Autopsy/Ontology/Comprehension, and any prior Ledger when present; the output Ledger is mandatory. - Validation checkpoints: run `python3 -I -S -B <plugin-root>/scripts/cursorqb_launcher.py --controller planner-validator -- --root . --mode step2 --strict`. - Stop gates: missing main plan, undecomposable phase roadmap, repository read errors, unrelated dirty worktree, or validation failure without a clear fix. - Subagent policy: use bounded read-only or planning-only subagents only for large repo exploration, ontology mapping, phase drafting, or review; parent CursorQB writes official artifacts. - Token/context risk: read only needed files and continue phase by phase until all phases are covered. ## Required Behavior 1. Read `second-planner.md` fully. 2. Read `Main-Planing.md` fully and extract the ordered phase list. 3. Read `Autopsy.md`, `Project-Ontology.md`, `Project-Comprehension.md`, and `Planing-Ledger.md` when present. 4. Do not modify Planner-docs/Main-Planing.md. 5. If `Main-Planing.md` is missing, inconsistent, incomplete, or impossible to decompose, create `Planner-docs/Step2-Blocked.md` and stop. 6. Plan in a vibecoding-first style: small reversible slices, fast validation signals, explicit deferrals, secure boundaries, and room for discovery during Step 4. 7. Avoid duplicating ledger work already marked `implemented`, `verified`, or `superseded` unless repo evidence or user intent requires replanning. 8. Create/update the artifact-schema-v3 `Planner-docs/Sub-Planing-Index.md` with full relative-path references, execution waves, traceability, decisions, framework ownership, and invariants. 9. Emit exactly one valid machine-readable Implementation Contract in every sub-plan. 10. Create or refresh `Planner-docs/Planing-Ledger.md`; preserve trustworthy prior evidence and initialize every new contract's independent state fields. 11. Validate all generated files; do not sample. ## Completion Report Report whether Step 2 succeeded or blocked, phase count, sub-plan count, changed files, validator result, first recommended Step 3 action, and confirmation that `Planner-docs/Main-Planing.md` was not modified.