openplanr 1.5.0 → 1.5.2

package/dist/templates/rules/cursor/agents/doc-gen-agent.md

@@ -1,11 +1,11 @@
-> **Cursor adapter — synthesized from openplanr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/openplanr-pipeline.mdc` for Composer subagent dispatch.
-> Source: `openplanr-pipeline/agents/doc-gen-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
+> **Cursor adapter — synthesized from planr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/planr-pipeline.mdc` for Composer subagent dispatch.
+> Source: `planr-pipeline/agents/doc-gen-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
 
 
 # Doc-Gen Agent
 
 > **Phase:** Step 3.5 — Post-build (after qa-agent verdict is PASS)
-> **Trigger:** Invoked by `/openplanr-pipeline:ship` if `--no-docs` not set
+> **Trigger:** Invoked by `/planr-pipeline:ship` if `--no-docs` not set
 > **Mode:** Generates Markdown docs from US, tasks, and generated source code
 ## Path Resolution (NEW in pipeline v0.3.0)
 
@@ -165,7 +165,7 @@ See [architecture.md](architecture.md).
 ## Execution Steps
 
 ```
-0. Receive feature name from /openplanr-pipeline:ship as $ARGUMENTS
+0. Receive feature name from /planr-pipeline:ship as $ARGUMENTS
 1. Verify QA gate passed (read output/feats/feat-$ARGUMENTS/qa-report.md → "Verdict: PASS")
    If FAIL: skip silently, log warning
 2. Load all us-*.md, task-*.md, qa-report.md, design-spec.md (if present)

package/dist/templates/rules/cursor/agents/frontend-agent.md

@@ -1,5 +1,5 @@
-> **Cursor adapter — synthesized from openplanr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/openplanr-pipeline.mdc` for Composer subagent dispatch.
-> Source: `openplanr-pipeline/agents/frontend-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
+> **Cursor adapter — synthesized from planr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/planr-pipeline.mdc` for Composer subagent dispatch.
+> Source: `planr-pipeline/agents/frontend-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
 
 
 # Frontend Agent

package/dist/templates/rules/cursor/agents/qa-agent.md

@@ -1,11 +1,11 @@
-> **Cursor adapter — synthesized from openplanr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/openplanr-pipeline.mdc` for Composer subagent dispatch.
-> Source: `openplanr-pipeline/agents/qa-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
+> **Cursor adapter — synthesized from planr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/planr-pipeline.mdc` for Composer subagent dispatch.
+> Source: `planr-pipeline/agents/qa-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
 
 
 # QA Agent
 
 > **Phase:** Step 3.5 — DEV Phase post-build gate
-> **Trigger:** Invoked by `/openplanr-pipeline:ship` after all DEV tasks settle (success or 3-fail)
+> **Trigger:** Invoked by `/planr-pipeline:ship` after all DEV tasks settle (success or 3-fail)
 > **Mode:** READ-ONLY on source (Write granted only for `output/feats/feat-{name}/qa-report.md`)
 ## Path Resolution (NEW in pipeline v0.3.0)
 
@@ -128,7 +128,7 @@ or
 ## Execution Steps
 
 ```
-0. Receive feature name from /openplanr-pipeline:ship as $ARGUMENTS
+0. Receive feature name from /planr-pipeline:ship as $ARGUMENTS
 1. List all output/feats/feat-$ARGUMENTS/us-*/tasks/task-*.md
 2. For each task:
    a. Parse Create / Modify / Preserve lists

package/dist/templates/rules/cursor/agents/specification-agent.md

