@curdx/flow 3.0.0 → 3.1.0

package/skills/start/SKILL.md

@@ -1,84 +0,0 @@
----
-name: start
-description: Create, resume, list, or switch the active feature spec.
-when_to_use: Use when the user wants to create a spec, switch active work, resume a prior spec, list specs, or set the workflow mode for a feature.
-argument-hint: "[<spec-name>] [\"<one-line goal>\"] [--resume] [--list] [--mode=<fast|standard|enterprise>]"
-disable-model-invocation: true
-allowed-tools: [Read, Write, Bash, AskUserQuestion, Agent]
----
-
-# Start or Resume a Feature Spec
-
-Entry point for every feature. Keep this skill focused on argument parsing,
-branch selection, state seeding, and next-step routing. Detailed branch behavior
-and workflow handoff rules live in:
-
-- `references/preflight.md`
-- `references/branch-routing.md`
-- `references/state-seeding.md`
-- `references/mode-semantics.md`
-- `references/workflow-handoff.md`
-- `references/reporting.md`
-
-## Invocation Patterns
-
-| Pattern | Behavior |
-|---------|----------|
-| `/curdx-flow:start my-feature "Add JWT auth to REST API"` | Create a fresh spec named `my-feature`, set it active, seed draft requirements. |
-| `/curdx-flow:start my-feature` (name exists) | Switch active spec to `my-feature` (same as v1 `/switch`). |
-| `/curdx-flow:start --resume` | Resume the last active spec from `.flow/.active-spec`. |
-| `/curdx-flow:start --list` | List all specs with their phase and last-updated time, prompt to pick. |
-| `/curdx-flow:start` (no args) | Interactive: ask the user whether to create new, resume recent, or list all. |
-| Add `--mode=<fast\|standard\|enterprise>` | Set the execution mode for this spec (stored in `.state.json`). |
-
-## Preflight
-
-Use `references/preflight.md` for the project-level guard.
-
-## Flag Parsing
-
-Do not shell-split `$ARGUMENTS`. Parse flags and positional arguments using the
-rules in `references/branch-routing.md`.
-
-Hard constraints:
-
-- Flags allowed: `--resume`, `--list`, `--mode=<fast|standard|enterprise>`
-- First positional token -> `SPEC_NAME`
-- Remaining trimmed content -> `GOAL`
-- `SPEC_NAME` must be kebab-case per `schemas/spec-state.schema.json`
-- Invalid mode -> warn and fall back to `standard`
-
-## Branch Selection
-
-Use `references/branch-routing.md` for the full branch contract:
-
-- Branch A: `--list`
-- Branch B: `--resume`
-- Branch C: existing `SPEC_NAME`
-- Branch D: new `SPEC_NAME`
-- Branch E: no args / no flags
-
-If a new spec must be created, seed `.state.json`, `.flow/.active-spec`, and
-`.progress.md` using `references/state-seeding.md`.
-
-## Mode Semantics
-
-Use `references/mode-semantics.md` for the workflow defaults implied by
-`mode`.
-
-## Post-Create and Resume Handoff
-
-The next-command routing rules are centralized in
-`references/workflow-handoff.md`.
-
-User-visible create/switch/resume summaries live in `references/reporting.md`.
-For a newly created spec, the immediate handoff remains:
-
-```text
-Next: /curdx-flow:spec
-```
-
-## References
-
-- State schema: `@${CLAUDE_PLUGIN_ROOT}/schemas/spec-state.schema.json`
-- Mode semantics: `@${CLAUDE_PLUGIN_ROOT}/knowledge/execution-strategies.md`

package/skills/start/references/branch-routing.md

