@gtrabanco/pi-agentic-workflow 0.13.2 → 0.14.0

package/skills/init-workspace/references/BOOTSTRAP_WRITE.md

@@ -1,11 +1,13 @@
 ## Write and verify the bootstrap
 
-4. **Write the adapted scaffold.** Fill the `CLAUDE.md` placeholders (commands,
-   the documentation map rows, architecture); keep `AGENTS.md`, the
-   `features/_TEMPLATE` + `ROADMAP`, the `fix/_TEMPLATE` + `README`, and the
-   `.github/` templates; keep `.agentic-workflow/hooks/` and activate only the
-   adapters explicitly accepted in the interview; prune unused doc folders and
-   map rows. Leave honest placeholders where the user hasn't decided — never
+4. **Write the adapted scaffold.** Fill the `AGENTS.md` placeholders (commands,
+   the documentation map rows, architecture); write the **adaptive lane
+   conventions** (unit document, triage, catalog steps, guards, evidence rows,
+   dated progress log, closed commit format `type(scope): description`); keep
+   the `features/_TEMPLATE` + `ROADMAP`, the `fix/_TEMPLATE` + `README`, and
+   the `.github/` templates; keep `.agentic-workflow/hooks/` and activate only
+   the adapters explicitly accepted in the interview; prune unused doc folders
+   and map rows. Leave honest placeholders where the user hasn't decided — never
    invent values.
 5. **Seed Normalized Repository State.** Copy
    `template/docs/workflow/REPOSITORY_STATE.md` to
@@ -19,6 +21,10 @@
    optional: an absent document means no project invariants are declared, not
    that the scaffold failed. If retained, add its documentation-map row and
    name the project's explicit architectural-decision authority.
+6. **Propagate the unit doc template.** Ensure
+   `docs/features/_TEMPLATE/SPEC.md` exists with all 13 mandatory sections.
+   This is the template used when creating new unit documents.
+
 7. **Install accepted agent safety hooks.** Keep the canonical policy and
    fullauto wrapper at `.agentic-workflow/hooks/`. Seed the shipped
    path-protection policy at `.agentic-workflow/path-policy.json` and its doc
@@ -41,7 +47,7 @@
    `review-a11y`, `review-brand`, `review-perf`, `review-seo`) — it installs
    with the skills and covers every review axis, so **no external review skill
    is required on any agent**. If the user wants platform-specific extras (a
-   framework skill, a stack-specific security skill), record them in `CLAUDE.md`
+   framework skill, a stack-specific security skill), record them in `AGENTS.md`
    under a short "Optional review extras" note so `review-change` and
    `product-audit` run them **in addition** — never as a dependency. Don't
    install anything without a yes.
@@ -58,7 +64,8 @@
    forge is unavailable or the user declines forge setup, skip this step and
    list the two labels as a residual for the user to create manually later
    (never fail the whole scaffold on it).
-11. **Report.** List what was created, which placeholders still need human input,
+12. **Report.** List what was created, which placeholders still need human input,
    the companion skills recorded/installed, the urgency labels seeded (or
-   skipped, with reason), and the next step: `discover-repository-state` →
-   `design-feature` → `plan-feature` → `execute-phase`.
+   skipped, with reason), and the next step:
+   `discover-repository-state` → `/unit-lane` (or `workflow-status`) → catalog
+   steps → `execute-phase`.

package/skills/init-workspace/references/PORTABILITY.md

@@ -7,7 +7,7 @@ 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.
-- **No per-skill `model:`/`effort:`** — on the `#claude` branch the frontmatter pins these tiers; here, pick tiers yourself:
+- **No per-skill `model:`/`effort:`** — no skill pins a tier; pick tiers yourself:
   the interview and adaptation are judgment work — run them on your
   **strongest** model.
 - **No Claude Code hooks** — choose the Cursor, Copilot, or OpenCode adapter

package/skills/init-workspace/references/UPGRADE.md

@@ -4,13 +4,14 @@ Entered when Step 0 finds an existing **agentic-workflow scaffold** (not a
 bare or foreign repo). Bootstrap mode (the Process section above) never
 engages here — upgrade mode reuses the same discovery + interview machinery,
 scoped to **only the blocks the current template has that this project
-lacks**. Seven ordered steps:
+lacks**. Eight ordered steps:
 
 1. **Locate the current template.** Fetch the current `template/` the same
    way bootstrap does — `npx degit gtrabanco/agentic-workflow/template <temp-dir>`
    (always into a temp dir here, never into the target); the SSH/local-path
    variant applies verbatim for a private source.
