openplanr 1.25.3 → 2.0.1

package/dist/templates/rules/cursor/planr-pipeline-ship.mdc.hbs

@@ -1,246 +0,0 @@
----
-description: "Planr Pipeline — DEV Phase orchestration (ship {feature}). Frontend ‖ backend → qa → devops ‖ doc-gen → snapshot → marker."
-globs: []
-alwaysApply: false
----
-
-# /ship {feature} — DEV Phase orchestration (Cursor)
-
-When the user says **"ship {feature}"** (or "implement {feature}", "build
-{feature}"), follow this rule end-to-end. The argument `{feature}` is the
-feature slug.
-
-**Per R1, this command MUST NOT be auto-chained from "plan {feature}".**
-The user must explicitly invoke it after reviewing the PO-phase output.
-
----
-
-## Step 0 — Snapshot sentinel
-
-Cursor has no Stop hook (unlike Claude Code). To approximate the same
-"reminder if /ship aborts before snapshot" guarantee, write
-`.cursor/.snapshot-pending` (empty file) at the start of this rule. If a
-later run encounters this sentinel, surface a one-line reminder to refresh
-`CLAUDE.md` (Step 5) before proceeding.
-
----
-
-## Step 1 — Mode detection + input validation
-
-### 1a — Detect planr spec mode
-
-Same as `planr-pipeline-plan.mdc` Step 1a:
-
-1. If `.planr/config.json` has `idPrefix.spec` set, **spec-driven mode**.
-2. `SPEC_DIR = .planr/specs/<SPEC-NNN-{feature}>/`.
-3. Otherwise, **default mode** (`output/feats/feat-{feature}/`).
-
-| Concept | Default | Spec-driven |
-|---|---|---|
-| Feature root | `output/feats/feat-{feature}/` | `<SPEC_DIR>/` |
-| US files | `output/feats/feat-{feature}/us-*/us-*.md` | `<SPEC_DIR>/stories/US-*.md` |
-| Task files | `output/feats/feat-{feature}/us-*/tasks/task-*.md` | `<SPEC_DIR>/tasks/T-*.md` |
-| Error report | `output/feats/feat-{feature}/us-{N}/tasks/error-report.md` | `<SPEC_DIR>/tasks/error-report.md` |
-| QA report | `output/feats/feat-{feature}/qa-report.md` | `<SPEC_DIR>/qa-report.md` |
-
-### 1b — Validate required inputs
-
-Verify these exist (mode-appropriate). Abort with clear errors if missing.
-
-Required (default mode):
-- `output/feats/feat-{feature}/` — fail: "feat-{feature}/ not found. Run plan {feature} first."
-- ≥1 `output/feats/feat-{feature}/us-*/us-*.md`
-- ≥1 `output/feats/feat-{feature}/us-*/tasks/task-*.md`
-- `input/tech/stack.md`
-
-Required (spec-driven mode):
-- `<SPEC_DIR>/` — fail: "Spec for slug '{feature}' not found under .planr/specs/. Run plan {feature} first."
-- ≥1 `<SPEC_DIR>/stories/US-*.md`
-- ≥1 `<SPEC_DIR>/tasks/T-*.md`
-- `input/tech/stack.md` — see self-heal below.
-
-### Self-healing in spec mode
-
-When MODE=spec-driven AND `input/tech/stack.md` is missing:
-
-1. Read `{{cursorRulesRoot}}/templates/stack.md.tpl` and write to `input/tech/stack.md`.
-2. Print "edit and re-run" message.
-3. Abort gracefully. Do NOT invoke any role.
-
-In default mode, missing `stack.md` aborts with the same template guidance.
-
----
-
-## Step 2 — Iterate User Stories in topological order
-
-In default mode, iterate each `us-{N}` directory under
-`output/feats/feat-{feature}/` (sorted by US number). In spec-driven mode,
-iterate each `<SPEC_DIR>/stories/US-*.md` (sorted by ID); tasks live in the
-**flat** `<SPEC_DIR>/tasks/` directory and link to their parent story via
-the `storyId` frontmatter field.
-
-For each story, run its tasks:
-
-1. Read the US file to identify which tasks belong to it.
-2. **Read project memory:** if `.planr/memory.md` exists, keyword-match relevant entries against the current task's file list. Include matched traps/decisions/corrections in the subagent's context.
-3. For each task:
-   - Read frontmatter `Type` and `status` fields.
-   - Skip tasks with `status: done`. Enqueue `pending`, `in-progress` (recover), `blocked` (retry).
-   - If `Type: UI` → dispatch the **frontend** subagent
-     (`{{cursorRulesRoot}}/agents/frontend-agent.md`).
-   - If `Type: Tech` → dispatch the **backend** subagent
-     (`{{cursorRulesRoot}}/agents/backend-agent.md`).
-   - frontend and backend tasks within the SAME US may run in parallel
-     (Cursor's Composer supports parallel subagent dispatch — use it).
-4. Each subagent applies the **3-iteration correction loop** (R6):
-   - Iteration 1: direct fix on build/test failure.
-   - Iteration 2: re-read task spec + design-spec/schema, fix holistically.
-   - Iteration 3: minimal safe fix, flag remaining issues.
-   - On entering iteration 2: append a trap entry to `.planr/memory.md` under `## Traps`.
-   - On 3rd failure: write `T-NNN-error-report.md` (default mode:
-     `output/feats/feat-{feature}/us-{N}/tasks/T-NNN-error-report.md`; spec mode:
-     `<SPEC_DIR>/tasks/T-NNN-error-report.md`). Then STOP that task.
-4. If a task fails after 3 iterations, ship continues with other independent
-   tasks but flags the failed task in the final summary.
-
----
-
-## Step 3 — QA Gate
-
-After all US tasks complete (or fail with error-reports), dispatch the
-**qa** subagent (`{{cursorRulesRoot}}/agents/qa-agent.md`).
-
-The qa subagent verifies, for each task:
-- All "Create" files exist
-- All "Modify" files were updated (and only as described)
-- All "Preserve" files are unchanged (`git diff` vs base)
-- Tests pass (`BuildCommand` + `TestCommand` from `stack.md`)
-- If task has `rationale:`, check implementation drift vs stated intent (non-blocking warning)
-- DoD checklist items satisfied
-
-If QA fails: flag in summary; **still proceed to Step 5 snapshot** so state
-is recorded; skip Step 4 (devops + doc-gen) until the underlying task is fixed.
-
----
-
-## Step 4 — devops + doc-gen subagents (parallel, optional)
-
-Run only if QA passes.
-
-- Dispatch **devops** subagent
-  (`{{cursorRulesRoot}}/agents/devops-agent.md`) — generates
-  `docker-compose.yml`, `.env.example`, Dockerfiles, CI workflow stubs.
-  **No `Bash` whatsoever** (prompt-level enforcement on Cursor).
-- Dispatch **doc-gen** subagent
-  (`{{cursorRulesRoot}}/agents/doc-gen-agent.md`) — writes
-  `Docs/feat-{feature}/` from US, tasks, generated source code.
-
----
-
-## Step 5 — Snapshot
-
-Refresh `CLAUDE.md` at the project root. Read
-`{{cursorRulesRoot}}/templates/CLAUDE.md.tpl` and write a populated copy.
-
-Capture in this order:
-
-1. **Project Identity** — `AppName`, `Version`, `DatabaseType`, `Framework`,
-   `Language` from `input/tech/stack.md`. Include ISO 8601 UTC timestamp.
-2. **Phase Status** — scan filesystem to determine actual state.
-3. **Feature Registry** — for each feature folder.
-4. **Active Roles** — list the 8 roles with their model tier.
-5. **Build Log** — append latest build/test outcomes (append-only — never truncate).
-6. **Known Issues** — scan all `error-report.md` files.
-7. **Stack Summary** — embed `input/tech/stack.md` content.
-
-### Snapshot integrity rules
-
-- ✅ Always write a complete, valid `CLAUDE.md` — never partial.
-- ✅ Always include the generation timestamp.
-- ✅ Preserve existing build log entries (append only).
-- ✅ If a scan section fails, write `[scan error]` rather than empty.
-- ❌ Never delete `CLAUDE.md`.
-- ❌ Never leave `CLAUDE.md` partially written.
-
-### Coexistence with planr-managed CLAUDE.md
-
-If the existing `CLAUDE.md` opens with `> Generated by OpenPlanr` or contains
-`## Context-Gathering Protocol`, do **not** overwrite. Print:
-*"CLAUDE.md is planr-managed; pipeline state recorded via .pipeline-shipped
-marker (Step 5.5) and qa-report.md."* Continue to Step 5.5.
-
-After writing (or skipping), remove `.cursor/.snapshot-pending`.
-
----
-
-## Step 5.5 — Write the `.pipeline-shipped` marker
-
-After Step 5 succeeds, write a marker file recording the pipeline run.
-
-**Default mode:** `output/feats/feat-{feature}/.pipeline-shipped`
-**Spec-driven mode:** `<SPEC_DIR>/.pipeline-shipped`
-
-YAML contents:
-
-```yaml
-shipped_at: "<ISO 8601 UTC timestamp>"
-pipeline_version: "<runtime adapter writes its own version, e.g. 0.6.0>"
-protocol_version: "{{protocolVersion}}"
-runtime: "cursor"
-mode: "<default | spec-driven>"
-feature: "{feature}"
-tasks_executed: <integer>
-tasks_failed: <integer>
-qa_gate_status: "<passed | failed | skipped>"
-duration_seconds: <integer>
-agents_invoked:
-  - frontend-agent          # only list roles that actually ran
-  - backend-agent
-  - qa-agent
-  - devops-agent
-  - doc-gen-agent
-devops_status: "<generated | skipped>"
-docs_status: "<generated | skipped>"
-snapshot_status: "<refreshed | skipped>"
-error_reports:               # paths to any error-report.md files; [] if none
-  - <path>
-```
-
-If Step 5 (snapshot) was skipped due to planr-managed CLAUDE.md, set
-`snapshot_status: skipped` so the partial-success state is recorded.
-
----
-
-## Step 6 — Print summary
-
-```
-✓ DEV Phase complete for {feature}
-  Runtime:         cursor
-  Mode:            <default | spec-driven>
-  Output dir:      <output/feats/feat-{feature}/ | .planr/specs/SPEC-NNN-{feature}/>
-  Tasks succeeded: X / Y
-  Tasks failed:    Z (see error-report.md files)
-  QA gate:         <passed | failed>
-  DevOps config:   <generated | skipped>
-  Docs:            <generated | skipped>
-  CLAUDE.md:       <refreshed | skipped (planr-managed)>
-  Marker:          <SPEC_DIR>/.pipeline-shipped
-```
-
-If any task failed, list paths to error-report.md files.
-
----
-
-## Failure modes
-
-| Condition | Action |
-|---|---|
-| feat folder / spec dir missing | Abort, suggest plan {feature} first |
-| No tasks | Abort, suggest re-running plan |
-| Single task fails 3x | Continue with other tasks, surface in summary |
-| All tasks fail | Skip QA + DevOps + Doc-Gen; still run snapshot |
-| QA gate fails | Skip DevOps + Doc-Gen; still run snapshot |
-
----
-
-*Generated by `planr rules generate --target cursor --scope pipeline`. Pairs with `planr-pipeline-plan.mdc` for the PO phase.*

package/dist/templates/rules/cursor/planr-pipeline.mdc.hbs

@@ -1,134 +0,0 @@
----
-description: "Planr Pipeline orchestration — PO/DEV phase rules, R1 human gate, mode detection, runtime parity for {{projectName}}"
-globs: [".planr/specs/**", "input/specs/**", "output/feats/**"]
-alwaysApply: false
----
-
-# Planr Pipeline (Cursor edition — Protocol v{{protocolVersion}})
-
-You are operating inside a planr-pipeline-aware project on **Cursor**.
-The pipeline is a two-phase factory:
-
-```
-PO Phase (planning)  →  HUMAN REVIEW  →  DEV Phase (implementation)
-```
-
-**Hard rule R1: NEVER auto-chain PO Phase to DEV Phase.** A human review step
-gates them. Two distinct user invocations are required: "plan {feature}" and
-"ship {feature}".
-
----
-
-## Mode detection
-
-Before doing anything, decide the project mode:
-
-1. If `.planr/config.json` exists AND its `idPrefix.spec` field is set,
-   the project is in **spec-driven mode**. Spec dir lives at
-   `.planr/specs/SPEC-NNN-{slug}/`.
-2. Otherwise, **default mode**: `output/feats/feat-{name}/`.
-
-| Concept | Default mode | Spec-driven mode |
-|---|---|---|
-| Spec source | `input/specs/spec-{name}.md` | `.planr/specs/SPEC-NNN-{slug}/SPEC-NNN-{slug}.md` |
-| Design spec | `output/feats/feat-{name}/design-spec.md` | `<SPEC_DIR>/design/design-spec.md` |
-| US output | `output/feats/feat-{name}/us-{N}/us-{N}.md` | `<SPEC_DIR>/stories/US-NNN-{slug}.md` |
-| Task output | `output/feats/feat-{name}/us-{N}/tasks/task-{M}.md` | `<SPEC_DIR>/tasks/T-NNN-{slug}.md` |
-
----
-
-## Routing
-
-When the user says **"plan {feature}"** (or "decompose {feature}", "spec {feature}"):
-follow `.cursor/rules/planr-pipeline-plan.mdc`.
-
-When the user says **"ship {feature}"** (or "implement {feature}", "build {feature}"):
-follow `.cursor/rules/planr-pipeline-ship.mdc`.
-
----
-
-## Subagents (8 named roles)
-
-The pipeline ships 8 specialised role prompts. On Cursor, dispatch each as a
-**Composer subagent** with the role's body as the system prompt. The bodies
-live in `{{cursorRulesRoot}}/agents/{role}.md`:
-
-{{#each agentNames}}
-- `{{this}}` — see `{{../cursorRulesRoot}}/agents/{{this}}.md`
-{{/each}}
-
-When invoking a role, prefix the dispatch with the project context:
-`MODE: {default|spec-driven}`, `SPEC_DIR` (if spec mode), `feature/slug`.
-
----
-
-## Tool restrictions (Cursor parity)
-
-The Claude Code plugin enforces tool restrictions at the manifest layer
-(`tools: Read, Glob, Grep, Edit, Write, Bash(npm:*)` etc.). Cursor uses a
-different permission model — these restrictions are **prompt-level only**
-on Cursor and must be respected by you, the model, voluntarily:
-
-- **db-agent** — read-only DB introspection. Never write SQL DDL/DML. Output
-  goes to `output/db/schema.json` only.
-- **designer-agent** — `Read`, `Glob`, `Write` only. No shell access.
-  Output: `<SPEC_DIR>/design/design-spec.md` (spec mode) or
-  `output/feats/feat-{name}/design-spec.md` (default).
-- **specification-agent** — `Read`, `Glob`, `Grep`, `Write`. Decomposes the
-  spec into US + Task files. No shell.
-- **frontend-agent** — `Read`, `Edit`, `Write`, `Bash(npm:*)` family. Writes
-  UI files only (`src/features/{name}/` UI layer, components, pages, styles).
-  Never touches services, controllers, DTOs, entities.
-- **backend-agent** — same shell tools as frontend, but writes services,
-  DTOs, entities, controllers, DB queries. Never touches UI files.
-- **qa-agent** — read-only on `src/`. Runs build + test commands. Writes only
-  `qa-report.md`.
-- **devops-agent** — `Read`, `Glob`, `Write`, `Edit`. **No `Bash` whatsoever.**
-  Generates `docker-compose.yml`, Dockerfiles, CI workflow stubs. Never deploys.
-- **doc-gen-agent** — `Read`, `Glob`, `Grep`, `Write`. Writes `Docs/feat-{name}/`.
-
-If you, as the model, violate these restrictions on Cursor, the conformance
-test will catch it via the post-ship `git diff` check on each task's "Preserve"
-list. **Treat the restrictions as binding.**
-
----
-
-## Hard rules (cross-runtime)
-
-- **R1** — Never auto-chain PO → DEV. Two user invocations required.
-- **R2** — Max 2 tasks per US (1 if no PNG, 2 if PNG present).
-- **R3** — Model assignments: roles using `Sonnet 5` are analysis/decomposition;
-  roles using `Opus 4.8` are codegen. On Cursor, use the runtime's tier
-  selector (Cursor's "Composer model" setting) and pick the equivalent.
-- **R5** — Files in any task's `Preserve:` list MUST NOT be touched.
-- **R6** — Max 3 correction iterations per task. After 3, write
-  `error-report.md` and stop that task.
-- **R7** — Refresh CLAUDE.md (or coexist with planr-managed CLAUDE.md) at end
-  of `/ship`. Cursor has no Stop hook — see `planr-pipeline-ship.mdc`
-  Step 5 for the alternative.
-- **R8** — db-agent role is read-only. Never DDL/DML.
-- **R9** — frontend role only writes UI files; backend role only writes
-  services/DTOs/entities. No crossover.
-
----
-
-## Conformance proof
-
-On a successful `/ship` run, write the `.pipeline-shipped` YAML marker file
-(see `planr-pipeline-ship.mdc` Step 5.5). The marker is the audit-grade
-proof that the pipeline executed; the conformance test harness (in the
-`planr-pipeline` repo at `conformance/runner.mjs`) verifies it.
-
----
-
-## Compatibility matrix
-
-This rule represents the **Cursor adapter** to the OpenPlanr Protocol v1.0.0.
-Other supported runtimes:
-
-- **Claude Code** — install the `planr-pipeline` plugin (canonical surface)
-- **Codex** — see the AGENTS.md generated by `planr rules generate --target codex --scope pipeline`
-
-Full parity table: `planr-pipeline/docs/compatibility-matrix.md`.
-
-*Generated by `planr rules generate --target cursor --scope pipeline`.*