@@ -1,51 +0,0 @@
-# Branch Routing — Start Skill Control Flow
-
-## Argument Parsing Rules
-
-Do not shell-split `$ARGUMENTS`.
-
-1. Detect and remove these flags from the raw string:
-   - `--resume`
-   - `--list`
-   - `--mode=<fast|standard|enterprise>`
-2. After flags are removed:
-   - first whitespace-delimited token -> `SPEC_NAME`
-   - remaining trimmed text -> `GOAL`
-   - strip one outer layer of matching single or double quotes from `GOAL`
-3. Reject unknown flags instead of ignoring them.
-
-## Branches
-
-### Branch A — `--list`
-
-- enumerate `.flow/specs/*`
-- read each `.state.json`
-- show phase + updated timestamp
-- use `AskUserQuestion` to choose
-- set `.flow/.active-spec`
-
-### Branch B — `--resume`
-
-- read `.flow/.active-spec`
-- if stale or missing, fall back to Branch A
-- report current phase and route using `references/workflow-handoff.md`
-
-### Branch C — Existing `SPEC_NAME`
-
-- switch `.flow/.active-spec` to that spec
-- confirm if the user likely intended to switch rather than overwrite
-- report current phase
-
-### Branch D — New `SPEC_NAME`
-
-- gather missing `GOAL` if necessary
-- create state and progress files using `references/state-seeding.md`
-- set `.flow/.active-spec`
-
-### Branch E — No args / no flags
-
-Ask the user to choose:
-
-- create a new spec
-- resume the last active spec
-- list all specs

package/skills/start/references/mode-semantics.md

@@ -1,12 +0,0 @@
-# Start Mode Semantics — What Each Mode Implies
-
-The `mode` field in `.state.json` drives later workflow defaults:
-
-| Mode | `/curdx-flow:spec` default | `/curdx-flow:implement` default | Gates applied |
-|------|---------------------------|--------------------------------|---------------|
-| `fast` | skipped (use `/curdx-flow:fast` instead) | linear strategy | karpathy + verification |
-| `standard` | full 4 phases | auto strategy | + tdd + coverage-audit |
-| `enterprise` | full 4 phases + `--review=all` | auto strategy + stricter gates | + adversarial + edge-case + security + devex |
-
-If an invalid mode is provided during argument parsing, warn and fall back to
-`standard`.

package/skills/start/references/preflight.md

@@ -1,13 +0,0 @@
-# Start Preflight — Project Must Be Initialized
-
-Before parsing arguments or touching spec state:
-
-```bash
-[ ! -d ".flow" ] && {
-  echo "✗ Not a CurdX-Flow project. Run /curdx-flow:init first.";
-  exit 1;
-}
-```
-
-`/curdx-flow:start` is the first mutable workflow entrypoint after init. If the
-project scaffold is missing, stop immediately instead of attempting recovery.

package/skills/start/references/reporting.md

@@ -1,20 +0,0 @@
-# Start Reporting — User-Facing Summaries
-
-For a newly created spec, report:
-
-```text
-✓ Spec ready: <name>
-  Goal:  <goal>
-  Mode:  <mode>
-  Path:  .flow/specs/<name>/
-
-Next: /curdx-flow:spec
-```
-
-For resume and switch flows, keep the message short:
-
-- identify the active spec
-- state the current phase when known
-- route using `references/workflow-handoff.md`
-
-Do not restate the full workflow. Point to the immediate next command only.

package/skills/start/references/state-seeding.md

@@ -1,44 +0,0 @@
-# State Seeding — New Spec Bootstrap
-
-When creating a fresh spec, use `Write` for all files so Claude checkpoints can
-rewind the bootstrap cleanly.
-
-## `.state.json`
-
-Required shape:
-
-```json
-{
-  "version": "1.0",
-  "spec_name": "$SPEC_NAME",
-  "goal": "$GOAL",
-  "mode": "$FLAG_MODE",
-  "phase": "research",
-  "phase_status": {},
-  "strategy": "auto",
-  "execute_state": {},
-  "created": "YYYY-MM-DD",
-  "updated": "YYYY-MM-DDTHH:MM:SSZ"
-}
-```
-
-## `.progress.md`
-
-```markdown
-# Progress Log — $SPEC_NAME
-
-**Goal**: $GOAL
-**Mode**: $FLAG_MODE
-**Created**: YYYY-MM-DD
-
-## Decisions
-(populated during /curdx-flow:spec)
-
-## Learnings
-(populated during /curdx-flow:implement)
-```
-
-## Activation
-
-Write `.flow/.active-spec` last, after the spec directory and both artifacts
-exist.

