@gtrabanco/pi-agentic-workflow 0.13.2 → 0.14.0

package/skills/implementation-discovery/SKILL.md

@@ -1,209 +0,0 @@
----
-name: implementation-discovery
-user-invocable: false
-version: 1.1.0
-author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
-license: MIT
-description: >
-  Internal contract: the single owner of the bounded pre-write implementation
-  discovery step. One read-only mapper that closes seven evidence questions,
-  emits one fixed compact map, and routes READY | REPLAN | NEEDS-DESIGN |
-  BLOCKED before any branch, planning, or source write. Consumed only by
-  execute-phase on the pre-write route. Not a menu entry.
----
-
-# Implementation Discovery (internal)
-
-The one authoritative owner of the bounded, read-only pre-write mapper consumed
-by `execute-phase`. A phase does not touch the repository until this step has
-closed its questions and said `READY`. Nothing else may define what a valid
-pre-write discovery pass is.
-
-## When to use
-
-- `execute-phase` — before any branch/planning/source write, after the read-only
-  dependency/status/acceptance/phase/feature-28 receipt checks.
-- The step runs only on the pre-write route; it is never a general-purpose
-  orientation pass and never a substitute for planning.
-
-## Inputs (exact, only these)
-
-The mapper receives only:
-
-- the governing SPEC/fix obligations for the current phase;
-- the current feature-28 SPEC and Plan receipt digests;
-- the phase-relevant rows from frozen planning evidence, with source revision,
-  affected decision/obligation, freshness, and declared unknowns;
-- the phase fingerprint, ordered tasks, acceptance/obligation ids, and the last
-  progress receipt;
-- source HEAD plus clean-source / allowed-planning-path evidence;
-- applicable NRS / decision / invariant evidence;
-- the repository discovery tools available in this environment.
-
-## Advisory locators
-
-Semantic/symbol navigation and Engram/memory tools are optional adapters that may
-locate evidence faster; they are never authority. Direct repository/Git/search/
-read/test fallback must satisfy the identical evidence contract, and only
-repository bytes answer a map field. The tool that found a citation does not
-excuse a missing `path:line` or a contradictory claim.
-
-## Seven evidence questions
-
-Every pass must answer — each answer citing repository-relative `path:line`,
-symbol, or test plus exact source revision / content identity:
-
-1. Which entry points and public/internal interfaces own current behaviour?
-2. Which callers, adapters, roles, compatibility surfaces, and failure paths
-   can this phase affect?
-3. Which helpers, patterns, decisions, and invariants constrain the change?
-4. Which tests, fixtures, probes, and production-like scenarios establish
-   current behaviour?
-5. Which exact writes are expected, and which reviewed obligation does each
-   serve?
-6. Which carried planning-evidence claims and Plan assumptions are directly
-   confirmed, refined, stale, missing, or contradicted by source?
-7. Which relevant unknowns remain, who owns them, and what evidence resolves
-   them?
-
-The mapper records conclusions, not every search. Repeating a search/read
-requires a new question, changed source, or insufficient cited evidence;
-otherwise it stops (no-progress).
-
-## Inline and fresh routing
-
-**Inline** is permitted only when behaviour is localized/familiar, targeted
-evidence answers every question, no public/persistence/security/recovery/
-compatibility boundary may change, and the executor can finish the map before
-writing.
-
-**A fresh read-only mapper** is required for cross-module/layer or unfamiliar
-work, public/persistence/security/recovery/compatibility impact, competing
-project patterns, an unproven material Plan assumption, prior failed
-attempts/review bias, or any case where editing would begin before the map
-closes. Same-model fresh context is useful but is not model diversity. Manual
-sequential fresh conversations are the portable fallback.
-
-No file-count threshold participates in the route or the verdict.
-
-## Fixed implementation map
-
-```text
-IMPLEMENTATION MAP — unit-id phase-id
-Map revision: opaque single-consumption id
-Source identity: HEAD + clean-source proof + cited-evidence manifest digest
-Authority: SPEC receipt + Plan receipt + phase fingerprint
-Planning evidence: carried row ids + current confirmation/refinement/conflict
-Obligations: ordered acceptance/fix/obligation ids
-Entry points: path:line or symbol + role + exact evidence
-Affected surfaces: callers/adapters/roles/compatibility/failure paths + evidence
-Current behaviour: evidence-backed summary
-Reuse and constraints: helper/pattern/decision/invariant/fixture + evidence
-Expected writes: ordered path + obligation served + reason
-Validation: falsification probe + TDD target + phase gate
-Plan assumptions: confirmed items + evidence
-Contradictions: none or exact Plan/source conflict
-Unknowns: none or exact missing fact + owner + resolution evidence
-Decision: READY | REPLAN | NEEDS-DESIGN | BLOCKED
-```
-
-## Verdicts
-
-`READY` requires every field, question, and owned obligation covered, no
-material contradiction/unknown, an observed falsification probe, and expected
-writes inside phase authority. It also requires every carried planning-evidence
-row to be confirmed or narrowly refined.
-
-`REPLAN` means source disproves Engineering assumptions while Product remains
-stable, or Plan-level topology/architecture/obligation/validator evidence is
-absent.
-
-`NEEDS-DESIGN` means Product, acceptance, authority, or architecture intent is
-missing or conflicting.
-
-`BLOCKED` names evidence that cannot currently be obtained.
-
-No other verdict exists.
-
-## Routes and upstream owners
-
-A verdict routes, it never repairs. Missing/contradicted Plan-level topology,
-architecture, obligations, validators, or assumptions return to
-`plan-feature`/`plan-fix` plus a fresh `review-plan`. Product/acceptance/
-authority/architecture gaps return to `design-feature` then `review-spec`. A
-verdict with unavailable evidence is one exact `BLOCKED` prerequisite. Mapping
-does not decide code correctness — candidate review, verification, and audit
-authority are unchanged, and a second repair/re-review cycle inherits feature
-28's `CONVERGENCE-ANOMALY` diagnosis.
-
-Source-local findings stay local; Plan/Product defects return upstream. A
-missing current-unit behaviour entailed by reviewed scope joins the obligation
-map and routes upstream; it is never a follow-up issue and never calls the
-forge.
-
-## Legacy and manual routes
-
-The portable fallback uses sequential fresh conversations with exact
-artifact/source bindings. It may not claim a machine receipt or a durable
-guarantee it cannot produce; it says plainly what was observed and what was
-not.
-
-## Early falsification
-
-Before READY, run the cheapest relevant read-only probe: a focused existing
-test, current parser/CLI output, public type/schema inspection, symbol callers,
-or an existing fixture. Record the command/query, the observed result, and the
-evidence. A failed probe informs REPLAN/NEEDS-DESIGN; unavailable high-risk
-evidence is BLOCKED, never rewritten as confident evidence. This does not
-replace TDD or later verification.
-
-## No-progress
-
-Conclusion once. Do not re-read or re-search to reconfirm the same conclusion
-without a new question, changed source, or insufficient cited evidence. On
-repetition, stop with `BLOCKED` and name what is still missing. Re-read is
-allowed only for a changed source revision, a new question, insufficient
-evidence, or a contradiction.
-
-## Read-only boundary
-
-The mapper reads; it may not write. It creates no forge issue, no committed
-map, no planning unit, no schema, no source edit, and no test edit. It emits the
-map and reuses `SkillOutcome v1`. A missing current-unit behaviour entailed by
-reviewed scope joins the obligation map and routes upstream; it is not a
-follow-up issue. Discovery never calls the forge.
-
-## Writer handoff
-
-The writer receives frozen phase authority plus the fixed compact map. It does
-not receive raw files, repeated summaries, raw planning discovery, raw
-exploration history, or the authoring conversation unless a cited claim cannot
-be interpreted without a focused excerpt. The map preserves the phase-relevant planning-evidence ids and
-their current confirmation. The writer may only touch expected paths /
-obligations; a newly discovered path or contradiction stops and remaps/routes
-rather than expanding silently.
-
-## Source identity
-
-Source identity is exact pre-map HEAD, proof that tracked/untracked changes
-outside the allowed planning paths are absent, an ordered manifest digest of
-every cited evidence path/content plus the current phase/receipt bindings, and
-an opaque `mappingRevisionId` created for this mapping event.
-
-## Preparation continuity
-
-After READY, deterministic setup may create the branch and commit only the
-already-reviewed planning paths. Before the first source/test edit the executor
-proves either HEAD is unchanged or the new commit is a direct descendant whose
-entire diff is the allowed planning set and whose authority/content digests
-match. Any other path, parent, receipt, phase, or evidence change invalidates
-the map and routes again.
-
-## Consumption and recovery
-
-READY is single-consumption: the first implementation write consumes it. A crash
-before the write may resume only after freshness/no-consumption proof. A crash
-after any partial write remaps current source during recovery. A new map
-revision plus changed Git causal identity prevents reuse after revert; direct
-out-of-protocol state manipulation cannot be claimed detectable without runtime
-history.

