@curdx/flow 2.3.11 → 3.1.0

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,27 +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`
-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,24 +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>
-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.

package/templates/CONTEXT.md.tmpl

@@ -1,53 +0,0 @@
-# {{PROJECT_NAME}} — User Preferences and Decisions
-
-> CurDX-Flow Context — your coding, design, and interaction preferences. Agents read this to understand your taste.
-
----
-
-## Code Style Preferences
-
-- **Indentation**: <!-- 2 spaces / 4 spaces / Tab -->
-- **Quotes**: <!-- single / double -->
-- **Semicolons**: <!-- always / never / asi -->
-- **Naming**: <!-- camelCase / snake_case / PascalCase -->
-- **Comment density**: <!-- minimal / when non-obvious / generous -->
-
-## Architecture Preferences
-
-- **Error handling**: <!-- try/catch / Result type / panics -->
-- **Async pattern**: <!-- async/await / promises / callbacks -->
-- **Dependency injection**: <!-- constructor / service locator / none -->
-- **Testing style**: <!-- TDD / test-after / integration-heavy -->
-
-## UI/UX Preferences
-
-- **Design style**: <!-- minimalist / brutalist / corporate / playful -->
-- **Color scheme**: <!-- light / dark / auto / specific palette -->
-- **Typography**: <!-- system / Inter / Space Grotesk / other -->
-- **Density**: <!-- spacious / compact / mixed -->
-- **Animation**: <!-- none / purposeful / expressive -->
-
-## Communication Preferences
-
-- **Language**: <!-- Simplified Chinese / English / bilingual -->
-- **Verbosity**: <!-- terse / balanced / verbose -->
-- **Explanation depth**: <!-- surface / mechanism / first-principles -->
-- **When to ask**: <!-- ask at any fork / only on major decisions / be autonomous -->
-
-## Tooling Preferences
-
-- **Package manager**: <!-- npm / pnpm / yarn / bun -->
-- **Runtime**: <!-- node / bun / deno -->
-- **Test framework**: <!-- vitest / jest / other -->
-- **Linter**: <!-- eslint / biome / other -->
-- **Commit convention**: <!-- conventional / gitmoji / free -->
-
-## Special Requirements
-
-<!-- Rules specific to this project -->
-
-- TODO:
-
----
-
-_Generated by `/curdx-flow:init` on {{CREATED_DATE}}. Update to match your actual preferences._

package/templates/PROJECT.md.tmpl

@@ -1,59 +0,0 @@
-# {{PROJECT_NAME}}
-
-> CurDX-Flow project vision — 500 lines max, loaded on every session
-
----
-
-## One-line Description
-
-<!-- In one sentence, state what this project is, for whom, and what problem it solves -->
-
-TODO: fill in the one-line description of the project
-
-## Why This Project Exists
-
-<!-- Background, motivation, pain points to solve -->
-
-TODO:
-
-## Core Users
-
-<!-- Who will use it? Their typical scenarios? -->
-
-TODO:
-
-## Success Criteria
-
-<!-- 3-5 verifiable metrics (e.g. "first response < 100ms", "weekly active users > 1000") -->
-
-1. TODO:
-2. TODO:
-3. TODO:
-
-## Tech Stack (with Rationale)
-
-<!-- Write the reasoning for each choice to avoid future second-guessing -->
-
-| Layer | Choice | Rationale |
-|---|-----|------|
-| Frontend | TODO | TODO |
-| Backend | TODO | TODO |
-| Database | TODO | TODO |
-| Deployment | TODO | TODO |
-
-## Out of Scope (Scope Guard)
-
-<!-- Explicitly list what does not belong in this project, to prevent scope creep -->
-
-- ✗ TODO:
-- ✗ TODO:
-
-## Constraints
-
-<!-- Budget, time, team size, compliance, etc. -->
-
-- TODO:
-
----
-
-_Generated by `/curdx-flow:init` on {{CREATED_DATE}}. Maintainer: {{USER_NAME}}_

package/templates/ROADMAP.md.tmpl

@@ -1,50 +0,0 @@
-# {{PROJECT_NAME}} — Roadmap
-
-> CurDX-Flow ROADMAP — phase plan and success criteria. Works alongside `.flow/specs/*`: ROADMAP sets direction, specs handle concrete implementation.
-
----
-
-## Current Version: v0.1 (MVP)
-
-**Goal**: <!-- one sentence -->
-
-TODO: describe the minimum viable product to deliver in v0.1.
-
-### Success Criteria (v0.1)
-
-<!-- Must be verifiable -->
-
-- [ ] TODO:
-- [ ] TODO:
-- [ ] TODO:
-
-### Phases
-
-<!-- List in development order -->
-
-#### Phase 1 — TODO
-- Goal:
-- Related spec: `specs/<name>`
-- Completion criteria:
-
-#### Phase 2 — TODO
-- Goal:
-- Completion criteria:
-
----
-
-## Next Version: v0.2
-
-**Theme**: TODO
-
-No details yet.
-
----
-
-## Vision (12 months)
-
-TODO: describe what this project should look like one year from now.
-
----
-
-_Initialized on {{CREATED_DATE}}. The roadmap is a statement of intent, not a commitment._

package/templates/STATE.md.tmpl

@@ -1,49 +0,0 @@
-# {{PROJECT_NAME}} — Cross-Session State
-
-> CurDX-Flow STATE — explicit decision log + important context. Agents read this file at the start of every session.
->
-> Division of labor with claude-mem: claude-mem captures everything automatically; STATE.md only records **decisions you and the agent explicitly agreed on**.
-
----
-
-## Key Decisions
-
-<!--
-Format: D-NN | YYYY-MM-DD | decision | why
-Once a decision is recorded, subsequent agents must explicitly note "I challenge D-NN" before violating it.
--->
-
-<!-- Example (delete on init):
-- **D-01** | 2026-04-19 | Use JWT instead of session cookie | Support cross-origin SPA
-- **D-02** | 2026-04-19 | bcrypt cost factor = 12 | Balance 10K QPS performance with security
--->
-
-No decisions yet.
-
-## Blockers
-
-<!-- Items currently blocking progress, and who/what is being waited on -->
-
-No blockers.
-
-## Open Questions
-
-<!-- Questions that need user answers or investigation -->
-
-None yet.
-
-## Important Context
-
-<!-- Long-standing context the agent should remember, not quite at "decision" level -->
-
-None yet.
-
-## Milestones
-
-<!-- Project-level major milestones -->
-
-None yet.
-
----
-
-_Initialized on {{CREATED_DATE}}. This file will grow as the project evolves._

package/templates/config.json.tmpl

@@ -1,51 +0,0 @@
-{
-  "$schema": "https://raw.githubusercontent.com/wdx/curdx-flow/main/schemas/config.schema.json",
-  "version": "1.0",
-  "mode": "standard",
-  "_mode_options": "fast | standard | enterprise",
-
-  "execution": {
-    "strategy": "auto",
-    "_strategy_options": "auto | subagent | stop-hook | wave | linear",
-    "max_parallel": 5,
-    "subagent_threshold": 8,
-    "wave_fail_policy": "continue-on-single",
-    "recovery_mode": "manual",
-    "_recovery_mode_options": "manual | fix-task",
-    "max_fix_tasks_per_original": 2
-  },
-
-  "gates": {
-    "always_on": [
-      "karpathy-gate",
-      "verification-gate"
-    ],
-    "standard_mode": [
-      "tdd-gate",
-      "coverage-audit-gate"
-    ],
-    "enterprise_mode": [
-      "adversarial-review-gate",
-      "edge-case-gate",
-      "security-gate",
-      "devex-gate"
-    ]
-  },
-
-  "specs": {
-    "directories": ["./.flow/specs"],
-    "default_task_size": "fine",
-    "_task_size_hint": "as-needed decomposition (no fixed count) — see agents/flow-planner.md"
-  },
-
-  "addons": {
-    "pua": {
-      "enabled": false,
-      "style": "alibaba",
-      "_style_options": "alibaba | bytedance | huawei | tencent | baidu | pdd | meituan | jd | xiaomi | netflix | musk | jobs | amazon",
-      "auto_trigger": "on-failure"
-    }
-  },
-
-  "created": "{{CREATED_DATE}}"
-}