package/skills/start/references/workflow-handoff.md

@@ -1,26 +0,0 @@
-# Workflow Handoff — What Comes Next
-
-`/curdx-flow:start` is the entrypoint, but it should route users to the right
-next command based on current phase.
-
-## New Spec
-
-After a fresh spec is created:
-
-```text
-Next: /curdx-flow:spec
-```
-
-## Resume / Switch Routing
-
-When resuming an existing spec:
-
-- `phase` before `tasks` completion -> suggest `/curdx-flow:spec`
-- `tasks` completed but execution not complete -> suggest `/curdx-flow:implement`
-- `execute` completed but verification missing or failed -> suggest `/curdx-flow:verify`
-- `verify` completed but review missing or failed -> suggest `/curdx-flow:review`
-- both verification and review completed -> report evidence-backed handoff is
-  ready for human PR/release work
-
-Do not invent non-existent ship commands. The workflow ends at human handoff
-with persisted evidence.

package/skills/status/SKILL.md

@@ -1,41 +0,0 @@
----
-name: status
-description: Show active spec health, progress, artifacts, and recovery hints.
-when_to_use: Use when the user asks what is active, which phase a spec is in, what artifacts exist, or how to recover from interrupted execution.
-argument-hint: "[--all]"
-disable-model-invocation: true
-allowed-tools: [Read, Bash, Glob]
----
-
-# CurdX-Flow Status
-
-Show a compact, read-only status summary for the current project. Keep this
-entrypoint focused on read-only inventory, health classification, and recovery
-hints. Detailed health and recovery rules live in:
-
-- `references/preflight.md`
-- `references/gather-contract.md`
-- `references/health-rules.md`
-- `references/recovery-hints.md`
-- `references/output-contract.md`
-
-## Preconditions
-
-Use `references/preflight.md` for the project-level guard.
-
-## Gather
-
-Use `references/gather-contract.md` for the full read-only inventory contract.
-
-## Output Format
-
-Use `references/output-contract.md` for the compact markdown report shape.
-
-Use `references/health-rules.md` to compute `Health`, and
-`references/recovery-hints.md` to compute the single best next action.
-
-## Strictness
-
-- Read-only. Do not modify files.
-- Do not claim a spec is complete from `.state.json` alone; compare `tasks.md`
-  checkboxes.

package/skills/status/references/gather-contract.md

@@ -1,30 +0,0 @@
-# Status Gather Contract — What to Read
-
-Gather read-only state in this order:
-
-1. Read `.flow/.active-spec` if present.
-2. List `.flow/specs/*/` directories.
-3. For each spec, check artifacts:
-   - `research.md`
-   - `requirements.md`
-   - `design.md`
-   - `tasks.md`
-   - `verification-report.md`
-   - `review-report.md`
-4. If `.state.json` exists, read:
-   - `phase`
-   - `strategy`
-   - `phase_status`
-   - `execute_state.task_index`
-   - `execute_state.total_tasks`
-   - `execute_state.failed_attempts`
-   - `execute_state.global_iteration`
-   - `execute_state.native_sync_enabled`
-   - `execute_state.native_sync_failure_count`
-   - `execute_state.native_task_map` size
-5. If `tasks.md` exists, count:
-   - completed tasks: lines matching `- [x] **`
-   - open tasks: lines matching `- [ ] **`
-
-Do not mutate files while gathering. `status` is an observer, not a repair
-workflow.

package/skills/status/references/health-rules.md

