feature-design
Skill1 starsChanged 6 months agoMITView on GitHub
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".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Wiserax/wisecrafttheir own version, first seen Oct 25, 2026
- streetsidesoftware/cspelltheir own version, first seen Oct 17, 2026
- yh594774855/skill-collectiontheir own version, first seen Aug 3, 2026
- masterno/agent-skillstheir own version, first seen Apr 16, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- streetsidesoftware/cspell★ 1.7ksame name
- masterno/agent-skills★ 2same name
- Wiserax/wisecraft★ 0same name
- yh594774855/skill-collection★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- claude-cliSkill
- codexSkill
- geminiSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Do NOT trigger this skill for:
- Very specific: line 47
Look for .feature-design/CURRENT in the working folder.
- Distinctive: line 51
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 …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Feature Design Pipeline
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.
When to suggest this skill
Trigger this skill when the user:
- Has a new feature idea and isn't sure how to scope it
- Asks "is this feature already covered by our docs?" or wants triage
- Wants to draft a problem statement
- Wants a Screen Contract / UI structural contract for a user-facing feature
- Wants a feature specification
- Wants to break a spec into epics and stories
- Wants to set up a Principal Engineer prompt for multi-agent implementation
- Mentions any of: feature design, feature idea, triage, problem statement, screen contract, feature spec, epic breakdown, story breakdown, PE setup, principal engineer prompt
Do NOT trigger this skill for:
- Simple bug fixes
- Pure refactors with no design questions
- Tasks that already have settled requirements and just need stories (use
/feature-design:startwith--entry-point spec-onlyif needed, but prefer skipping the plugin for these)
How to route the user
There are three entry points depending on session state:
No active session yet
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.
Active session already exists
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.
Mid-pipeline ask
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.
Session folder layout
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 state
A .feature-design/CURRENT file holds the active session's slug.
What's deferred
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.