package/skills/plan-feature/SKILL.md

@@ -1,208 +0,0 @@
----
-name: plan-feature
-user-invocable: true
-version: 5.3.1
-argument-hint: <NN-slug | #N> | --from-issue N | --scaffold <slug> | --next
-author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
-license: MIT
-description: >
-  Route designed features or issues into engineering planning and roadmap
-  registration; undesigned work stops at design-feature. Supports `--next`,
-  `--from-issue`, and `--scaffold`. Triggers: "plan-feature", "plan a feature",
-  "plan the next roadmap feature", "create SPEC and TASKS".
----
-
-# Plan Feature (router)
-
-The engineering-planning door for a feature whose product definition already
-exists. Routes to a focused internal step so only the work you need runs (no
-fat single skill). **Docs only — no code, no branch.** Product definition
-(raw-idea interview, capability closure) is `design-feature`'s job, not this
-one — the routed redirect gate enforces that split.
-
-## Turn contract — verify before ending the turn
-
-```
-✓ The redirect gate ran FIRST, before any SPEC edit: undesigned input → STOP,
-  print the fixed `/design-feature <slug>` block, do nothing else this turn
-✓ Then the Product-review gate ran: no current `spec-review-pass` receipt bound to
-  the recomputed snapshot → STOP with its fixed block and the `/review-spec`
-  hand-off; a candidate/verification receipt, a Plan receipt, or readiness never counts
-✓ Designed input only: engineering half filled, artifacts written, and the
-  roadmap entry registered (number, order, deps verified)
-✓ If `plan-feature-scaffold` ran this turn: the roadmap row was re-read
-  AFTER the write and literally reads `planned` — a dropped `defined→planned`
-  write fails this box; do not end the turn until it's fixed
-✓ Planned, not reviewed: the ledgers are frozen, `stage: plan` readiness printed
-  `READY-FOR-REVIEW`, and the turn hands off to `/review-plan` — this skill never
-  reviews the plan it just wrote and never hands off to `/execute-phase` for a
-  plan with no current Plan review receipt
-✓ The dependency & blocker check was RUN and its result decides which closing block is printed
-✓ An unmet dependency? The closing block lists the complete dependency chain, deepest first, joined with ` + `
-✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
-✓ The closing `→ Next:` block is printed as the ABSOLUTE last output
-```
-
-About to end the turn with any box unchecked? The turn is NOT done — complete
-the missing box first (weak models drop end-of-document duties; this list is
-first on purpose).
-
-## Step 0 — Discover the project (always first)
-
-Per the agent guide's **Workflow conventions** + **documentation map**, then read
-what THIS skill needs: the **roadmap** (`docs/features/ROADMAP.md`), so routing
-and roadmap registration match the project's real layout.
-
-## Progressive loading — route before planning
-
-The allowlist:
-
-1. Every invocation: read [redirect gate and routing](references/ROUTING.md),
-   apply the status gate, then the Product-review gate, and stop on its exact
-   block when instructed.
-2. Any route that can write planning artifacts: after the redirect gate permits
-   routing, consume the [planning preflight](<../planning-preflight/SKILL.md>) —
-   it owns the normalized repository-state read and the ONE final architectural
-   classification — before composing an internal step.
-3. Before composing an internal step: load the [phase contract](<../phase-contract/SKILL.md>)
-   so every SPEC written this turn carries the canonical 8-box phase-lint and
-   the normalized phase fingerprint.
-4. Only when `node scripts/unit-route.mjs <NN>` prints `route: replan`: load the
-   [replan contract](<../replan-findings/SKILL.md>); it owns the exemption.
-
-Do not load planning gates after a redirect stop. Both resources are normative,
-one hop from this file, and fail closed when missing.
-
-## Process
-
-1. **Redirect gate** from `ROUTING.md` — always first.
-2. **Product-review gate** from the same resource — current `spec-review-pass`
-   receipt bound to the recomputed snapshot, or STOP. No bypass flag.
-3. **Route** from the same resource. For issue input, resolve and validate the issue
-   identity only; after the [planning preflight](<../planning-preflight/SKILL.md>)
-   confirms that planning may write, compose the from-issue internal to produce
-   a **filled, sized SPEC product half**; that internal stops at the Product-review
-   gate, so `plan-feature-scaffold` runs only once `review-spec` has passed the half:
-   it fills the engineering half, scales the artifacts to the SPEC's size (XS/S →
-   SPEC-only; M/L → full set) and registers the roadmap. The
-   already-designed scoped path runs `plan-feature-scaffold` directly. Every
-   path holds **one immutable planning context** — the roadmap snapshot taken
-   before writing (and one issue payload when `--from-issue`) — reused across
-   the internal steps; never re-fetched mid-plan.
-4. **Confirm roadmap.** Verify the feature is registered in
-   `docs/features/ROADMAP.md` with the right number, ordering, and dependencies;
-   if any of the three is missing or wrong, fix the entry now — never leave registration for later.
-   `plan-feature` verifies and repairs the roadmap entry; `plan-feature-scaffold`
-   is the sole writer of the `defined → planned` write.
-5. **Dependency & blocker check (always, before recommending execution).**
-   - Walk the feature's `Depends on:` closure (transitively): every dependency
-     must be `done` **and merged**. Any unmet → the closing block recommends
-     building the deepest unmet dependency first, NOT this feature.
-   - Check the fix index + open issues (forge CLI) for fix-now items touching
-     the same modules this SPEC names. Any hit → the closing block recommends
-     `/plan-fix <n>` before execution ("building on a known defect bakes it in").
-   - Planning itself never blocks on either — the SPEC/artifacts are still
-     written; only the **recommended next step** changes.
-5. **Print the next step** per the check above (see Done when).
-
-## Guardrails
-
-- Docs only — no code, no branch (that is `execute-phase`).
-- **Never plan an undesigned feature** — the redirect gate has no bypass flag,
-  ever. Do not add one, even if asked; point at `/design-feature` instead.
-- **Never plan an unreviewed Product half** — this gate has no bypass flag either.
-  Planning binds the reviewer's receipt; it may never write, widen, or "refresh"
-  one, and a receipt bound to older bytes is stale, not close enough.
-- Don't re-ask what a flag, the issue, or the docs already settle.
-- Surface conflicts (numbering clashes, dependency cycles, scope overlap) before
-  writing, not after.
-- Otherwise per the project's **Workflow conventions** (docs-language).
-
-## Internal steps (not user-invocable)
-
-- `plan-feature-from-issue` — issue → scoped SPEC product half, `Closes #N`.
-- `plan-feature-scaffold` — SPEC → engineering half + full artifact set +
-  roadmap entry.
-
-These run **within this same conversation** (that's what "composing" means) —
-on any agent, just follow their `SKILL.md` inline as the routed step. The
-raw-idea interview that used to be an internal step of this router is retired
-— see `docs/workflow/MIGRATION.md`; that logic now lives in `design-feature`,
-a user-facing skill in its own right (product definition is its own pipeline
-stage, not an internal routing detail of this one).
-
-## Portability (agents other than Claude Code)
-
-The workflow is the contract; Claude Code features are conveniences. On an
-agent that lacks one, apply the fallback — never skip the step the feature
-enables:
-
-- **No slash-command menu** — where this skill says `/<skill>`, open that
-  skill's `SKILL.md` (wherever your agent installed the skills) and follow it
-  literally, in a fresh conversation: hand-offs assume a clean context. The
-  internal steps above are the exception — they run inline, in this one.
-- **No per-skill `model:`/`effort:`** — on the `#claude` branch the frontmatter pins these tiers; here, pick tiers yourself:
-  planning is judgment work — run it on your **strongest** model. The
-  execution it hands off to may run cheaper.
-
-## Relationship to other skills
-
-- **Redirects to** `design-feature` when the redirect gate stops on an
-  undesigned feature — never composed in-turn (planning-class, ≥-tier hand-off).
-- **Redirects to** `review-spec` when the Product-review gate stops: designed is not
-  reviewed. Its receipt is this skill's input, and `plan-feature-scaffold` binds it
-  as the Plan snapshot's Product parent.
-- `triage-issue` routes here to promote an issue to a feature (still subject to
-  the redirect gate if the promoted issue is undesigned).
-- `execute-phase` executes the phases afterward (`audit-docs` audits anytime).
-
-## Done when
-
-- The redirect gate ran, and if it stopped, nothing else in this turn touched
-  the SPEC.
-- Designed input only: a planned feature with its full artifact set exists and
-  is roadmap-registered — **and the roadmap row was re-read after the write and
-  literally reads `planned`** (never assumed from having run the write step).
-- The two planning ledgers were frozen with the Engineering half
-  ([planning ledgers](<../../pre-execution-review/SKILL.md>)), the
-  `stage: plan` readiness preflight printed `READY-FOR-REVIEW`, and the new
-  `artifactRevisionId` is named in the hand-off. A planned unit is **not** an
-  executable unit: this skill never reviews its own plan.
-- The dependency & blocker check ran, and **the closing `→ Next:` block matches
-  its result** — clean:
-
-  ```
-  → Next: /review-plan <NN> — the plan is written; an independent context must
-    review it before any phase is executed
-    · the review returned PLAN-REVIEW-FAIL → this skill replans the batch, then re-reviews
-    · adjust scope first → re-run /design-feature <slug>   · audit the planning docs → /audit-docs
-  ```
-
-  already-planned feature (redirect gate stopped, never re-scaffolded):
-
-  ```
-  → Next: /execute-phase <NN> — this feature is already planned; execute every
-    remaining phase, don't re-plan it.
-    · explicit atomic mode → /execute-phase <NN> P1
-  ```
-
-  undesigned feature (redirect gate stopped):
-
-  ```
-  → Next: /design-feature <slug> — this feature has no completed product design yet
-    (capability closure not done). Design it first; then re-run /plan-feature <slug>.
-  ```
-
-  designed but unreviewed/stale (Product-review gate stopped): the fixed
-  `PRODUCT-REVIEW GATE … BLOCKED` block from `ROUTING.md`, closing with
-  `/review-spec <NN>-<slug>`.
-
-  unmet dependency and/or blocking fix-now issue:
-
-  ```
-  Dependency chain (deepest first): <deepest> + <dependency> + <NN> (replace with every actual member; never print `…`)
-  → Next: /plan-feature <deepest-unmet-dep> (or /execute-phase <deepest-unmet-dep>) — build the
-    complete dependency chain first: <deepest> + <dependency> + <NN>
-    · blocking fix-now issue #<n> in the same area → /plan-fix <n> before executing
-    · proceed anyway → /execute-phase <NN> --force (the gate logs the override)
-  ```

package/skills/plan-feature/references/ROUTING.md

@@ -1,155 +0,0 @@
-## Redirect gate (always, before routing)
-
-Before any other step, resolve the target slug/issue. An issue input
-(`--from-issue <N>` or issue URL/number) resolves and validates the issue
-identity only; it does not invoke `plan-feature-from-issue` here. The parent
-must consume the [planning preflight](<../../planning-preflight/SKILL.md>) and
-confirm that planning may write before composing that internal writer. The
-internal step supplies the feature slug for the later roadmap gate.
-
-**Replan exemption — the router runs first.** Before the status gate, run
-`node scripts/unit-route.mjs <NN>`. A `route: replan` line means the unit
-carries an open finding whose frozen route is the plan owner: skip the STOP and
-load [the replan contract](<../../replan-findings/SKILL.md>) to re-cut the plan
-from the router's bounded read set. Any other route keeps the gate and the
-hand-off its line names; a router that cannot run is `BLOCKED`.
-
-For other inputs, read **the roadmap status** (`docs/features/ROADMAP.md` → the five-state machine
-`idea/defined/planned/in-progress/done`) — the **primary** gate signal. The
-SPEC's `## Design status` marker is the SPEC-local record and the
-**legacy-compat fallback** only (see step 6 below), never the primary check:
-
-1. **Roadmap row status `defined`** → proceed to Routing below (the product
-   half is designed; the engineering half still needs scaffolding).
-2. **Roadmap row status `planned`** (SPEC + artifacts already present) →
-   **STOP**. Never invoke `plan-feature-scaffold` — re-scaffolding an
-   already-planned feature is the re-plan-loop bug this gate exists to close.
-   Print exactly:
-
-   ```
-   → Next: /execute-phase <NN> — this feature is already planned; execute every
-     remaining phase, don't re-plan it.
-     · explicit atomic mode → /execute-phase <NN> P1
-   ```
-3. **Roadmap row status `in-progress`** → **STOP**. Print exactly:
-
-   ```
-   → Next: /execute-phase <NN> <next-phase> — this feature is already being
-     implemented; resume the current phase, don't re-plan it.
-   ```
-4. **Roadmap row status `done`** → **STOP** (replanning stays forbidden — the
-   feature is fully built), and: `done` means built + PR open with the human merge
-   pending (a lifecycle label, never a gate verdict), so this is **not** "nothing
-   pending". Route to the merge gate instead. Print exactly:
-
-   ```
-   → Next: /audit-pr <PR> — done means built + PR open, merge pending (a lifecycle label, never a gate verdict)
-     · the row's PR is merged → nothing pending, pick the next unit → /plan-feature --next
-     · no PR is open → the row is mislabeled or execution stopped → /execute-phase <NN> (never a replan)
-   ```
-5. **Roadmap row status `idea`, or no row at all** → **STOP**. Print exactly:
-
-   ```
-   → Next: /design-feature <slug> — this feature has no completed product design yet
-     (capability closure not done). Design it first; then re-run /plan-feature <slug>.
-   ```
-
-   No bypass flag exists for this gate — an undesigned feature is never
-   planned by this skill, under any flag or instruction.
-6. **Legacy compat.** A roadmap row still reading a plain `planned` with no
-   five-state history (predates this repo's roadmap-status-machine feature):
-   fall back to the SPEC marker — `## Design status: designed` and Capability
-   closure filled → treat as `defined`+`planned`, STOP per step 2 above (a
-   legacy `planned` row is still already-planned — hand off to
-   `/execute-phase`, never re-scaffold). Marker missing/`not designed`/closure
-   empty → treat as `idea`, STOP per step 5. See `docs/workflow/MIGRATION.md`.
-7. **A raw idea with no slug at all** (nothing to check) → the same STOP
-   applies: print the block above pointing at `/design-feature "<idea>"`
-   instead of a slug.
-
-## Product-review gate (after the redirect gate, before Routing)
-
-The redirect gate proves the Product half was **designed**; this proves it was
-**independently reviewed** and unchanged since. Run it before any write on every
-planning route. Issue input has no slug yet: evaluate it on the slug
-`plan-feature-from-issue` produces, just before `plan-feature-scaffold` would run.
-
-1. Read the newest `## Pre-execution review receipt v1 — spec` block in the unit's
-   `progress.md`; none → fail closed.
-2. Recompute the SPEC-stage snapshot from the bytes on disk now — exactly one
-   artifact row (`kind: spec`, `selector: spec-product-v1`) plus the current
-   `artifactRevisionId` — digested with the schema package's canonical entry (no
-   package: record `validated: manual` and compare the stored digest line by line).
-3. Accept only when all hold: contract `agentic-workflow/
-   pre-execution-review-receipt@1`, `stage: spec`, verdict `spec-review-pass`,
-   `snapshotDigest` equals step 2, zero open or unverified material findings,
-   `contextClean: true`, and under `authorExclusion: enforced` reviewer ≠ author.
-4. Refuse, never silently: **missing** · **stale** (digest or `artifactRevisionId`
-   differs — any Product write, context change, or mutate-and-revert) ·
-   **wrong-stage** (a `plan` receipt) · **substitute** (candidate `ReviewReceipt v1`
-   or staged `VerificationReceipt v1`: different contracts, never interchangeable) ·
-   **self-approved** (reused identity under enforced exclusion, or `contextClean:
-   false`) · **author-readiness** (`READY-FOR-REVIEW` licenses a review request, it
-   is not one).
-
-Fail closed — print exactly, then touch nothing else this turn:
-
-```
-PRODUCT-REVIEW GATE — <NN>-<slug> BLOCKED (<missing|stale|wrong-stage|substitute|self-approved|author-readiness>)
-Expected: current spec-review-pass receipt bound to snapshot <digest>
-Actual:   <receipt state>
-
-→ Next: /review-spec <NN>-<slug> — the Product half needs a current independent
-    review before engineering planning can start
-  · a product choice is genuinely open → /design-feature <NN>-<slug> "<question>"
-  · no bypass flag exists for this gate
-```
-
-A stale receipt is never "refreshed" by editing the block — only a new review of a
-new snapshot produces one, and `--force` is not a `plan-feature` flag.
-
-## Routing
-
-Once the gate passes, pick the mode — first match wins:
-
-1. **Flag forces it** (skip detection): `--scaffold <slug>`, `--next`.
-2. **Issue input** — `--from-issue <N>`, an issue URL, or a bare numeric argument
-   `<N>` (for example, `131`) selects the issue-derived route; detection itself
-   does not compose `plan-feature-from-issue`. The parent route owns the
-   [planning preflight](<../../planning-preflight/SKILL.md>) consumption and must
-   confirm that planning may write before it composes `plan-feature-from-issue`,
-   then `plan-feature-scaffold`.
-3. **Scoped** — an existing, designed roadmap slug or a filled `SPEC.md` →
-   `plan-feature-scaffold`.
-4. **`--next` / no input** — read the roadmap, take the next `defined` entry
-   (the units that still need engineering planning — a `planned` row is
-   already scaffolded); apply the redirect gate to it, then scaffold.
-5. **Ambiguous** — ask one question, then route.
-
-### Example (routing)
-
-| You run | Detected | Routes to | Then |
-|---|---|---|---|
-| `plan-feature 14-csv-export` (not designed) | undesigned slug | — | STOP → `/design-feature 14-csv-export` |
-| `plan-feature 14-csv-export` (designed, no current spec review) | unreviewed Product half | — | STOP → `/review-spec 14-csv-export` |
-| `plan-feature 131` | issue #131 | `plan-feature-from-issue` (stops at the Product-review gate) | `/review-spec` → re-run `plan-feature 131` |
-| `plan-feature 14-csv-export` (designed + reviewed) | designed slug | `plan-feature-scaffold` | `execute-phase 14 P1` |
-| `plan-feature 14-csv-export` (already `planned`) | already-planned slug | — | STOP → `/execute-phase 14 P1` (no re-scaffold) |
-| `plan-feature --next` | next `defined` roadmap entry | gate, then scaffold | `execute-phase NN P1` |
-
-## Mode grammar (versioned — read by `scripts/normative-drift.test.mjs`)
-
-The detection order above is prose for the human; this table is the machine form
-of the same routing: `flag` must be a flag this skill's `argument-hint:` accepts
-and `route` must be a skill that exists. A flag or a route no surface declares is
-a defect in this table, never in the hint.
-
-```text
-plan-mode-routes@1
-# owner: plan-feature
-mode | flag | route
-issue-derived | --from-issue | plan-feature-from-issue
-forced-scaffold | --scaffold | plan-feature-scaffold
-next-defined | --next | plan-feature-scaffold
-designed-slug | n/a | plan-feature-scaffold
-```