@@ -1,27 +0,0 @@
-# Status Health Rules — Canonical Evaluation
-
-## `OK`
-
-Use `OK` only when:
-
-- state and tasks agree
-- failed attempts are zero
-- the current phase's expected artifact exists
-
-## `NEEDS_ATTENTION`
-
-Use `NEEDS_ATTENTION` when any of these is true:
-
-- `.state.json` says execute complete but `tasks.md` still has open tasks
-- `failed_attempts > 0`
-- `.flow/.active-spec` points to a missing directory
-- the current phase's expected artifact is missing or obviously truncated
-
-## Artifact Expectations
-
-- `research` -> `research.md`
-- `requirements` -> `requirements.md`
-- `design` -> `design.md`
-- `tasks` / `execute` -> `tasks.md`
-- `verify` -> `verification-report.md`
-- `review` -> `review-report.md`

package/skills/status/references/output-contract.md

@@ -1,25 +0,0 @@
-# Status Output Contract — Compact Read-Only Summary
-
-Render:
-
-```markdown
-# CurDX-Flow Status
-
-Project: <cwd>
-Active spec: <name | none>
-
-## Specs
-
-### <spec-name> [ACTIVE]
-Phase: <phase | unknown>
-Strategy: <strategy | auto>
-Tasks: <done>/<total from tasks.md> checked, state cursor <task_index>/<total_tasks>
-Failures: <failed_attempts>, rounds: <global_iteration>
-Native sync: <on|off>, mapped tasks: <count>, sync failures: <native_sync_failure_count>
-Artifacts: [x] research [x] requirements [x] design [x] tasks [ ] verify [ ] review
-Health: OK | NEEDS_ATTENTION
-Recovery: <one concrete next command>
-```
-
-Keep it compact and operational. Show one best recovery command, not a list of
-possible next steps.

package/skills/status/references/preflight.md

@@ -1,10 +0,0 @@
-# Status Preflight — Project Must Exist
-
-Before reading any status signals:
-
-```bash
-[ ! -d ".flow" ] && { echo "✗ Not a CurdX-Flow project. Run /curdx-flow:init first."; exit 1; }
-```
-
-`status` is strictly read-only. If `.flow/` does not exist, stop immediately
-and route to `/curdx-flow:init`.

package/skills/status/references/recovery-hints.md

@@ -1,18 +0,0 @@
-# Status Recovery Hints — Single Best Next Command
-
-Choose one concrete recovery command, not a menu.
-
-## Priority Rules
-
-- No `.flow/` -> `/curdx-flow:init`
-- No active spec -> `/curdx-flow:start <name> "<goal>"`
-- Missing or stale spec artifact before tasks completion -> `/curdx-flow:spec`
-- Tasks complete but execute not done -> `/curdx-flow:implement`
-- Execute complete but verification missing or failed -> `/curdx-flow:verify`
-- Verification complete but review missing or failed -> `/curdx-flow:review`
-- Stop-hook or execution parity drift -> `/curdx-flow:cancel`, then `/curdx-flow:implement --strategy=subagent`
-
-## Constraint
-
-Do not suggest a later-stage command when an earlier missing artifact or failed
-phase blocks it.

package/skills/ui-sketch/SKILL.md

@@ -1,39 +0,0 @@
----
-name: ui-sketch
-description: Use when the user needs UI design drafts, layout variants, mockups, prototypes, or styling direction.
-when_to_use: Triggers on "design UI", "UI design", "component layout", "variants", "wireframe", "mockup", "prototype", "sketch", "draft layout", "visual design", "styling", "CSS", "theming", "dark mode", "responsive design", "color scheme", "build me a UI", "show several variants", "try different colors".
-argument-hint: "\"<screen or component brief>\""
-context: fork
-agent: flow-ux-designer
-paths:
-  - "**/*.{html,css,scss,sass,less,js,jsx,ts,tsx,vue,svelte,astro}"
-  - "app/**"
-  - "pages/**"
-  - "components/**"
-  - "public/**"
----
-
-# UI Sketch
-
-This skill is for design exploration, not final implementation. Keep the
-entrypoint focused on design-brief intake, variant output requirements, and the
-iteration handoff. Detailed rules live in:
-
-- `references/brief-intake.md`
-- `references/variant-contract.md`
-- `references/iteration-handoff.md`
-
-## Design Brief
-
-Use `references/brief-intake.md` to confirm the brief before dispatching
-`flow-ux-designer`.
-
-## Variant Contract
-
-The required outputs for `flow-ux-designer` and optional `flow-ui-researcher`
-live in `references/variant-contract.md`.
-
-## Iteration Handoff
-
-How to pick, merge, or promote a variant lives in
-`references/iteration-handoff.md`.

