@jakkrichm/create-nexus-devflow 2.5.0 → 2.6.1

package/template/.agents/skills/grill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: grill
-description: "[devflow][B] Interactive Socratic alignment & domain modeling - stress-test plans, extract domain glossary, and record architecture decision records (ADRs) before delivery."
+description: "[devflow] Interactive Socratic alignment & domain modeling - stress-test plans, extract domain glossary, and record architecture decision records (ADRs) before delivery."
 argument-hint: "{topic, plan, or question}"
 ---
 

package/template/.agents/skills/idea/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: idea
-description: "[devflow][B] Quick idea capture and AI enrichment - analyze feasibility, value, key points, and record into devflow/ideas.md inbox."
+description: "[devflow] Quick idea capture and AI enrichment - analyze feasibility, value, key points, and record into devflow/ideas.md inbox."
 argument-hint: "\"<idea text or description>\""
 ---
 

package/template/.agents/skills/implement/SKILL.md

@@ -1,9 +1,10 @@
 ---
 name: implement
-description: "[devflow][F] Build the feature, fix, or rollback spec'd in devflow/context/current-feature.md, one small reviewable step at a time. Creates the matching branch, implements each step, shows the diff and explains it in plain English, tests, and iterates until it works. Type: Rollback specs use a guarded reverse patch that preserves Blueprint history. After each approved step it offers an optional commit checkpoint on the branch; the work-level commit, merge, and logging are /complete's job. Use when the user runs /implement, or asks to build, implement, or start the current feature, fix, or rollback once its spec is ready."
+description: "[devflow] Build the feature, fix, or rollback spec, one small reviewable step at a time with Strict TDD. Supports Multi-Run: given an optional ID or name (/implement 12, /implement 012), targets that spec from devflow/context/{xxx-slug}/. Checks out matching branch, runs pre-flight drift revalidation, executes TDD steps with diffs, and offers commit checkpoints. Use when running /implement, or starting work on a spec."
+argument-hint: "[{run-id, number, or name}]"
 ---
 
-# implement - build the current spec, one reviewed step at a time
+# implement - build the target spec, one reviewed step at a time
 
 Where this sits in the workflow:
 
@@ -12,7 +13,7 @@ Where this sits in the workflow:
                                         reviewed)        merge + log)
 
 `/feature`, `/fix`, or `/rollback` wrote the spec to
-`devflow/context/current-feature.md` and stopped.
+`devflow/context/{xxx-slug}/spec.md` (or `devflow/context/current-feature.md`) and stopped.
 This skill turns that spec into code, following the build loop in
 `devflow/context/ai-interaction.md`, without vibe coding: small steps, a visible diff plus
 a plain-English explanation for each, testing, and iteration until it works, all
@@ -20,9 +21,14 @@ behind your approval. It builds on a branch and offers an optional commit
 checkpoint after each step; the work-level commit, merging, and logging are
 `/complete`'s job.
 
+## Multi-Run Target Resolution
+
+- **Given an ID or name** (e.g. `/implement 12`, `/implement 012`, `/implement kanban`) -> locates the matching run folder `devflow/context/{xxx-slug}/`, checks out `feature/{xxx-slug}`, and loads only that run's `spec.md`.
+- **With no argument** (`/implement`) -> checks current git branch, or auto-picks if only 1 spec is active, or prompts the user if multiple specs are queued.
+
 ## Before you start
 
