@gtrabanco/pi-agentic-workflow 0.15.2 → 0.16.0

package/skills/triage-issue/references/REVIEW_FINDING_PROCESS.md

@@ -15,11 +15,11 @@ after `/fold-findings` leaves rows unresolved.
      remains on the current unit. Route it to `/fold-findings` or an explicit
      `/execute-phase <unit> P<n>`.
    - A correction too large for the current fold is `replan-in-unit`. Run
-     `node scripts/unit-route.mjs <unit>`; its `route: replan` line names the
-     planner (`/plan-feature <unit>` for a feature, `/plan-fix <issue-number>`
-     for a fix) and the fresh `/review-plan <unit>` that must pass before
-     execution. The plan must append concrete `P<n>` phases to the unit's
-     SPEC and preserve the finding's acceptance evidence.
+     `node scripts/unit-route.mjs <unit>`; its `route: replan` line prints the
+     planner command — `/unit-lane <unit>` for a feature, `/unit-lane --fix <n>`
+     for a fix — which re-runs the lane's `plan` step and appends concrete
+     `P<n>` phases to the unit's SPEC, preserving the finding's acceptance
+     evidence. The lane's `review` step gates execution.
    - A product, architecture, or acceptance decision that blocks safe work is
      `decision-required`. Ask the user; do not guess or weaken the finish line.
    - A finding disproved by current evidence is `disputed`. Preserve the row
@@ -35,7 +35,7 @@ Return exactly one block per finding:
 REVIEW FINDING <F-k> — <short title>
 Checked: <commands and evidence>
 VERDICT: fix-now | replan-in-unit | decision-required | disputed
-Action taken: <current-unit fold/phase | plan-feature | plan-fix | user decision>
+Action taken: <current-unit fold/phase | unit-lane | user decision>
 ```
 
 Close with every finding ID mapped to its own command, joined with ` + `, and

package/skills/unit-lane/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: unit-lane
 user-invocable: true
-version: 1.0.0
-argument-hint: <NN-slug | "<idea>"> [--retriage]
+version: 1.1.0
+argument-hint: <NN-slug | "<idea>"> [--retriage] | --fix <issue-number> | --from-issue <issue-number>
 description: >
   One-shot lane conductor for a delivery unit: triage, implement, evidence, and
   close in a single document. Triggers: "unit-lane", "run the lane",
@@ -36,8 +36,14 @@ done:
 
 - A known unit slug: `unit-lane <NN-slug>`
 - A raw idea (no slug yet): `unit-lane "<idea description>"`
+- A tracked fix issue (no fix folder yet): `unit-lane --fix <issue-number>`
+- A tracked roadmap feature issue (no feature folder yet): `unit-lane --from-issue <issue-number>`
 - Force re-triage: `unit-lane <NN-slug> --retriage`
 
+Both `--fix <n>` and `--from-issue <n>` are the exact forms
+`scripts/unit-route.mjs` prints for a tracked issue with no unit folder
+(`route: plan-from-issue`) — never invent a different spelling.
+
 ## Step 0 — Discover the project
 
 Per the agent guide's **Workflow conventions** + **documentation map**, then read
@@ -48,11 +54,20 @@ exists, read its current `SPEC.md` to avoid overwriting.
 
 ### 1. Resolve or create the unit doc
 
-If the idea has no slug, assign the next number from `docs/features/ROADMAP.md`
-and create `docs/features/<NN>-<slug>/SPEC.md` from the template. Fill
-objective, why, user outcome, and non-goals from the invocation. Acceptance
-criteria are induced from user scenarios — **ask-don't-infer**; if the request
-is too vague, STOP and ask the user with concrete options. See
+If the unit folder already exists, read its `SPEC.md` and continue. Otherwise
+create it from the tree the unit belongs to:
+
+| Invocation | Folder | Template | Index to register |
+|---|---|---|---|
+| `<NN-slug>` / `"<idea>"` | `docs/features/<NN>-<slug>/` | `docs/features/_TEMPLATE/SPEC.md` | `docs/features/ROADMAP.md` |
+| `--fix <issue-number>` | `docs/fix/<issue-number>-<topic>/` | `docs/fix/_TEMPLATE/SPEC.md` | `docs/fix/README.md` |
+| `--from-issue <issue-number>` | `docs/features/<NN>-<slug>/` | `docs/features/_TEMPLATE/SPEC.md` | `docs/features/ROADMAP.md` (row links `#<issue-number>`) |
+
+For `--fix`/`--from-issue`, read the tracked issue in the forge first and keep
+its number; the folder name carries it (`fix/<issue-number>-<topic>`). Fill
+objective, why, user outcome, and non-goals from the invocation (or the issue).
+Acceptance criteria are induced from user scenarios — **ask-don't-infer**; if the
+request is too vague, STOP and ask the user with concrete options. See
 [the unit doc template](references/STEPS.md) for section order.
 
 ### 2. Triage — read the catalog, never re-derive
@@ -119,8 +134,8 @@ unit doc's status, and print the closing block.
 
 ## Relationship to other skills
 