package/skills/ui-sketch/references/brief-intake.md

@@ -1,10 +0,0 @@
-# UI Sketch Brief Intake — What to Clarify
-
-Before sketching, confirm:
-
-- what is being designed
-- context (consumer, enterprise, marketing, internal tool)
-- must-haves (brand, system, responsive constraints)
-- variant count
-
-If the user already provided all of this, do not over-interview.

package/skills/ui-sketch/references/iteration-handoff.md

@@ -1,5 +0,0 @@
-# UI Sketch Iteration Handoff — Pick, Merge, or Promote
-
-- if the user picks a variant, promote it into the active design discussion
-- if the user wants a hybrid, rerun with an explicit merge instruction
-- treat sketches as exploratory assets, not shipped implementation by default

package/skills/ui-sketch/references/variant-contract.md

@@ -1,15 +0,0 @@
-# UI Sketch Variant Contract — What Must Be Produced
-
-`flow-ux-designer` should:
-
-1. invoke the frontend-design workflow
-2. generate distinct variants
-3. write rationale for each variant
-4. optionally use `flow-ui-researcher` for precedent gathering
-
-## Required Artifacts
-
-- `.flow/specs/<active>/ui-sketch/`
-- `.flow/specs/<active>/ui-sketch/index.html`
-
-Each variant should include rationale and accessibility notes.

package/skills/verify/SKILL.md

@@ -1,56 +0,0 @@
----
-name: verify
-description: Verify the active spec against code, tests, and browser evidence.
-when_to_use: Use when implementation is done and the user wants proof that FRs, ACs, and ADs are actually satisfied rather than merely claimed complete.
-argument-hint: "[--strict]"
-disable-model-invocation: true
-context: fork
-agent: flow-verifier
----
-
-# Goal-Backward Verification
-
-Verify the active `.flow/` spec using goal-backward analysis. Keep this
-entrypoint focused on preflight, evidence scope, strict-mode expansion, and the
-final handoff. Detailed evidence rules live in:
-
-- `references/preflight.md`
-- `references/evidence-workflow.md`
-- `references/strict-mode.md`
-- `references/output-contract.md`
-- `references/report-handoff.md`
-
-## Arguments
-
-`$ARGUMENTS` optionally includes `--strict`.
-
-## Preflight
-
-Use `references/preflight.md` for the project-level guard.
-
-## Evidence Scope
-
-Use `references/evidence-workflow.md` for the full evidence contract.
-UI-facing checks still rely on `mcp__chrome_devtools__*` when browser evidence
-is required.
-
-## Strict Mode
-
-If `$ARGUMENTS` contains `--strict`, also apply the multi-source audit from
-`references/strict-mode.md`.
-
-## Deliverables and Gate
-
-Use `references/output-contract.md` for the required artifact and compact
-summary. The exact report structure, landing order, and post-write routing are
-governed by `references/report-handoff.md` plus the `flow-verifier` agent
-contract.
-Primary artifact: `.flow/specs/<name>/verification-report.md`.
-
-Apply `@${CLAUDE_PLUGIN_ROOT}/gates/verification-gate.md` before returning a
-PASS verdict.
-
-## Output to User
-
-Use `references/output-contract.md` for the final compact response. Next-step
-routing is defined in `references/report-handoff.md`.

package/skills/verify/references/evidence-workflow.md