-Read `devflow/context/current-feature.md`. If it has no real spec (still the stub, or its
+Read the target spec from `devflow/context/{xxx-slug}/spec.md` (or `devflow/context/current-feature.md`). If it has no real spec (still the stub, or its
 status is already complete), stop and tell the user to run `/feature` (for a
 planned feature), `/fix` (for an ad-hoc bug or change), or `/rollback` (for a
 completed feature reversal) first. Pull the

package/template/.agents/skills/onboard/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: onboard
-description: "[devflow][B] Set up the Blueprint after overlaying it onto a freshly scaffolded or early project. Detects the stack, tunes project files and adapters, documents real commands and existing checks, points to the optional standalone CI setup, and tells the user what to fill in before /overview or $overview. Use when the user runs /onboard, invokes $onboard, just copied the Blueprint into a new project, or asks what to do after overlaying the Blueprint. For an existing app with meaningful shipped features, use adopt instead."
+description: "[devflow] Set up the Blueprint after overlaying it onto a freshly scaffolded or early project. Detects the stack, tunes project files and adapters, documents real commands and existing checks, points to the optional standalone CI setup, and tells the user what to fill in before /overview or $overview. Use when the user runs /onboard, invokes $onboard, just copied the Blueprint into a new project, or asks what to do after overlaying the Blueprint. For an existing app with meaningful shipped features, use adopt instead."
 ---
 
 # onboard - finish the Blueprint overlay setup

package/template/.agents/skills/overview/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: overview
-description: "[devflow][B] Distill user-owned planning docs into `devflow/context/project-overview.md` using a deterministic compiler. The overview is the living source of truth that agents read every session."
+description: "[devflow] Distill user-owned planning docs into `devflow/context/project-overview.md` using a deterministic compiler. The overview is the living source of truth that agents read every session."
 ---
 
 # overview - dynamic project overview compiler

package/template/.agents/skills/prototype/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: prototype
-description: "[devflow][B] Interactively prototype the look of a project. Asks about the desired look and feel and which pages to draft, proposes a plan, and only then writes throwaway static HTML/CSS mockups to prototypes/ that share one theme (a set of CSS theme variables). A plan-first, pre-build helper that sits outside the spec-driven feature loop, like scaffolding. Use when the user runs /prototype, names screens to mock up, or asks to prototype the layout, theme, or look and feel."
+description: "[devflow] Interactively prototype the look of a project. Asks about the desired look and feel and which pages to draft, proposes a plan, and only then writes throwaway static HTML/CSS mockups to prototypes/ that share one theme (a set of CSS theme variables). A plan-first, pre-build helper that sits outside the spec-driven feature loop, like scaffolding. Use when the user runs /prototype, names screens to mock up, or asks to prototype the layout, theme, or look and feel."
 ---
 
 # prototype - lock the look before you build

package/template/.agents/skills/release/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: release
-description: "[devflow][B] Prepare a Blueprint project for deployment to Render or Vercel. Reads the plans, project commands, app config, and current repo state; verifies build, start, output, env, health checks, and provider config; can create or update render.yaml or vercel.json when requested; and stops before any external deploy, service creation, remote env change, push, publish, or destructive action unless the user explicitly approves. Use when the user runs /release, invokes $release, asks for Render setup, Vercel setup, deploy readiness, deployment config, render.yaml, or vercel.json."
+description: "[devflow] Prepare a Blueprint project for deployment to Render or Vercel. Reads the plans, project commands, app config, and current repo state; verifies build, start, output, env, health checks, and provider config; can create or update render.yaml or vercel.json when requested; and stops before any external deploy, service creation, remote env change, push, publish, or destructive action unless the user explicitly approves. Use when the user runs /release, invokes $release, asks for Render setup, Vercel setup, deploy readiness, deployment config, render.yaml, or vercel.json."
 ---
 
 # release - deployment readiness for Render and Vercel

package/template/.agents/skills/report-html/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: report-html
-description: "[devflow][B] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from current-feature.md or 60-report.md on demand."
+description: "[devflow] Standalone HTML Report Generator - render an interactive standalone HTML dashboard from current-feature.md or 60-report.md on demand."
 argument-hint: "{running-id or workspace path}"
 ---
 

package/template/.agents/skills/rollback/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rollback
-description: "[devflow][B] Plan a safe reversal of a completed Blueprint feature using its archived spec and squashed git commit. Finds the exact feature commit, reviews later commits for dependency risk, writes a Type: Rollback spec to devflow/context/current-feature.md, and stops for review before /implement applies any code change. Use when the user runs /rollback, asks to remove or undo a completed feature, or wants to return the app to its pre-feature behavior without erasing Blueprint history."
+description: "[devflow] Plan a safe reversal of a completed Blueprint feature using its archived spec and squashed git commit. Finds the exact feature commit, reviews later commits for dependency risk, writes a Type: Rollback spec to devflow/context/current-feature.md, and stops for review before /implement applies any code change. Use when the user runs /rollback, asks to remove or undo a completed feature, or wants to return the app to its pre-feature behavior without erasing Blueprint history."
 ---
 
 # rollback - safely reverse a completed feature

package/template/.agents/skills/status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: status
-description: "[devflow][B] Show where the project stands: build-plan progress, the current feature's checked and unchecked steps, git state, drift warnings, and the exact next action. Read-only. Use when the user runs /status, asks where things stand, what's next, what's in progress, or is picking work back up after a break or a context clear."
+description: "[devflow] Show where the project stands: build-plan progress, the current feature's checked and unchecked steps, git state, drift warnings, and the exact next action. Read-only. Use when the user runs /status, asks where things stand, what's next, what's in progress, or is picking work back up after a break or a context clear."
 ---
 
 # status - where the project stands right now

package/template/.agents/skills/test/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test
-description: "[devflow][B] Test execution, missing test generation, and coverage analysis across unit, integration, and smoke test suites."
+description: "[devflow] Test execution, missing test generation, and coverage analysis across unit, integration, and smoke test suites."
 ---
 
 # Test-Driven Development, Generation & Execution

package/template/.agents/skills/tests/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tests
-description: "[devflow][B] Add or normalize unit testing for a Blueprint project. Detects the stack, reuses an existing test runner when present, or installs the stack-native unit test runner when missing, then adds one small example test, updates AGENTS.md commands, runs build and tests, and reports the diff. Use when the user runs /tests, invokes $tests, asks to add unit tests, set up unit testing, configure tests, or make tests part of the Blueprint workflow."
+description: "[devflow] Add or normalize unit testing for a Blueprint project. Detects the stack, reuses an existing test runner when present, or installs the stack-native unit test runner when missing, then adds one small example test, updates AGENTS.md commands, runs build and tests, and reports the diff. Use when the user runs /tests, invokes $tests, asks to add unit tests, set up unit testing, configure tests, or make tests part of the Blueprint workflow."
 ---
 
 # tests - add unit testing to the project

package/template/.agents/skills/try/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: try
-description: "[devflow][B] Generate a human manual try guide for the current or most recently completed Blueprint feature, fix, or rollback. Reads the spec, project commands, and available app context, then tells the user exactly what to start, where to go, what to click or run, what to expect, and what would count as wrong. Read-only. Use when the user runs /try, invokes $try, asks how to test manually, asks where to click, asks how to see the change, or wants a manual review path after /implement, /autopilot, /check, or /complete."
+description: "[devflow] Generate a human manual try guide for the current or most recently completed Blueprint feature, fix, or rollback. Reads the spec, project commands, and available app context, then tells the user exactly what to start, where to go, what to click or run, what to expect, and what would count as wrong. Read-only. Use when the user runs /try, invokes $try, asks how to test manually, asks where to click, asks how to see the change, or wants a manual review path after /implement, /autopilot, /check, or /complete."
 ---
 
 # try - manual review guide

package/template/.claude/skills/adopt/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: adopt
-description: "[devflow][B] Bring the blueprint into an existing (brownfield) codebase. Surveys the real repo, interviews for intent, generates the owned plans and coding standards, documents existing verification and CI, asks whether DevFlow workflow files should be committed or kept local-only, and points to the optional standalone CI setup. Use when the user runs /adopt, is overlaying the blueprint onto an app that already has meaningful code, or asks to adopt or bootstrap the workflow into an existing project. For freshly scaffolded or early projects, use onboard instead."
+description: "[devflow] Bring the blueprint into an existing (brownfield) codebase. Surveys the real repo, interviews for intent, generates the owned plans and coding standards, documents existing verification and CI, asks whether DevFlow workflow files should be committed or kept local-only, and points to the optional standalone CI setup. Use when the user runs /adopt, is overlaying the blueprint onto an app that already has meaningful code, or asks to adopt or bootstrap the workflow into an existing project. For freshly scaffolded or early projects, use onboard instead."
 ---
 
 # adopt - bootstrap the blueprint from an existing codebase

package/template/.claude/skills/audit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: audit
-description: "[devflow][B] Read-only code audit for a Blueprint project, except for the findings ledger it maintains at devflow/context/findings.md. Reviews the active feature, changed files, a selected path, or the full project through all concerns or a focused quality, security, performance, or tests lens. Use when the user runs /audit, invokes $audit, asks for a code or quality audit, security review, performance review, test quality review, dead-code or duplication check, vibe-coded project cleanup, or standards review."
+description: "[devflow] Read-only code audit for a Blueprint project, except for the findings ledger it maintains at devflow/context/findings.md. Reviews the active feature, changed files, a selected path, or the full project through all concerns or a focused quality, security, performance, or tests lens. Use when the user runs /audit, invokes $audit, asks for a code or quality audit, security review, performance review, test quality review, dead-code or duplication check, vibe-coded project cleanup, or standards review."
 ---
 
 # audit - review code quality against the project standards

package/template/.claude/skills/autopilot/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: autopilot
-description: "[devflow][B] Optional explicit Blueprint mode for one bounded spec/build/check/audit pass. It can pick or resume the current feature, write the spec when needed, create or reuse the branch, implement small steps, run build/tests/checks, create checkpoint commits after passing steps, audit changed code, repair confirmed high-severity findings, and stop with a review packet. It never completes, merges, pushes, deploys, publishes, sends, or performs destructive actions without explicit approval. Use only when the user explicitly runs /autopilot, invokes $autopilot, or directly asks for Autopilot."
+description: "[devflow] Optional explicit Blueprint mode for one bounded spec/build/check/audit pass. It can pick or resume the current feature, write the spec when needed, create or reuse the branch, implement small steps, run build/tests/checks, create checkpoint commits after passing steps, audit changed code, repair confirmed high-severity findings, and stop with a review packet. It never completes, merges, pushes, deploys, publishes, sends, or performs destructive actions without explicit approval. Use only when the user explicitly runs /autopilot, invokes $autopilot, or directly asks for Autopilot."
 ---
 
 # autopilot - optional Blueprint loop

package/template/.claude/skills/brainstorm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: brainstorm
-description: "[devflow][B] Companion skill for structured divergent and convergent ideation, generating 2-3 viable options with trade-off analysis before committing to delivery."
+description: "[devflow] Companion skill for structured divergent and convergent ideation, generating 2-3 viable options with trade-off analysis before committing to delivery."
 argument-hint: "{topic, feature, or discovery-id}"
 ---
 

package/template/.claude/skills/brief/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: brief
-description: "[devflow][B] Read-only briefing on an upcoming build-plan feature before you spec it. With no argument, briefs the next unchecked item; given a number or name, briefs that one. Reads build-plan.md and project-overview.md and explains what the feature is, what it depends on, what it will touch, how big it is, and whether it will split - without writing anything. Use when the user runs /brief, asks what the next feature involves, wants to understand or preview a feature before /feature, or is deciding what to build or reorder next."
+description: "[devflow] Read-only briefing on an upcoming build-plan feature before you spec it. With no argument, briefs the next unchecked item; given a number or name, briefs that one. Reads build-plan.md and project-overview.md and explains what the feature is, what it depends on, what it will touch, how big it is, and whether it will split - without writing anything. Use when the user runs /brief, asks what the next feature involves, wants to understand or preview a feature before /feature, or is deciding what to build or reorder next."
 ---
 
 # brief - understand a feature before you spec it

package/template/.claude/skills/check/SKILL.md

@@ -1,108 +1,113 @@
 ---
 name: check
-description: "[devflow][F] Prove the current work actually does what its spec says by running the real app and observing behavior against the \"done when\" criteria in current-feature.md. Drives the app (browser, CLI, or server), captures evidence (screenshots, output, console/network errors), and reports pass/fail per criterion. Does not edit source or commit - it observes; fixing stays /implement's job. Use when the user runs /check, asks to confirm a step or feature works, wants proof before /complete, or wants to check a change in the running app rather than just the build. (Supersedes the built-in /verify with a spec-aware version inside blueprint projects.)"
+description: "[devflow] Prove the current work actually does what its spec says and adheres to architectural standards through a Dual-Axis Independent Review. Supports Multi-Run: given an optional ID or name (/check 12), targets that spec and records proof to devflow/context/{xxx-slug}/findings.md. Drives the app, captures empirical evidence, checks Fowler smells, and reports pass/fail. Use when running /check, confirming work, or validating before /complete."
+argument-hint: "[{run-id, number, or name}]"
 ---
 
-# check - prove it works against the spec, with evidence
+# check - Dual-Axis Independent Verification Engine
 
 Where this sits in the workflow:
 
     /implement  ->  [check]  ->  /complete
-    (built a       (run the app,    (only once the
-     step or        prove each       done-whens are
-     the feature)   done-when)       proven)
+    (built a       (dual-axis       (only once both
+     step or        review with      axes pass with
+     the feature)   empirical proof) evidence)
 
-`/implement` builds and does a quick build-plus-screenshot check inline. `/check`
-is the deeper, repeatable gate for when a "done when" needs the *real running app*,
-not just a green build: a click that triggers a download, a route that returns a
-file, a flow across screens. Run it on a single step whose done-when is
-behavioral, or on the whole feature as the acceptance check before `/complete`.
+`/implement` builds and does a quick build-plus-screenshot check inline. `/check` is the rigorous, repeatable gate for when a feature or step needs **empirical proof** on the running app and **two-axis code review** before merging.
 
-The point is evidence. A passing build proves the code compiles; `/check` proves
-the thing the spec promised actually happens. It changes no source and commits
-nothing - it runs the app and reports what it saw.
+It changes no source and commits nothing — it executes, inspects, and reports observed facts.
+
+---
 
 ## Input
 
-Optional: a specific thing to check (a step, a flow, a URL). With no argument,
-verify the whole current feature against every "done when" in
-`devflow/context/current-feature.md`.
+- **Given an ID or name** (e.g. `/check 12`, `/check 012`) -> targets `devflow/context/{xxx-slug}/` and records audit ledger to `{xxx-slug}/findings.md`.
+- **With no argument** (`/check`) -> verifies the active run matching current git branch or single active spec.
 
-## Step 1 - build the checklist
+---
 
-Read `devflow/context/current-feature.md`. Pull the observable "done when"
-criteria from the build steps (and any acceptance notes in the Testing section).
-Turn them into a concrete checklist of claims to prove - each one a specific,
-observable behavior, not "it works". If the user named one thing, scope to that.
+## Step 1 - Build the Dual-Axis Review Matrix
 
-If there's no current feature spec, ask what to verify rather than guessing.
+Read the target spec from `devflow/context/{xxx-slug}/spec.md` (or `devflow/context/current-feature.md`) and `devflow/context/coding-standards.md`. Prepare the inspection criteria across two independent axes:
 
-## Step 2 - get the app running
+1. **Axis 1 (Standards & Architecture Criteria)**:
+   - Coding conventions in `coding-standards.md`
+   - Deep Modules discipline (Small interface, deep implementation, clean seams, no leaky abstractions)
+   - Baseline 12 Fowler Code Smells (Primitive obsession, Feature envy, Shotgun surgery, Speculative generality, etc.)
+   - Multi-lane technical gates (Typecheck, test suites, zero secrets, zero P0/P1 findings)
+2. **Axis 2 (Spec Fidelity & Behavioral Observables)**:
+   - Line-by-line Acceptance Criteria (ACs) and "Done When" observables from `current-feature.md`
+   - Scope Creep detection (Unrequested behavior in the diff)
+   - Missing Requirements detection (Unimplemented edge cases)
 
-Use the project's real commands (see Commands in `AGENTS.md`). Match the project
-type:
+---
 
-- **Web app** - start (or reuse) the dev/preview server, then drive a real browser
-  to the relevant routes. Prefer reusing an already-running server over starting a
-  duplicate. If Playwright is already installed or declared in `AGENTS.md`, prefer
-  it for browser driving, screenshots, console errors, and failed request checks.
-  If it is not installed, do not add it from `/check`; use another real-browser
-  evidence path and report what you used.
-- **CLI** - run the actual command(s) with representative inputs.
-- **Server/API** - start it and hit the endpoints.
-- **Library** - exercise the public API through an example or the test command.
+## Step 2 - Get the App Running & Exercise Live Proof
 
-If a `test` command is declared in `AGENTS.md`, you may run it as *one* input, but
-`/check` is broader than unit tests: it checks real behavior, which is exactly the
-evidence UI and integration steps ride on instead of unit tests.
+Use the project's real commands (from `AGENTS.md`):
 
-## Step 3 - exercise each claim
+- **Web app**: Start (or reuse) the local dev server. Drive a real browser to relevant routes. Prefer Playwright when installed for screenshots, network errors, and console assertions.
+- **CLI**: Execute commands with representative input fixtures, asserting exit codes and output snapshots.
+- **Server / API**: Hit endpoints with real payloads and assert on HTTP response status and bodies.
+- **Library**: Exercise public interfaces through integration tests or sample scripts.
 
-Drive the app to each checklist item and capture evidence as you go:
+> [!IMPORTANT]
+> **Evidence or it didn't happen**: Every verdict must be backed by empirical evidence (screenshot, command output, status code, response time). Never assume a pass from reading source code alone.
 
-- Navigate and interact for real (click, type, submit, download) - don't assert
-  from the code what the running app would do.
-- Capture **screenshots** for visual/UI claims, **output** for CLI/API claims.
-- Watch for **console errors and failed network requests**; a clean-looking screen
-  with errors in the console is not a pass.
+---
 
-## Step 4 - report (Two-Stage Review Pattern)
+## Step 3 - Dual-Axis Independent Report
 
-Format the verification report into two explicit review stages:
+Format the report into two distinct, un-merged review axes:
 
-### Stage 1: Spec Fidelity & Acceptance Gate
-Give a line-by-line verdict for each Acceptance Criterion and "done when" item:
+```markdown
+# 🔍 Verification Report: [Feature Name]
 
-    [pass] AC-1: Download PDF saves certificate-<slug>.pdf - file downloaded, opened to cert
-    [pass] AC-2: Both buttons show a loading state - screenshot: loading-state.png
-    [fail] AC-3: PDF border missing - printBackground not set; screenshot: pdf-no-border.png
-    [skip] AC-4: Vercel deploy smoke test - can't verify locally (pending staging)
+## ⚖️ Axis 1: Standards, Architecture & Quality Gate
 
-### Stage 2: Code Quality, Security & Architecture Gate
-Report the multi-lane technical verification results:
-- **Type & Syntax**: `tsc --noEmit` (0 errors)
-- **Automated Tests**: Unit & integration tests (100% pass)
-- **Security & Hygiene**: Zero secrets, sanitized inputs
-- **Findings Ledger**: 0 blockers (P0/P1) in `devflow/context/findings.md`
+- **Technical Lanes**:
+  - [pass] Type Safety: `tsc --noEmit` (0 errors)
+  - [pass] Automated Tests: `npm test` (All tests green)
+  - [pass] Security & Hygiene: Zero secrets, sanitized inputs
+  - [pass] Findings Ledger: 0 blocking P0/P1 in `devflow/context/findings.md`
+- **Deep Modules & Architecture**:
+  - [pass] Seam Integrity: Public interfaces remain small, implementation details hidden.
+  - [pass] The Deletion Test: Complexity is concentrated inside the module, not scattered across callers.
+- **Code Smells Assessment**:
+  - [clean] 12 Fowler Code Smells evaluated across git diff: No critical smells detected.
 
-### Final Verdict & Route
-- **All Passed**: State that the feature is verified and ready for `/complete`.
-- **Any Failure**: Hand back to `/implement` with exact failure evidence and reproduction steps. Never fix issues inside `/check`.
-- **Unverifiable**: Clearly state reasons and residual risk. Never fabricate a pass.
+## 🎯 Axis 2: Spec Fidelity & Behavioral Acceptance Gate
 
-## Rules
+Line-by-line verification against `current-feature.md`:
+- [pass] **AC-1 (<title>)**: <Observed empirical evidence / screenshot path>
+- [pass] **AC-2 (<title>)**: <Observed empirical evidence / terminal output>
+- [fail] **AC-3 (<title>)**: <Exact observed failure with reproduction command>
+- [clean] **Scope Creep Check**: No unrequested features or unnecessary abstractions introduced.
+- [clean] **Completeness Check**: 100% of spec requirements addressed.
+
+---
+
+## 🚦 Final Routing & Verdict
 
-- **Observe, don't change.** `/check` runs the app and reports. It never edits
-  source, never commits, never merges. Fixing is `/implement`'s job.
-- **Evidence or it didn't happen.** Every `pass` is backed by something observed -
-  a screenshot, output, a response. No assumed passes from reading the code.
-- **Honest over green.** "Couldn't verify" and "failed" are valid, useful results.
-  Faking a pass defeats the entire gate.
-- **Check the spec, not vibes.** Verify against the done-whens in
-  `current-feature.md`, so "works" means what the spec said it would do.
+- **ALL PASSED**: Both axes green. Ready for `/complete`.
+- **ANY FAILURE**: Hand back to `/implement` with exact failure evidence and reproduction steps.
+- **UNVERIFIABLE**: Clearly document the gap and residual risk. Never fabricate a pass.
+```
 
-## Formatting
+---
+
+## Why Two Independent Axes?
+
+A code change can pass one axis and fail the other:
+- **Standards Pass, Spec Fail**: Code is beautifully architected and tested, but implements the wrong business behavior.
+- **Spec Pass, Standards Fail**: Feature works end-to-end, but violates encapsulation, introduces shallow modules, or leaks secrets.
+
+Reporting both axes side-by-side stops elegance from masking functional bugs, and stops functional completeness from excusing architectural rot.
+
+---
+
+## Rules
 
-Format the output to match the project's conventions in
-`devflow/context/ai-interaction.md`: concise, scannable markdown, with lists for
-enumerations and tables for matrices rather than dense paragraphs.
+- **Observe, don't change**: `/check` runs the app and reports. It never edits source or commits. Fixing is `/implement`'s job.
+- **Honest over green**: "Failed" and "Could not verify" are valid, valuable outputs. Faking a pass destroys the gate.
+- **Check the spec, not vibes**: Verify against documented ACs, not subjective feelings.

package/template/.claude/skills/ci/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ci
-description: "[devflow][B] Set up or normalize automatic GitHub checks for a Blueprint project around one documented Verify command. Detects the real stack, package manager, existing checks, default branch, and workflows; preserves existing CI; combines only configured typecheck, test, and build commands; runs the command locally; and stops before push or remote ruleset changes. Use when the user runs /ci, invokes $ci, asks to add CI, set up GitHub Actions, add pull-request checks, or create automatic GitHub checks."
+description: "[devflow] Set up or normalize automatic GitHub checks for a Blueprint project around one documented Verify command. Detects the real stack, package manager, existing checks, default branch, and workflows; preserves existing CI; combines only configured typecheck, test, and build commands; runs the command locally; and stops before push or remote ruleset changes. Use when the user runs /ci, invokes $ci, asks to add CI, set up GitHub Actions, add pull-request checks, or create automatic GitHub checks."
 ---
 
 # ci - set up automatic GitHub checks

package/template/.claude/skills/complete/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: complete
-description: "[devflow][F] Wrap up a finished feature, fix, or rollback. Runs a final safety pass, archives its spec to devflow/history/features/, devflow/history/fixes/, or devflow/history/rollbacks/, updates the build plan for features and rollbacks, resets devflow/context/current-feature.md to its stub, and makes the work commit. Enforces a mandatory user gate: asks whether to squash-merge to main/master OR pull latest main/master into the feature/dev branch and push to remote for Merge Request (MR / PR) creation. Never merges into main/master without explicit user instruction."
+description: "[devflow] Wrap up a finished feature, fix, or rollback. Supports Multi-Run: given an optional ID (/complete 12), archives that run from devflow/context/{xxx-slug}/ to devflow/history/, cleans up the run workspace, updates build-plan and HISTORY.md, and makes the work commit. Enforces mandatory user gate (Squash-merge vs MR/PR)."
+argument-hint: "[{run-id, number, or name}]"
 ---
 
 # complete - log the finished work, make the work commit, and deliver
@@ -12,13 +13,18 @@ Where this sits in the workflow:
 
 `/implement` built the feature, fix, or rollback on its branch, with optional per-step commit
 checkpoints. This skill closes it out: it logs the work, makes the single
-work-level commit, and guides the delivery through a **Mandatory User Delivery Gate**. Run it only when the work is done,
+work-level commit, archives from `devflow/context/{xxx-slug}/`, cleans up the active run workspace, and guides the delivery through a **Mandatory User Delivery Gate**. Run it only when the work is done,
 reviewed, and the documented `Verify` command, or the fallback build and tests,
 passes.
 
+## Multi-Run Target Resolution
+
+- **Given an ID or name** (e.g. `/complete 12`, `/complete 058`) -> targets `devflow/context/{xxx-slug}/` for archiving and cleanup.
+- **With no argument** (`/complete`) -> targets the run matching the active branch or single active spec.
+
 ## Before you start
 
-Confirm the work is actually finished: `devflow/context/current-feature.md`
+Confirm the target work is actually finished: `devflow/context/{xxx-slug}/spec.md` (or `current-feature.md`)
 holds a real spec, its steps are built on a branch, and `Verify`, or the fallback
 build and tests, passes. If any of the
 spec's done-whens are behavioral, `/check` should have proven them against the

package/template/.claude/skills/convert-any-to-md/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: convert-any-to-md
-description: "[devflow][B] Converts any document (.xlsx, .pdf, .docx, .txt, .csv, .log, .json, .yaml, etc.) or mixed folders into clean Markdown in devflow/reference. Use whenever documents need to be analyzed, summarized, searched, or extracted from."
+description: "[devflow] Converts any document (.xlsx, .pdf, .docx, .txt, .csv, .log, .json, .yaml, etc.) or mixed folders into clean Markdown in devflow/reference. Use whenever documents need to be analyzed, summarized, searched, or extracted from."
 ---
 
 # Convert Any Document to Markdown