@@ -1,13 +1,13 @@
-> **Cursor adapter — synthesized from openplanr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/openplanr-pipeline.mdc` for Composer subagent dispatch.
-> Source: `openplanr-pipeline/agents/specification-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
+> **Cursor adapter — synthesized from planr-pipeline.** Agent role system prompt (body-only). Used by `/cursor/rules/planr-pipeline.mdc` for Composer subagent dispatch.
+> Source: `planr-pipeline/agents/specification-agent.md` (frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
 
 
 # Specification Agent
 
 > **Phase:** Step 1 — PO Phase (terminal agent in the PO chain)
-> **Trigger:** Invoked by `/openplanr-pipeline:plan` after upstream agents complete
+> **Trigger:** Invoked by `/planr-pipeline:plan` after upstream agents complete
 > **Chained after:** db-agent (if DatabaseType configured) → designer-agent (if PNGs present)
-> **Input feature name:** Passed by `/openplanr-pipeline:plan` as `$ARGUMENTS` (e.g. `auth` → operates on `feat-auth`)
+> **Input feature name:** Passed by `/planr-pipeline:plan` as `$ARGUMENTS` (e.g. `auth` → operates on `feat-auth`)
 
 ## Path Resolution (NEW in pipeline v0.3.0)
 
@@ -242,7 +242,7 @@ RULE 5 — DB alignment:
 ## Execution Steps
 
 ```
-0. Receive feature name from /openplanr-pipeline:plan as $ARGUMENTS (the {name} in feat-{name})
+0. Receive feature name from /planr-pipeline:plan as $ARGUMENTS (the {name} in feat-{name})
 1. Load input/specs/spec-$ARGUMENTS.md
 2. Load input/tech/stack.md
    2a. For each path in stack.md's ActiveStackFiles list → load that stack file
@@ -251,9 +251,9 @@ RULE 5 — DB alignment:
        (e.g. ${CLAUDE_PLUGIN_ROOT}/stacks/frontend/nextjs.md, .claude/stacks/backend/custom.md)
    2b. Use stack-file conventions (folder layout, naming) when filling task file paths
 3. Check if output/feats/feat-$ARGUMENTS/design-spec.md exists → set has_design = true/false
-   (Designer Agent should have run first via /openplanr-pipeline:plan if PNGs were present)
+   (Designer Agent should have run first via /planr-pipeline:plan if PNGs were present)
 4. Check if output/db/schema.json exists → load if relevant
-   (DB Agent should have run first via /openplanr-pipeline:plan if DatabaseType is configured)
+   (DB Agent should have run first via /planr-pipeline:plan if DatabaseType is configured)
 5. Decompose spec into N User Stories
 6. For each US:
    a. Write us-{N}/us-{N}.md
@@ -261,7 +261,7 @@ RULE 5 — DB alignment:
    c. If has_design: write task-1.md (UI, Frontend Agent) + task-2.md (Tech, Backend Agent)
    d. If !has_design: write task-1.md (Tech only, Backend Agent) — per docs/rules.md R2
 7. Log: "Specification Agent complete. N US, M tasks → output/feats/feat-$ARGUMENTS/"
-8. STOP. Do not proceed to DEV phase. The /openplanr-pipeline:plan orchestrator stops here for human review.
+8. STOP. Do not proceed to DEV phase. The /planr-pipeline:plan orchestrator stops here for human review.
 ```
 
 ---

package/dist/templates/rules/cursor/{openplanr-pipeline-plan.mdc.hbs → planr-pipeline-plan.mdc.hbs}

@@ -1,5 +1,5 @@
 ---
-description: "OpenPlanr Pipeline — PO Phase orchestration (plan {feature}). Decomposes a spec into User Stories + Tasks. STOPS at the human-review gate."
+description: "Planr Pipeline — PO Phase orchestration (plan {feature}). Decomposes a spec into User Stories + Tasks. STOPS at the human-review gate."
 globs: []
 alwaysApply: false
 ---
@@ -191,4 +191,4 @@ The user must explicitly say "ship {feature}" to proceed. Do not auto-chain.
 
 ---
 
-*Generated by `planr rules generate --target cursor --scope pipeline`. Pairs with `openplanr-pipeline-ship.mdc` for the DEV phase.*
+*Generated by `planr rules generate --target cursor --scope pipeline`. Pairs with `planr-pipeline-ship.mdc` for the DEV phase.*

package/dist/templates/rules/cursor/{openplanr-pipeline-ship.mdc.hbs → planr-pipeline-ship.mdc.hbs}

@@ -1,5 +1,5 @@
 ---
-description: "OpenPlanr Pipeline — DEV Phase orchestration (ship {feature}). Frontend ‖ backend → qa → devops ‖ doc-gen → snapshot → marker."
+description: "Planr Pipeline — DEV Phase orchestration (ship {feature}). Frontend ‖ backend → qa → devops ‖ doc-gen → snapshot → marker."
 globs: []
 alwaysApply: false
 ---
@@ -29,7 +29,7 @@ later run encounters this sentinel, surface a one-line reminder to refresh
 
 ### 1a — Detect planr spec mode
 
-Same as `openplanr-pipeline-plan.mdc` Step 1a:
+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}>/`.
@@ -239,4 +239,4 @@ If any task failed, list paths to error-report.md files.
 
 ---
 
-*Generated by `planr rules generate --target cursor --scope pipeline`. Pairs with `openplanr-pipeline-plan.mdc` for the PO phase.*
+*Generated by `planr rules generate --target cursor --scope pipeline`. Pairs with `planr-pipeline-plan.mdc` for the PO phase.*

package/dist/templates/rules/cursor/{openplanr-pipeline.mdc.hbs → planr-pipeline.mdc.hbs}

@@ -1,12 +1,12 @@
 ---
-description: "OpenPlanr Pipeline orchestration — PO/DEV phase rules, R1 human gate, mode detection, runtime parity for {{projectName}}"
+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
 ---
 
-# OpenPlanr Pipeline (Cursor edition — Protocol v{{protocolVersion}})
+# Planr Pipeline (Cursor edition — Protocol v{{protocolVersion}})
 
-You are operating inside an OpenPlanr-pipeline-aware project on **Cursor**.
+You are operating inside a planr-pipeline-aware project on **Cursor**.
 The pipeline is a two-phase factory:
 
 ```