-`unit-lane` absorbs the fixed-pipeline skills (design-feature, plan-feature,
-review-spec, review-plan) into catalog steps. The review pack axes
+`unit-lane` absorbed the retired fixed-pipeline skills (design-feature,
+plan-feature, review-spec, review-plan) into catalog steps. The review pack axes
 (`review-implementation`, `review-code`, `review-security`, `review-perf`,
 `review-a11y`, `review-debt`) compose the review step; `triage-issue` feeds
 issues into the lane; `workflow-status` computes the next lane invocation.

package/skills/workflow-status/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: workflow-status
 user-invocable: true
-version: 3.9.0
+version: 3.9.1
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 argument-hint: "[--json-only] [--last-envelope <json|path>] [--compact]"
@@ -30,15 +30,14 @@ report — it never assembles the envelope by hand.
   stdout, never assembled by the model
 ✓ Nothing was edited, committed, pushed, or created — read-only, always
 ✓ `next.recommended` is non-bare (carries the unit's slug/NN, never a bare
-  `/plan-feature`) AND the script computed it from the unit's resolved status
-  **and** its current pre-execution evidence: `idea`/undesigned →
-  `/design-feature <slug>`; `defined` → `/plan-feature <slug>` only on a current
-  `SPEC-REVIEW-PASS`, else `/review-spec <slug>`; `planned`/`in-progress` → `/execute-phase <NN>` only on a
-  current `PLAN-REVIEW-PASS`, else `/review-plan <NN>` (step 6a)
+  `/unit-lane`) AND the script computed it from the unit's resolved status:
+  `idea`/`defined` → `/unit-lane <slug>` (or `/unit-lane --fix <n>` for a fix);
+  `planned`/`in-progress` → `/execute-phase <NN>` (its triage block is the
+  authority; no separate plan-receipt currency check, step 6a)
 ✓ `detail.crash_recovery` carries a verdict from the decision table and the
   envelope `state` matches it (CLEAN→OK, RESUMABLE→CONTINUE,
   AMBIGUOUS→NEEDS_INPUT)
-✓ Every `detail.design_candidates[].next` begins with `/design-feature `
+✓ Every `detail.design_candidates[].next` begins with `/unit-lane `
 ✓ Every degraded dimension is named in `detail.degradations` as
   `unavailable-<source>-<cause>` — and, when `--last-envelope` was supplied, the
   no-progress guard's `workflow_observations` note is present (never a silently
@@ -99,11 +98,11 @@ the JSON contract.
 
 ## Relationship to other skills
 
-- The **sensor** counterpart to `ship-roadmap`'s conductor: an external
-  orchestrator calls `workflow-status` → routes on the envelope → invokes
-  `plan-feature` / `execute-phase` / `review-change` / `audit-pr` /
-  `triage-issue` directly, choosing the model per step — the same loop without
-  the in-agent autopilot.
+- The **sensor** counterpart to `advance`'s conductor: an external
+  orchestrator (or `advance` itself) calls `workflow-status` → routes on the
+  envelope → invokes `unit-lane` / `execute-phase` / `review-change` /
+  `audit-pr` / `triage-issue` directly, choosing the model per step — the same
+  loop without the in-agent autopilot.
 - Read-only sibling of `audit-docs` (which judges coherence and can fix) and
   `product-audit` (which judges health): this one only reports state.
 - Schema owner: `orchestration-envelope` (internal).
@@ -118,7 +117,7 @@ the JSON contract.
   `detail.crash_recovery` were read from the envelope, and the envelope `state`
   matches the crash-recovery verdict.
 - With `--last-envelope` supplied: the no-progress guard ran — a stalled
-  `/plan-feature`/`/design-feature` hint surfaces as a `workflow_observations`
+  `/unit-lane` hint surfaces as a `workflow_observations`
   note, never a silent bland repeat, with no new write path introduced.
 - The human summary (unless `--json-only`) and the envelope are printed, envelope
   last.

package/skills/workflow-status/references/CRASH_RECOVERY.md

@@ -23,12 +23,12 @@ section *classifies*; the resume command it recommends does the acting.
   caller's persisted envelope against the recomputed state and report the
   divergence in one line. The hint never overrides recomputed state.
 - ✓ **No-progress guard (optional, requires `--last-envelope`).** When the
-  hint's `next.recommended` was `/plan-feature <slug>` or `/design-feature
-  <slug>` for a given unit, and this run's own recomputed status for that
-  **same unit** is still at the **same pre-advance status** the hint expected
-  to move it off of (`defined` for a `/plan-feature` hint; `idea` for a
-  `/design-feature` hint) — either the recommended command ran but its status
-  write was dropped, or it never ran at all; this guard cannot distinguish the
+  hint's `next.recommended` was `/unit-lane <slug>` for a given unit, and this
+  run's own recomputed status for that **same unit** is still at the **same
+  pre-advance status** the hint expected to move it off of (`idea`/`defined` —
+  the lane's triage write lands when the unit doc is created) — either the
+  recommended command ran but its status write was dropped, or it never ran at
+  all; this guard cannot distinguish the
   two from the envelope alone, so the note names it as a **suspected** stall,
   not a confirmed dropped write. Emit a `workflow_observations` note (see
   `## Machine envelope` for the exact note shape). This is strictly additive:

package/skills/workflow-status/references/ENVELOPE_CORE.md

@@ -108,15 +108,12 @@ the key's presence.
 |---|---|
 | `/discover-repository-state` | `strong` |
 | `/resolve-repository-state` | `strong` |
-| `/plan-feature` | `strong` |
-| `/design-feature` | `strong` |
+| `/unit-lane` | `strong` |
 | `/review-change` | `strong` |
 | `/audit-pr` | `strong` |
 | `/triage-issue` | `strong` |
 | `/product-audit` | `strong` |
 | `/execute-phase` | `cheap` |
-| `/review-spec` | `strong` |
-| `/review-plan` | `strong` |
 
 `next.tier` is read off this map by matching the resolved `next.recommended`
 command's name (ignoring its arguments) — never guessed and never copied from

package/skills/workflow-status/references/ENVELOPE_FIELDS.md

@@ -2,12 +2,12 @@
 
 **No-progress guard note (`workflow_observations`, requires `--last-envelope`,
 see the crash-recovery checklist above)** — when the hint's `next.recommended`
-targeted `/plan-feature <slug>` or `/design-feature <slug>` and this run still
+targeted `/unit-lane <slug>` and this run still
 classifies that same unit at the same pre-advance status, append a note of the
 exact shape:
-`"<slug> still 'defined' after the hint's /plan-feature <slug> recommendation — suspected dropped defined→planned write (see #51)"`
-(swap `defined`/`/plan-feature` for `idea`/`/design-feature` on the design
-side). The recommendation itself is unaffected — this only adds visibility.
+`"<slug> still 'defined' after the hint's /unit-lane <slug> recommendation — triage not yet applied"`
+(the note fires for a `defined` unit; the lane's triage write is what moves it
+off `idea`/`defined`). The recommendation itself is unaffected — this only adds visibility.
 
 **Shape vs. current output — read this before trusting the example below.** The
 example is the envelope's **intended shape**, not everything the deterministic
@@ -33,10 +33,10 @@ absent-legacy` or `issues_born.n: 0`; the owning note is
   "dependencies": {"unmet": [], "build_order": []},
   "recommendations": {"product_audit": false, "reason": null},
   "needs_input": null,
-  "next": {"recommended": "/review-change", "alternatives": ["/plan-feature 05"], "tier": "strong",
+  "next": {"recommended": "/review-change", "alternatives": ["/unit-lane 05"], "tier": "strong",
            "suggested": [{"command": "/review-change", "trigger": "accumulation: 420 changed lines since last-reviewed sha", "source_skill": "execute-phase"}]},
   "detail": {
-    "design_candidates": [{"id": "08-billing-webhooks", "status": "idea", "next": "/design-feature 08-billing-webhooks"}],
+    "design_candidates": [{"id": "08-billing-webhooks", "status": "idea", "next": "/unit-lane 08-billing-webhooks"}],
     "pre_execution": [{"unit": "12-export-api", "unitDir": "docs/features/12-export-api", "stage": "lane", "label": "current", "verdict": "READY", "boundDigest": null, "observedDigest": null, "recommended": "/unit-lane 12-export-api", "reason": "unit-doc currency is checked per step by unit-lane/execute-phase"}],
     "features": [
       {"id": "07-csv-export", "status": "in-progress", "deps": ["01"], "deps_unmet": [],
@@ -87,7 +87,7 @@ fully in `features`/`fixes` — an `idea` unit appears ONLY in
 `design_candidates` (and `detail.features`), never in `startable_now`, since
 it has no deps-met check to pass (design precedes dependency startability).
 `05-auth` above illustrates `defined` (not yet `planned`): startable, next
-`/plan-feature`, phase fields null (no planning artifacts yet).
+`/unit-lane`, phase fields null (no planning artifacts yet).
 
 ## The `--compact` projection
 

package/skills/workflow-status/references/PRE_EXECUTION.md

@@ -1,5 +1,10 @@
 ## Pre-execution receipt sensing (step 6a)
 
+> **Legacy (feature 61 P8b):** the spec/plan pre-execution receipt stages are
+> retired — the sensor now senses the unit doc's single triage block
+> (`stage: lane`, see `ENVELOPE_FIELDS.md`). This reference is retained for
+> units that still carry those receipts; the live sensing is the `lane` stage.
+
 Roadmap status says what exists; only a receipt bound to the current bytes says
 whether the unit may be executed. Sense it like every other signal — read the file,
 recompute the digest, never trust the prose sitting around the block.

package/skills/workflow-status/references/SENSOR_SIGNALS.md

@@ -145,5 +145,5 @@ mechanized.*
     `CRASH RECOVERY` sub-block to the report.
 18. **Report.** Print a short human summary (table: unit | status | deps unmet |
     PR | next gate) plus a **design candidates** line (`idea` units and their
-    `/design-feature` next command) plus the `CRASH RECOVERY` sub-block, then
+    `/unit-lane` next command) plus the `CRASH RECOVERY` sub-block, then
     the envelope. With `--json-only`, envelope only.