-2. **Diff the substrate.** Compare the project's `CLAUDE.md` (and the `docs/`
+2. **Diff the substrate.** Compare the project's agent guide (`AGENTS.md`,
+   or a legacy `CLAUDE.md`) (and the `docs/`
    blocks its documentation map references) against the fetched template.
    Produce the list of blocks/conventions the template carries that this
    project's substrate lacks, or still holds as a raw, unfilled placeholder —
@@ -32,13 +33,23 @@ lacks**. Seven ordered steps:
    dated migration note so the proposal explains *why* the block exists and
    *what* it migrates. If `MIGRATION.md` is absent, proceed on the template
    diff alone and say so in the report — never block on a missing note.
-4. **Propose only the missing blocks — one short, batched interview round.**
-   Each item is the block, a discovery-based default (the same detection
-   bootstrap mode already runs — e.g. `astro.config.*` + Starlight ⇒ `Docs
-   site` default, Biome ⇒ the complexity-lint slot, the remote URL ⇒ forge),
-   and the `MIGRATION.md` rationale when available. The user accepts, edits,
-   or skips each block. **Never re-ask what the project already answered** —
-   a block that's already filled is skipped, not re-interviewed.
+4. **Propose the adaptive lane conventions (feature 61 P11).** For pre-lane
+   installs (before the fixed pipeline was retired), propose these missing
+   blocks additively — **never clobber existing content**:
+   - The **unit document conventions** section in AGENTS.md (the 13-section
+     SPEC.md, triage-driven step selection, diff-size guard, evidence rows,
+     dated progress log, closed commit format `type(scope): description`).
+   - The **unit doc template** under `docs/features/_TEMPLATE/SPEC.md` if
+     absent — the same 13-section template used by new units.
+   - The **lane workflow doc** under `docs/workflow/` if absent: `FEATURE_WORKFLOW.md`
+     (unit doc → triage → catalog steps → evidence → review → release),
+     `ISSUE_WORKFLOW.md` (issues route through triage to the lane).
+   - A **documentation-map row** for `docs/features/_TEMPLATE/SPEC.md` and the
+     lane workflow docs if missing from the existing map.
+   Each item is accepted, edited, or skipped by the user. **Never re-ask what
+   the project already answered** — a block that's already filled is skipped,
+   not re-interviewed. The lane conventions are additive only: existing content
+   is never rewritten, only new blocks are inserted where missing.
 5. **Write additively.** Insert accepted blocks, including a missing
    `docs/workflow/REPOSITORY_STATE.md`; fill raw, still-placeholder
    blocks with the confirmed values. **Never rewrite a block the project has
@@ -50,16 +61,39 @@ lacks**. Seven ordered steps:
    `path-protection.md` page are proposed from the template; an existing
    owner-written `path-policy.json` is never clobbered and is listed as a
    residual instead. Leave honest placeholders where the user skipped.