@@ -1,39 +0,0 @@
-# Evidence Workflow — Verification Rules
-
-## Read Set
-
-Load:
-
-- `.flow/specs/<name>/requirements.md`
-- `.flow/specs/<name>/design.md`
-- `.flow/specs/<name>/tasks.md`
-- `.flow/specs/<name>/.progress.md`
-- `.flow/specs/<name>/.state.json`
-- `.flow/STATE.md`
-
-## Assertion Model
-
-Verify every relevant:
-
-- `FR`
-- `AC`
-- `AD`
-- implementation-relevant component existence
-
-For fix/debug specs, also verify `VF-original-issue`.
-
-## UI vs Code-Only
-
-- UI-facing ACs require browser verification through `mcp__chrome_devtools__*`
-- Code inspection plus `jsdom` / `happy-dom` tests are insufficient for
-  UI-facing ACs
-- If browser MCP is unavailable, mark UI-facing ACs as
-  `unverified — browser MCP missing`
-
-## Required Checks
-
-- run real tests or verify commands, never hypothetical ones
-- scan for stub and fake-completion patterns on FR-covered paths
-- apply `test-quality-gate` to every evidentiary test
-- downgrade assertions backed only by weak tests
-- require `.progress.md` BEFORE/AFTER reality checks for fix/debug work

package/skills/verify/references/output-contract.md

@@ -1,23 +0,0 @@
-# Verify Output Contract — Artifact and Summary
-
-## Artifact
-
-Write:
-
-```text
-.flow/specs/<name>/verification-report.md
-```
-
-## Summary
-
-After the report lands, respond with:
-
-```text
-✓ Verification complete: <spec-name>
-  FR coverage: N/M implemented (S stub, K missing)
-  AC coverage: N/M tested
-  Verdict: PASS | PARTIAL | MISSING
-  Report: .flow/specs/<name>/verification-report.md
-```
-
-Keep the response compact. The report file holds the detail.

package/skills/verify/references/preflight.md

@@ -1,11 +0,0 @@
-# Verify Preflight — Active Spec and Artifact Guard
-
-Before verifying:
-
-- `.flow/` must exist
-- `.flow/.active-spec` must be non-empty
-- `.flow/specs/<active>/requirements.md` must exist
-- `.flow/specs/<active>/design.md` must exist
-- `.flow/specs/<active>/tasks.md` must exist
-
-If any precondition fails, emit a clear error and stop immediately.

package/skills/verify/references/report-handoff.md

@@ -1,35 +0,0 @@
-# Report Handoff — Deliverable and Next Step
-
-## Deliverable
-
-Write:
-
-```text
-.flow/specs/<name>/verification-report.md
-```
-
-The first substantive action after gathering findings must be the `Write` call
-for the complete report. Do not preview the report first.
-
-## Gate Outcome
-
-- `PASS` -> verification evidence is complete; next logical step is
-  `/curdx-flow:review`
-- `PARTIAL` or `MISSING` -> address findings, then rerun `/curdx-flow:verify`
-
-## Output Summary
-
-After `Write` succeeds, respond with no more than 5 lines:
-
-```text
-✓ Verification complete: <spec-name>
-  FR coverage: N/M implemented (S stub, K missing)
-  AC coverage: N/M tested
-  Verdict: PASS | PARTIAL | MISSING
-  Report: .flow/specs/<name>/verification-report.md
-```
-
-Next:
-
-- `/curdx-flow:review` after a clean verification pass
-- `/curdx-flow:verify` again after fixes

package/skills/verify/references/strict-mode.md

@@ -1,12 +0,0 @@
-# Strict Mode — Multi-Source Audit
-
-When `--strict` is present, also apply
-`@${CLAUDE_PLUGIN_ROOT}/gates/coverage-audit-gate.md`.
-
-Cross-check:
-
-- every `FR` <-> `AC` <-> `AD` <-> task <-> test <-> commit chain
-- research recommendations versus the actual implementation
-- every relevant `D-NN` in `.flow/STATE.md`
-
-`--strict` expands evidence requirements; it does not relax any baseline gate.