From curdx-flow
Invoke when user wants to break a large feature into multiple smaller specs with a dependency graph. Triggers on "epic", "big feature", "too big", "decompose", "break down", "break into", "split into", "multi-spec", "multiple features", "sub-features", "vertical slice", "parent feature", "large scope", "won't fit in one sprint", "needs splitting".
npx claudepluginhub curdx/curdx-flow --plugin curdx-flowThis skill is limited to using the following tools:
You are invoked when the user wants to break a large feature into multiple vertical-slice specs.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are invoked when the user wants to break a large feature into multiple vertical-slice specs.
.flow/ project must exist (run /curdx-flow:init first if missing).Ask the user (or infer from context) for:
flow-triage-analystDelegate to the flow-triage-analyst agent with the epic name + goal + boundary. The agent returns:
Create .flow/_epics/<epic-name>/epic.md with:
# Epic: <name>
## Goal
<one sentence>
## Slices (vertical)
| ID | Slice | Depends on | Shared interface |
|----|-------|-----------|------------------|
| S1 | ... | — | — |
| S2 | ... | S1 | `types/auth.ts` |
| S3 | ... | S1 | — |
## Frozen Interfaces
(contracts that must not change once slices start)
## Out of Scope
- ...
For each slice, create .flow/specs/<epic-name>-<slice-id>/ with a minimal .state.json linking back to the epic manifest.
Summarize: "Epic <name> decomposed into N vertical slices. Start any slice with /curdx-flow:start <epic-name>-<slice-id>. Suggested order: S1 → S2 → S3."
@${CLAUDE_PLUGIN_ROOT}/knowledge/epic-decomposition.md@${CLAUDE_PLUGIN_ROOT}/templates/