curdx-flow

Use when a spec has tasks.md and should enter autonomous task execution.

Use when starting curdx-flow, creating a spec, resuming work, or routing intent.

Use when handling curdx-flow flags, state files, delegation, execution loops, or skill entrypoint rules.

Use when curdx-flow needs user decisions after codebase facts are discovered.

Use when a spec has design.md and needs implementation tasks.

Use when showing curdx-flow slash skills, options, workflow, or troubleshooting.

Fixture help skill

Use when planning, running, or resuming curdx-flow spec-driven workflows.

Use when stopping an active curdx-flow execution loop or removing spec state.

Use when submitting curdx-flow feedback, bug reports, or feature requests.

Use when creating a new curdx-flow spec from a name and goal.

Use when inspecting curdx-flow specs, active state, progress, or index status.

Use when a spec has requirements.md and needs technical design.

Use when indexing codebase components or external resources for future specs.

Use when updating requirements, design, or tasks after implementation learnings.

Use when a spec has research or goal context and needs requirements.

Use when running or re-running discovery research for the active spec.

Use when changing the active spec by name or path.

Use when a large feature should be decomposed into dependency-aware specs.

Use when optimizing a task prompt or asking how to route curdx-flow work without executing it.

Use when checking fixes, phase exits, completion evidence, or mock-heavy tests before claiming success.