Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From feature-design
Adversarial-pressure feature design pipeline. Trigger when the user has a new feature idea, wants to triage whether something needs design work, asks for help turning an idea into a spec, wants to break a spec into epics and stories, or needs an implementation Principal Engineer prompt. Use whenever the user mentions "design a feature", "feature idea", "triage", "problem statement", "screen contract", "ui contract", "feature spec", "epics", "stories breakdown", or "implementation handoff".
npx claudepluginhub choughton/feature-design-prompt-templates --plugin feature-designHow this skill is triggered — by the user, by Claude, or both
Slash command
/feature-design:feature-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides a structured pipeline for taking a feature from a raw idea to implementation-ready epics, stories, and a Principal Engineer prompt. It wraps eight prompt templates into slash commands and tracks state across stages in a per-feature session folder.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
This skill provides a structured pipeline for taking a feature from a raw idea to implementation-ready epics, stories, and a Principal Engineer prompt. It wraps eight prompt templates into slash commands and tracks state across stages in a per-feature session folder.
Trigger this skill when the user:
Do NOT trigger this skill for:
/feature-design:start with --entry-point spec-only if needed, but prefer skipping the plugin for these)There are three entry points depending on session state:
Recommend /feature-design:start <feature-name> -- <raw idea>. Example:
Sounds like a feature design task. Run:
/feature-design:start <feature-name> -- <one-line description of the idea>That will create a session folder, capture the idea, and run triage. From there
/feature-design:nextwalks the rest of the pipeline.
Look for .feature-design/CURRENT in the working folder. If it exists, read the slug and .feature-design/<slug>/state.json to find the current stage. Recommend /feature-design:next to advance, or /feature-design:status for a snapshot.
If the user asks for a specific stage out of context (e.g., "draft a problem statement", "give me a screen contract"), point them at the corresponding command:
| User intent | Command |
|---|---|
| Triage / coverage check | /feature-design:triage |
| Explore the idea | /feature-design:explore |
| Draft problem statement | /feature-design:problem |
| UI / Screen Contract | /feature-design:ui-draft |
| Verify the design | /feature-design:verify |
| Generate spec | /feature-design:spec |
| Break spec into epics | /feature-design:epics |
| Generate PE prompt | /feature-design:pe-setup |
Each step command requires an active session (created via /feature-design:start). If the user wants a one-shot of a stage without ceremony, recommend /feature-design:start first — the session folder is lightweight and the staging makes downstream stages work.
Sessions live in .feature-design/<slug>/ in the user's working folder. The plugin writes:
00-feature-idea.md — raw idea capture01-triage.md — triage assessment02-exploration.md — exploration transcript03-problem-statement.md04-ui-contract.md (user-facing only)07-verification.md (slots 05/06 reserved for future crossfire docs)08-spec.md09-epics.md10-pe-prompt.mdstate.json — pipeline stateA .feature-design/CURRENT file holds the active session's slug.
Crossfire and decision-synthesis stages (Templates 05, 06, 08, 09, 10, 11 in the original repo) are not in this v1. The pipeline runs single-agent through verification. When crossfire is added later, the numbering gaps in the output filenames give the new stages a place to land without renumbering existing artifacts.