-6. **Seed missing urgency labels, additively (feature 15).** Independent of
-   the `CLAUDE.md`/`docs/` block diff above (this is forge-repo state, not a
+6. **Retire the legacy `CLAUDE.md` — only with an explicit yes, never as a side
+   effect.** Older releases of this workflow wrote the guide as `CLAUDE.md`;
+   current ones write `AGENTS.md`, and current Claude Code reads `AGENTS.md`.
+   When the project has a `CLAUDE.md`, three ordered moves — never skip (a):
+   a. **Reconcile first.** Diff `CLAUDE.md` against `AGENTS.md` and fold every
+      block, rule, or value that exists only in `CLAUDE.md` into `AGENTS.md`,
+      keeping the project's own wording and values. Name each folded item in the
+      report; when nothing is unique, say that plainly instead of implying a
+      merge happened.
+   b. **Then ask once, stating the risk.** A user may deliberately be on a Claude
+      Code release that reads only `CLAUDE.md`, and deleting the file would stop
+      their agent from seeing the guide at all. Present the choice as remove
+      (one guide, nothing left to drift) or keep (older client), and take the
+      answer. Never delete a tailored `CLAUDE.md` because "the template moved
+      on".
+   c. **On yes:** delete `CLAUDE.md`, keeping the reconciliation from (a) already
+      written. **On keep:** leave the file byte-identical and list it as a
+      residual naming the reason (the user's client still reads it) — a kept
+      legacy guide is a decision, not drift.
+
+   This step is the only writer of `CLAUDE.md` in upgrade mode, and it is never
+   reached without the answer from (b).
+7. **Seed missing urgency labels, additively (feature 15).** Independent of
+   the agent-guide/`docs/` block diff above (this is forge-repo state, not a
    doc block): check whether the target repo already has the `urgent` and
    `fix-next` labels (`gh label list`); create whichever is missing with the
    same `gh label create` calls bootstrap mode uses (see Process step 9) —
    never touch a label that already exists (additive-only, same never-clobber
    rule as the doc blocks; a pre-existing `urgent`/`fix-next` label the
    project recolored or redescribed is left exactly as-is).
-7. **Report + hand off.** Summarize blocks added, filled, and skipped
-   (residuals), the urgency labels seeded (or already present), then print the
+8. **Report + hand off.** Summarize blocks added, filled, and skipped
+   (residuals), the legacy `CLAUDE.md` outcome (folded items and removed, or kept
+   with the reason), the urgency labels seeded (or already present), then print the
    recommendation to run `product-audit` next to see which newly-available
    *capabilities* apply to the code (upgrade mode migrates the substrate only,
    never the code).
@@ -81,8 +115,9 @@ lacks**. Seven ordered steps:
   separately, via an explicit bootstrap adapt-in-place run, whether to
   re-tailor it.
 - **Bootstrap stays unchanged on a bare or foreign repo.** If Step 0's
-  scaffold markers (`CLAUDE.md` + `docs/features/ROADMAP.md` or
-  `docs/workflow/`) are absent — no repo, an empty repo, or a `CLAUDE.md`
+  scaffold markers (an agent guide — `AGENTS.md` or a legacy `CLAUDE.md` — plus
+  `docs/features/ROADMAP.md` or
+  `docs/workflow/`) are absent — no repo, an empty repo, or a guide
   that isn't this workflow's — upgrade mode never engages; the existing
   bootstrap Process (merge/adapt/abort) runs exactly as before this mode was
   added.

package/skills/log-session/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: log-session
 user-invocable: true
-version: 2.2.0
+version: 2.2.1
 argument-hint: "[note to prepend to the entry]"
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
@@ -9,8 +9,9 @@ description: >
   Append a structured entry to the project's session log (`docs/LOGS.md`):
   what was done this session, files touched, decisions taken, and the next
   step — so the next session (or another person) can pick up the thread
-  without re-reading git history. Run it before `/clear`, before closing
-  Claude Code, or at any natural stopping point. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using.
+  without re-reading git history. Run it before `/clear`, before closing your
+  agent session, or at any natural stopping point. Model-agnostic: the skill
+  inherits whatever model and effort your agent session is already using.
   Triggers: "log this
   session", "log-session", "write a session log", "journal what we did",
   "record this session before I clear", "save the session summary".

package/skills/orchestration-envelope/references/TURN_CONTRACT.md

@@ -41,7 +41,7 @@ preserving the fixed block shape.
 turn-contract-receipt@1
 ok-line:    TURN-CONTRACT ok
 fail-line:  TURN-CONTRACT fail box<N>: <code>
-codes:      branch-default | not-a-repo | no-commits | acceptance-missing |
+codes:      branch-default | not-a-repo | no-commits | unit-doc-missing |
             phase-lint-failed | pr-not-open | pr-head-mismatch |
             pr-unreachable | dirty-tree | ahead-of-remote
 exit:       0 ok | 1 contract fail | 2 usage error

package/skills/pre-execution-review/references/LEDGERS.md

@@ -6,9 +6,9 @@ Plan snapshot binds them, and `execute-phase` may not invent a substitute.
 
 | Ledger | Home | Written by | Read by |
 |---|---|---|---|
-| Planning evidence | `planning-evidence.md` (M/L) · `### Planning evidence` inside the SPEC (XS/S) | the authoring planner | `review-plan`, then the phase slice for `execute-phase` |
-| Obligations | `planning-obligations.md` (M/L) · `### Obligations` inside the SPEC (XS/S) | the authoring planner, then the phase owner for `status` | `review-plan`, `execute-phase`, `fold-findings`, `audit-pr` |
-| Findings | `planning-findings.md` (one per unit, both stages) | reviewers append; only the stage's author resolves | the author skill, `review-plan` on re-review, `audit-pr` |
+| Planning evidence | `### Planning evidence` inside the unit doc (XS/S) · separate file (M/L) | `unit-lane:planning-evidence` | `execute-phase`, `fold-findings`, `audit-pr` |
+| Obligations | `### Obligations` inside the unit doc (XS/S) · separate file (M/L) | `unit-lane:obligations` | `execute-phase`, `fold-findings`, `audit-pr` |
+| Findings | `review-findings.md` (one per unit, both stages) | reviewers append; only the stage's author resolves | `execute-phase` on re-review, `audit-pr` |
 
 XS/S embeds both tables in the SPEC to stay within the size's artifact budget;
 the Plan snapshot then binds them through the whole-SPEC row (kind `spec`), and
@@ -19,10 +19,9 @@ M/L freeze the separate files and bind them with their own rows. Never both.
 
 Row shape — the base row, the closed `authority-kind` / `freshness` vocabularies,
 the prefixed stable `id`, and the `affected-decision-or-obligation` Plan-stage
-extension with its full column order — is owned by the `evidence-grounding`
-reference `ROWS.md` (§ "Plan-stage table — one declared extension"): one
-definition, no second copy. This ledger owns only the lifecycle rules and uses
-markdown headings, nothing else. Ids are stable (`PE-001`, `PE-002`, …): an
+extension with its full column order — is owned by the unit-lane's planning
+reference: one definition, no second copy. This ledger owns only the lifecycle
+rules and uses markdown headings, nothing else. Ids are stable (`PE-001`, `PE-002`, …): an
 obligation or finding cites a row by id, so renumbering the table is a replan,
 not a formatting edit.
 
@@ -36,8 +35,8 @@ Rules specific to this ledger:
 - An assumption about a model's or service's behaviour that was never sampled is
   `unknown` with an owner — `ASSUMPTION-UNVERIFIED` is what the row *means*, and
   the row must stay visible in the artifact rather than becoming a citation.
-- `review-plan` reads the whole table; `execute-phase` reads only the rows whose
-  `affected-decision-or-obligation` names its frozen phase.
+- `execute-phase` reads only the rows whose `affected-decision-or-obligation`
+names its frozen phase; the unit-lane plans the table before `execute-phase` runs.
 
 ### 2. Obligations
 
@@ -101,9 +100,9 @@ status | resolution-evidence | resolving-artifact-revision
 - `status` is `open | resolved | dismissed`. `dismissed` requires
   counter-evidence that falsifies the finding ([POLICY.md](POLICY.md) §2); the
   evidence goes in `resolution-evidence`, not in chat.
-- The author resolves a row through its own route: `design-feature` for
-  `class: product`, `plan-feature` / `plan-fix` for `class: plan`, and the
-  candidate loop (`review-change` → `fold-findings`) only for
+- The author resolves a row through its own route: `unit-lane` for
+  `class: product` and `class: plan`, and the candidate loop
+  (`review-change` → `fold-findings`) only for
   `class: source | environment | runtime`.
 - `resolving-artifact-revision` is the `artifactRevisionId` of the write that
   closed the row — the link that lets a re-review prove the snapshot actually
@@ -125,41 +124,41 @@ its `· fold <sha>` (or `· ticked <sha>` on a row that scores 1) plus the
 annotation — never a `yes` of its own.
 
 `scripts/ledger-ownership.test.mjs` reads the block below as the single source of
-truth for the seven AC16 truth classes and the projections in
-`docs/features/_TEMPLATE/LEDGERS.md` and `docs/fix/_TEMPLATE/LEDGERS.md` as its
-copies. It fails closed on a missing or malformed block, an owner-less row, drift
-in either direction, a token the annotator cannot produce, and any non-test script
-under `scripts/` or `packages/<name>/scripts/` whose write or append target names a
-durable ledger its row does not name it for. Cells carry bare values: ` · ` joins
-ledgers, ` + ` joins owners, an owner is `<skill>:<column-set>` (the literal
-`human-owner` marks the person, the only authority for an amendment), and a `#`
-line is a directive. A script that writes only generated artifacts names no ledger
-and is out of scope; a copy or shell rewrite stays the reviewer's job. Validator
-commands follow the repository's runtime convention: **bun first** (`bun test …`),
-with the same command under `node --test …` when bun is absent — both runtimes
-must pass; the CI node-compat job enforces the fallback.
+truth for the seven AC16 truth classes and the projection in
+`docs/fix/_TEMPLATE/LEDGERS.md` as its copy (the features-template projection
+was retired at P8b). It fails closed on a missing or malformed block, an owner-less
+row, drift in either direction, a token the annotator cannot produce, and any
+non-test script under `scripts/` or `packages/<name>/scripts/` whose write or append
+target names a durable ledger its row does not name it for. Cells carry bare values:
+` · ` joins ledgers, ` + ` joins owners, an owner is `<skill>:<column-set>` (the
+literal `human-owner` marks the person, the only authority for an amendment), and a
+`#` line is a directive. A script that writes only generated artifacts names no
+ledger and is out of scope; a copy or shell rewrite stays the reviewer's job.
+Validator commands follow the repository's runtime convention: **bun first**
+(`bun test …`), with the same command under `node --test …` when bun is absent —
+both runtimes must pass; the CI node-compat job enforces the fallback.
 
 ```text
 ledger-ownership@1
 truth-class | ledger | owner | annotator | annotator-token | validator
 review-findings | docs/features/<NN>-<slug>/review-findings.md · docs/fix/<issue>-<topic>/review-findings.md | review-change:finding-rows + review-change:finding-mark + review-change:review-mark + review-change:review-gate-ran-marks + audit-pr:audit-rows + triage-issue:triage-rows + execute-phase:gate-ran-marks + fold-findings:folded-flag | scripts/ledger-provenance.mjs | · fold <sha> + · ticked <sha> + · REOPENED | bun test scripts/ledger-provenance.test.mjs
-planning-findings | docs/features/<NN>-<slug>/planning-findings.md · docs/fix/<issue>-<topic>/planning-findings.md | review-spec:spec-stage-rows + review-plan:plan-stage-rows + design-feature:product-class-resolutions + plan-feature:plan-class-resolutions + plan-fix:fix-plan-class-resolutions + fold-findings:source-class-resolutions | none | none | bun test scripts/pre-execution-quality.test.mjs
-progress | docs/features/<NN>-<slug>/progress.md · docs/fix/<issue>-<topic>/progress.md | plan-feature-scaffold:create + execute-phase:phase-entries + execute-phase:gate-rejection-traces + review-spec:product-receipt + review-plan:plan-receipt | none | none | bun test scripts/pre-execution-sensor.test.mjs
-known-issues | docs/features/<NN>-<slug>/known-issues.md · docs/fix/<issue>-<topic>/known-issues.md | plan-feature-scaffold:create + execute-phase:blocker-entries-and-status | none | none | bun test scripts/ledger-ownership.test.mjs
-decisions | docs/features/<NN>-<slug>/decisions.md · docs/fix/<issue>-<topic>/decisions.md | plan-feature-scaffold:create + design-feature:product-decisions + plan-feature:engineering-decisions + execute-phase:phase-decisions + human-owner:ratified-verdicts | none | none | bun test scripts/ledger-ownership.test.mjs
-roadmap | docs/features/ROADMAP.md · docs/fix/README.md | design-feature:idea-or-defined-row + plan-feature-scaffold:planned-row + plan-fix:fix-index-row + execute-phase:status-and-pr-link + ship-roadmap:founding-and-flip + audit-docs:low-risk-row-repair | none | none | bun test scripts/bounded-delivery-loops.test.mjs
-acceptance-manifest | docs/features/<NN>-<slug>/ACCEPTANCE.md · docs/fix/<issue>-<topic>/ACCEPTANCE.md | plan-feature-scaffold:feature-freeze + plan-fix:fix-freeze + human-owner:approved-amendment | none | none | git hash-object docs/features/<NN>-<slug>/ACCEPTANCE.md
+planning-findings | docs/features/<NN>-<slug>/planning-findings.md · docs/fix/<issue>-<topic>/planning-findings.md | unit-lane:planning-findings + fold-findings:source-class-resolutions | none | none | bun test scripts/pre-execution-quality.test.mjs
+progress | docs/features/<NN>-<slug>/SPEC.md · docs/fix/<issue>-<topic>/SPEC.md | unit-lane:progress-entries + execute-phase:phase-entries + execute-phase:gate-rejection-traces | none | none | bun test scripts/pre-execution-sensor.test.mjs
+known-issues | docs/features/<NN>-<slug>/known-issues.md · docs/fix/<issue>-<topic>/known-issues.md | unit-lane:known-entries + execute-phase:blocker-entries-and-status | none | none | bun test scripts/ledger-ownership.test.mjs
+decisions | docs/features/<NN>-<slug>/decisions.md · docs/fix/<issue>-<topic>/decisions.md | unit-lane:decisions + execute-phase:phase-decisions + human-owner:ratified-verdicts | none | none | bun test scripts/ledger-ownership.test.mjs
+roadmap | docs/features/ROADMAP.md · docs/fix/README.md | unit-lane:row-registration + execute-phase:status-and-pr-link + audit-docs:low-risk-row-repair | none | none | bun test scripts/bounded-delivery-loops.test.mjs
+acceptance-manifest | docs/features/<NN>-<slug>/ACCEPTANCE.md · docs/fix/<issue>-<topic>/ACCEPTANCE.md | unit-lane:acceptance-freeze + human-owner:approved-amendment | none | none | git hash-object docs/features/<NN>-<slug>/ACCEPTANCE.md
 # no-script-writer: SPEC.md · PLAN.md · TASKS.md · CHECKLIST.md · testing.md · architecture-notes.md · planning-evidence.md · planning-obligations.md · delegated-evidence.md
 ```
 
 `SPEC.md`, `PLAN.md`, `TASKS.md`, `testing.md` and `architecture-notes.md` are
 durable unit records, but not ledgers with a row lifecycle of their own: their
-writers are the phases that already order them (`plan-feature-scaffold` creates
-them, `execute-phase` ticks and appends), so the directive line keeps any script
-away from them instead of forking the table above. Same for the two frozen
-planning ledgers at the top of this file, and for `delegated-evidence.md`: a
-versioned artifact of a delegated reading pass, whose writer and zones are stated
-by `evidence-grounding`'s `references/DELEGATION.md`, not by this map.
+writers are the phases that already order them (`unit-lane` creates them, `execute-phase`
+ticks and appends), so the directive line keeps any script away from them instead
+of forking the table above. Same for the two frozen planning ledgers at the top
+of this file, and for `delegated-evidence.md`: a versioned artifact of a delegated
+reading pass, whose writer and zones are stated by the triage/research step's
+documentation, not by this map.
 
 ### The durable review mark
 
@@ -236,7 +235,8 @@ GATE-RAN | HEAD <40-hex sha> | <cmds> | exit <code> | [reserved trailing slot: `
   declares `execute-phase:gate-ran-marks` (executor phase gates) and
   `review-change:review-gate-ran-marks` (reviewer gate runs), distinct column-set
   names per the one-writer-per-column-set rule.
-- **Owner extension**: the identical owner cell is mirrored into both template
-  projections (`docs/features/_TEMPLATE/LEDGERS.md` and `docs/fix/_TEMPLATE/LEDGERS.md`).
+- **Owner extension**: the identical owner cell is mirrored into the fix-template
+  projection (`docs/fix/_TEMPLATE/LEDGERS.md`); the features-template projection
+  was retired at P8b because the unit doc carries its evidence sections.
 - **No new truth-class row**: the grammar admits no new row — the existing
   `review-findings.md` ledger pattern is reused with extended owner cells.

package/skills/pre-execution-review/references/POLICY.md

@@ -218,6 +218,7 @@ reports; a printed verdict whose mark is still "for next turn" is not finished.
   phase-lint | PREFLIGHT.md
   path-protection | PREFLIGHT.md
   stale-or-missing-receipt | PRE_EXECUTION_GATE.md
+  stale-unit-doc | PRE_EXECUTION_GATE.md
   ```
 
   `execute-phase` appends that trace to the unit's `progress.md`, under

package/skills/product-audit/SKILL.md

@@ -2,7 +2,7 @@
 name: product-audit
 user-invocable: true
 disable-model-invocation: true
-version: 3.2.0
+version: 3.2.1
 metadata:
   opencode/autoinvoke: false
 argument-hint: <path-or-area> (optional — defaults to the whole product)
@@ -125,7 +125,7 @@ Verdict: <one-line honest health verdict>
   (none — <why>)
 
 ### Tooling — register / re-design
-  - <skill|MCP> — register in CLAUDE.md (Optional review extras): <why> — route: user edits CLAUDE.md
+  - <skill|MCP> — register in AGENTS.md (Optional review extras): <why> — route: user edits AGENTS.md
   - <skill|MCP> — would change <feature> scope: <why> — route: /design-feature <slug>
   (none — <why>)
 
@@ -161,7 +161,7 @@ security items to track first").
   lineage lives only in Delta mappings as `<audit-id> F<k>`, never global slugs or
   replaced ids. When the user accepts, route: `triage-issue` files/classifies,
   `plan-feature` adds roadmap work, `plan-fix` scopes a concrete fix.
-- **Never registers tooling or edits `CLAUDE.md`.** The tooling sweep proposes a
+- **Never registers tooling or edits `AGENTS.md`.** The tooling sweep proposes a
   skill/MCP to register, but the user (or a routed `design-feature` run)
   performs the edit; a scope-affecting discovery routes to
   `/design-feature <slug>`, which the user approves.
@@ -201,7 +201,7 @@ product-audit (whole product, all axes, periodic)
    └─ proposes ─┬─ Issues to open ........ ▶ triage-issue / plan-fix
                 ├─ Roadmap: add .......... ▶ plan-feature
                 ├─ Roadmap: remove/revise  ▶ triage-issue / roadmap edit   (user decides)
-                └─ Tooling: register/re-design ▶ user edits CLAUDE.md / design-feature
+                └─ Tooling: register/re-design ▶ user edits AGENTS.md / design-feature
 ```
 
 - Broader than `review-change` (one change) and `audit-pr` (one PR); subsumes

package/skills/product-audit/references/AUDIT_PROCESS.md

@@ -41,9 +41,9 @@ step (2–5). Each item ends with exactly one fallback; never pick another one m
 5. **Sweep installed tooling** — (a) inventory the installed skills and
    connected MCP servers available to the agent; (b) cross-reference each
    against the applicable review axes and the roadmap features; (c) classify
-   each as **register** (useful, not yet named in the project's `CLAUDE.md`),
+   each as **register** (useful, not yet named in the project's `AGENTS.md`),
    **re-design** (would change a feature's definition/scope), or
-   **not-relevant**; (d) dedupe against what `CLAUDE.md` already registers —
+   **not-relevant**; (d) dedupe against what `AGENTS.md` already registers —
    only unregistered/relevant items survive into proposals. If the agent
    cannot enumerate its installed skills / connected MCPs, say so plainly
    (no silent caps) rather than inventing an inventory.
@@ -54,7 +54,7 @@ step (2–5). Each item ends with exactly one fallback; never pick another one m
    - **Roadmap: remove or revise** — features that are obsolete, superseded, or no
      longer make sense.
    - **Tooling: register or re-design** — unregistered-but-useful tooling to add
-     to `CLAUDE.md`, or a discovered skill/MCP that would rescope a feature.
+     to `AGENTS.md`, or a discovered skill/MCP that would rescope a feature.
 7. **Number the findings.** Assign every finding in the severity-ranked list a
    sequential id `F1, F2, …` — **one single `F` sequence for the whole audit**,
    in ranked order, regardless of dimension. Never use a different letter per

package/skills/review-change/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: review-change
 user-invocable: true
-version: 3.7.0
+version: 3.7.1
 argument-hint: <path-or-glob> [--adversarial N] [--synthesize]
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT

package/skills/review-change/references/PORTABILITY.md

@@ -13,7 +13,7 @@ enables:
   tiers as `--adversarial N` (subagents / headless / fresh conversations); an
   agent with none of them runs the documented inline fallback: sequential
   in-turn passes, each reduced to its findings table before the next starts.
-- **No per-skill `model:`/`effort:`** — on the `#claude` branch the frontmatter pins these tiers; here, pick tiers yourself:
+- **No per-skill `model:`/`effort:`** — no skill pins a tier; pick tiers yourself:
   this review needs your **strongest** model. Never review a change with a
   model weaker than the one that wrote it — and prefer a different model family
   than the writer's: same-family instances share training blind spots,

package/skills/unit-lane/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: unit-lane
+user-invocable: true
+version: 1.0.0
+argument-hint: <NN-slug | "<idea>"> [--retriage]
+description: >
+  One-shot lane conductor for a delivery unit: triage, implement, evidence, and
+  close in a single document. Triggers: "unit-lane", "run the lane",
+  "work on this feature/fix", "build this unit".
+---
+
+# Unit Lane — Adaptive Conductor
+
+One document, adaptive steps. The lane reads a closed catalog, triages which
+steps a unit needs, executes them in order, and commits at each gate. Replaces:
+design-feature, plan-feature, review-spec, review-plan.
+
+## Turn contract
+
+Tick every box before ending the turn; an unchecked box means the turn is not
+done:
+
+```
+✓ Triage ran (bun scripts/unit-route.mjs --triage <slug>) and its block pasted
+  verbatim into the unit doc's Evidence section as the authoritative step list
+✓ Unit doc exists at docs/features/<NN>-<slug>/SPEC.md (created from template
+  if new, with all mandatory sections filled or n/a)
+✓ Guard ran (bun scripts/diff-guard.mjs --base <ref>) after each implement step;
+  on BREACH: re-triage or record exception, never shrink the diff
+✓ Unit doc's Evidence rows updated (command → exit/digest → output → verified-by)
+  and Progress log updated (dated entry) before every commit
+✓ → Next: block printed as the absolute last output
+```
+
+## When to use
+
+- A known unit slug: `unit-lane <NN-slug>`
+- A raw idea (no slug yet): `unit-lane "<idea description>"`
+- Force re-triage: `unit-lane <NN-slug> --retriage`
+
+## Step 0 — Discover the project
+
+Per the agent guide's **Workflow conventions** + **documentation map**, then read
+`docs/features/_TEMPLATE/SPEC.md` (the unit doc template). If the unit folder
+exists, read its current `SPEC.md` to avoid overwriting.
+
+## Process
+
+### 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
+[the unit doc template](references/STEPS.md) for section order.
+
+### 2. Triage — read the catalog, never re-derive
+
+Run `bun scripts/unit-route.mjs --triage <slug>` (or `<NN>` for numeric). PASTE
+its stdout block **verbatim** into the unit doc's Evidence section header under
+a `## Triaged steps` heading. This block is authoritative. The model never
+re-derives, reorders, or invents steps — it executes only what the catalog says.
+
+### 3. Execute triaged steps in order
+
+For each step the triage returned, follow its reference file. Execute **one step
+per turn-commit**:
+
+1. Read the step's reference — for example:
+   [research](references/RESEARCH.md), [design](references/DESIGN.md),
+   [plan](references/PLAN.md), [implement](references/IMPLEMENT.md),
+   [tests](references/TESTS.md), [evidence](references/EVIDENCE.md),
+   [review](references/REVIEW.md), [docs](references/DOCS.md),
+   [release](references/RELEASE.md) — only the ones the triage demands).
+2. Perform the step's checklist items.
+3. Write/update evidence in the unit doc.
+4. Update the Progress log with a dated entry.
+5. Commit with a conventional commit message.
+6. For implement steps, run the diff guard (step 4 below).
+
+### 4. Diff-size guard (after each implement step)
+
+Run `bun scripts/diff-guard.mjs --base <last-reviewed-ref> --unit <NN>`. Paste
+the output verbatim. On **BREACH**: stop, re-triage the unit, or record an
+exception. **Anti-gaming: NEVER shrink a diff by deleting comments, blank lines,
+docs or tests.** If the unit cannot fit the budget, record the exception and stop.
+
+### 5. Update evidence and progress
+
+Before every commit:
+
+- **Evidence rows**: One row per AC satisfied — `| AC | command | exit/digest |
+  output (≤2 lines) | verified-by |`
+- **Progress log**: `YYYY-MM-DD HH:MM — <what was done> → <commit sha> — next:
+  <what is next>`
+
+### 6. Close the unit
+
+When all triaged steps are done, run the review pack axis summary, update the
+unit doc's status, and print the closing block.
+
+## Guardrails
+
+**Allowed:**
+- Only the triaged steps listed by the catalog
+- Changes scoped to the acceptance criteria
+- Documentation updates in docs/ and template/
+- Conventional commit messages per the project's Workflow conventions
+
+**Forbidden:**
+- Never expand scope beyond what Non-goals define — findings discovered during
+  implementation never widen the unit
+- Never invent an acceptance criterion — ask the user with concrete options
+- Never skip a triaged step silently — every step the catalog demands must run
+- Findings never authorize scope growth — record them, route to their owner
+- Never commit red (test failure) — fix or replan, never silence tests
+- Never alter a triaged step's order
+
+## 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
+(`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.
+`init-workspace` seeds the unit doc template and catalog conventions into target
+projects.
+
+## Portability (agents other than Claude Code)
+
+- **No slash menu** — open this `SKILL.md` and follow it literally in a fresh
+  conversation. Where it says `run`, execute the shell command directly.
+- **No model tiers** — triage and review use the strongest model; execution
+  steps may use cheaper. Never review with a weaker model than the author.
+- **No `/loop`/subagents** — re-invoke manually and follow the closing `→ Next:`
+  block at each step boundary.
+
+## Done when
+
+- Every triaged step is executed and committed.
+- The unit doc's Evidence rows, Progress log, and References section are current.
+- The diff guard passed for all implement steps.
+- The review step is complete (or skipped per catalog).
+- **The closing `→ Next:` block is printed.**
+
+## Closing recommendation
+
+```
+→ Next: /unit-lane <NN-slug> — continue to the next triaged step
+  · all steps done → /review-change (review the accumulated diff)
+  · re-triage needed → /unit-lane <NN-slug> --retriage
+  · finished and merge-ready → /audit-pr (merge gate)
+```

package/skills/unit-lane/references/DESIGN.md

@@ -0,0 +1,35 @@
+# Design step
+
+## Purpose
+
+Induce acceptance criteria from user scenarios and close entity, role, and
+expectation boundaries — distilled from the full design skill's closure.
+
+## Inputs
+
+- The unit's objective, why, and user outcome from the SPEC
+- Research findings from the research step
+
+## Fixed output contract
+
+Fill the unit doc's **Acceptance criteria** section. Each AC must be:
+- Induced from a concrete user scenario ("I do X and observe Y")
+- Command-verified where possible (not "feel correct")
+- Numbered (AC1, AC2, …)
+
+## Checklist (pass only if)
+
+- [ ] Every AC is induced from a user scenario, not inferred from vague intent
+- [ ] Acceptance criteria are command-verified where possible
+- [ ] Entity closure: every entity mentioned has its role in the unit stated
+- [ ] Role closure: every actor/role that interacts with the unit is listed
+- [ ] Expectation sweep: user's accepted and rejected inputs are bounded
+- [ ] Vague items → ask the user with concrete options, never invent
+
+## Forbidden
+
+- Do not build a separate DESIGN.md — one SPEC, all in the unit doc
+- Do not invent product scope the user did not confirm
+- Do not pre-fill engineering content (phases, tests, architecture)
+- Do not stamp "designed" with an incomplete closure row
+- An incomplete row silently un-does the skill's purpose