@@ -40,10 +40,10 @@ Before doing anything, decide the project mode:
 ## Routing
 
 When the user says **"plan {feature}"** (or "decompose {feature}", "spec {feature}"):
-follow `.cursor/rules/openplanr-pipeline-plan.mdc`.
+follow `.cursor/rules/planr-pipeline-plan.mdc`.
 
 When the user says **"ship {feature}"** (or "implement {feature}", "build {feature}"):
-follow `.cursor/rules/openplanr-pipeline-ship.mdc`.
+follow `.cursor/rules/planr-pipeline-ship.mdc`.
 
 ---
 
@@ -104,7 +104,7 @@ list. **Treat the restrictions as binding.**
 - **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 `openplanr-pipeline-ship.mdc`
+  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
@@ -115,9 +115,9 @@ list. **Treat the restrictions as binding.**
 ## Conformance proof
 
 On a successful `/ship` run, write the `.pipeline-shipped` YAML marker file
-(see `openplanr-pipeline-ship.mdc` Step 5.5). The marker is the audit-grade
+(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
-`openplanr-pipeline` repo at `conformance/runner.mjs`) verifies it.
+`planr-pipeline` repo at `conformance/runner.mjs`) verifies it.
 
 ---
 
@@ -126,9 +126,9 @@ proof that the pipeline executed; the conformance test harness (in the
 This rule represents the **Cursor adapter** to the OpenPlanr Protocol v1.0.0.
 Other supported runtimes:
 
-- **Claude Code** — install the `openplanr-pipeline` plugin (canonical surface)
+- **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: `openplanr-pipeline/docs/compatibility-matrix.md`.
+Full parity table: `planr-pipeline/docs/compatibility-matrix.md`.
 
 *Generated by `planr rules generate --target cursor --scope pipeline`.*

package/dist/templates/spec/spec-shaped.md.hbs

@@ -84,6 +84,6 @@ _Optional hints to guide `planr spec decompose`. Not business requirements._
 ---
 
 > **Pipeline handoff:** Once decomposed and reviewed, run from Claude Code:
-> `/openplanr-pipeline:plan {{slug}}`
+> `/planr-pipeline:plan {{slug}}`
 >
 > _This spec was authored via `planr spec shape {{id}}` on {{date}}. Run `planr spec decompose {{id}}` to generate User Stories + Tasks._

package/dist/templates/spec/spec.md.hbs

@@ -64,10 +64,10 @@ _Optional hints to guide `planr spec decompose`. Not business requirements._
 
 > **Next steps:**
 >
-> In Claude Code with the `openplanr-pipeline` plugin:
+> In Claude Code with the `planr-pipeline` plugin:
 > ```
-> /openplanr-pipeline:plan {{slug}}     # decompose + human review
-> /openplanr-pipeline:ship {{slug}}     # full DEV phase
+> /planr-pipeline:plan {{slug}}     # decompose + human review
+> /planr-pipeline:ship {{slug}}     # full DEV phase
 > ```
 >
 > Bare CLI:

package/dist/templates/spec/task.md.hbs

@@ -17,7 +17,7 @@ updated: "{{date}}"
 > **User Story:** {{storyId}}
 > **Spec:** {{specId}}
 > **Type:** {{type}}
-> **Agent:** `{{agent}}` (matches `openplanr-pipeline` subagent name; free-form for other tools)
+> **Agent:** `{{agent}}` (matches `planr-pipeline` subagent name; free-form for other tools)
 > **Note:** T-NNN ID is **scoped to the parent spec** ({{specId}}), not project-globally unique.
 
 ## Objective

package/dist/utils/constants.d.ts

@@ -9,7 +9,7 @@ export declare const DEFAULT_CURSOR_RULES_DIR = ".cursor/rules";
  * roles). Bumps RARELY — only on artifact-schema breaks or workflow
  * contract changes, NOT on pipeline plugin patches.
  *
- * NOT to be confused with the openplanr-pipeline plugin version (which moves
+ * NOT to be confused with the planr-pipeline plugin version (which moves
  * fast and is tracked in the marketplace pin file, not here). Generated rule
  * files reference the protocol contract; the runtime adapter (Claude Code
  * plugin / Cursor MDC / Codex AGENTS.md) writes its own actual version into
@@ -17,10 +17,10 @@ export declare const DEFAULT_CURSOR_RULES_DIR = ".cursor/rules";
  *
  * Read by:
  *   - CursorGenerator (renders into Cursor MDC headers)
- *   - ClaudeGenerator (renders into the sibling `openplanr-pipeline.md` reference card)
+ *   - ClaudeGenerator (renders into the sibling `planr-pipeline.md` reference card)
  *   - CodexGenerator  (renders into the AGENTS.md pipeline section)
  *
- * See `openplanr-pipeline/docs/protocol/` for the full protocol spec.
+ * See `planr-pipeline/docs/protocol/` for the full protocol spec.
  */
 export declare const OPENPLANR_PROTOCOL_VERSION = "1.0.0";
 export declare const ARTIFACT_DIRS: {
@@ -48,14 +48,14 @@ export declare const VALID_STATUSES: Partial<Record<ArtifactType, readonly strin
 /**
  * Spec-driven mode (third planning posture) uses a richer status lifecycle
  * because each phase corresponds to a different role transition:
- * PO authoring → AI decomposition → human review → handoff to openplanr-pipeline.
+ * PO authoring → AI decomposition → human review → handoff to planr-pipeline.
  *
  * - pending             — SPEC created, body not yet written
  * - shaping             — SPEC body authored (manually or via `planr spec shape`)
  * - decomposing         — `planr spec decompose` is running (AI generating US + tasks)
  * - decomposed          — US + Task files written, awaiting human review
- * - ready-for-pipeline  — `planr spec promote` validated; ready for openplanr-pipeline
- * - in-pipeline         — openplanr-pipeline `/plan` or `/ship` is running
+ * - ready-for-pipeline  — `planr spec promote` validated; ready for planr-pipeline
+ * - in-pipeline         — planr-pipeline `/plan` or `/ship` is running
  * - done                — DEV phase complete, code shipped
  */
 export declare const VALID_SPEC_STATUSES: readonly ["pending", "shaping", "decomposing", "decomposed", "ready-for-pipeline", "in-pipeline", "done"];

package/dist/utils/constants.js

@@ -12,7 +12,7 @@ export const DEFAULT_CURSOR_RULES_DIR = '.cursor/rules';
  * roles). Bumps RARELY — only on artifact-schema breaks or workflow
  * contract changes, NOT on pipeline plugin patches.
  *
- * NOT to be confused with the openplanr-pipeline plugin version (which moves
+ * NOT to be confused with the planr-pipeline plugin version (which moves
  * fast and is tracked in the marketplace pin file, not here). Generated rule
  * files reference the protocol contract; the runtime adapter (Claude Code
  * plugin / Cursor MDC / Codex AGENTS.md) writes its own actual version into
@@ -20,10 +20,10 @@ export const DEFAULT_CURSOR_RULES_DIR = '.cursor/rules';
  *
  * Read by:
  *   - CursorGenerator (renders into Cursor MDC headers)
- *   - ClaudeGenerator (renders into the sibling `openplanr-pipeline.md` reference card)
+ *   - ClaudeGenerator (renders into the sibling `planr-pipeline.md` reference card)
  *   - CodexGenerator  (renders into the AGENTS.md pipeline section)
  *
- * See `openplanr-pipeline/docs/protocol/` for the full protocol spec.
+ * See `planr-pipeline/docs/protocol/` for the full protocol spec.
  */
 export const OPENPLANR_PROTOCOL_VERSION = '1.0.0';
 export const ARTIFACT_DIRS = {
@@ -59,14 +59,14 @@ export const VALID_STATUSES = {
 /**
  * Spec-driven mode (third planning posture) uses a richer status lifecycle
  * because each phase corresponds to a different role transition:
- * PO authoring → AI decomposition → human review → handoff to openplanr-pipeline.
+ * PO authoring → AI decomposition → human review → handoff to planr-pipeline.
  *
  * - pending             — SPEC created, body not yet written
  * - shaping             — SPEC body authored (manually or via `planr spec shape`)
  * - decomposing         — `planr spec decompose` is running (AI generating US + tasks)
  * - decomposed          — US + Task files written, awaiting human review
- * - ready-for-pipeline  — `planr spec promote` validated; ready for openplanr-pipeline
- * - in-pipeline         — openplanr-pipeline `/plan` or `/ship` is running
+ * - ready-for-pipeline  — `planr spec promote` validated; ready for planr-pipeline
+ * - in-pipeline         — planr-pipeline `/plan` or `/ship` is running
  * - done                — DEV phase complete, code shipped
  */
 export const VALID_SPEC_STATUSES = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openplanr",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "description": "AI-powered planning CLI — backlog, sprints, task templates, estimation, GitHub and Linear sync, and AI agent rules for Cursor, Claude Code, and Codex",
   "type": "module",
   "main": "./dist/cli/index.js",