feature-spec
Skill4 starsChanged 51 days agoMITView on GitHub
Create an implementation-ready specification for one feature from feature_list.json. Use when the user asks to plan a feature, create a feature spec, apply lightweight SDD/spec-driven development, prepare work for another implementation agent, or generate specs/tasks/technical plan from the feature list. If no feature id is provided, select the first dependency-ready feature in feature_list.json order that is neither passing nor accepted.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- lyeyixian/skillstheir own version, first seen Nov 16, 2026
- dvy1987/agent-loomtheir own version, first seen Nov 15, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- CesarRivasP/feature-spectheir own version, first seen Oct 15, 2026
- PiloTracer/pilo.ai.logicbisontheir own version, first seen Oct 11, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
Used with
Projects with it also use changelog and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- WikiEducationFoundation/WikiEduDashboard★ 434same name
- PackmindHub/packmind★ 323same name
- https-deeplearning-ai/sc-spec-driven-development-files★ 310same name
- natnew/awesome-ai-scientists★ 20same name
- yasunori0418/skills★ 9same name
- insight68/Skills★ 5same name
- carreiras/claude-skills★ 4same name
- dvy1987/agent-loom★ 4same name
- gonimar/claude-web-studio★ 4same name
- Simone-Tarantino/godot-superpowers★ 2same name
12 more not listed
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.
- build-briefSkill
- feature-validatorSkill
- harness-starterSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 9 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
All paths in this skill are relative to the repository root.
- Distinctive: line 15
Do not implement code.
- Distinctive: line 16
Do not modify application source files.
- Distinctive: line 17
Do not generate specs for every feature unless the user explicitly asks after this skill finishes.
- Very specific: line 18
Create or update only docs/specs/<feature-id>.md by default.
- Very specific: line 19
If the feature id is not provided, select the first feature in feature_list.json order whose status is neither passing nor accepted and …
- Very specific: line 20
If a feature is too broad to plan cleanly, stop and recommend splitting it in feature_list.json instead of producing a vague spec.
- Distinctive: line 21
Treat the spec as a contract between agents: planner -> implementer -> validator.
- Distinctive: line 22
Prefer concrete repository findings over assumptions.
- Very specific: line 42
If feature_list.json is missing, stop and tell the user to run the harness-starter skill first.
- Very specific: line 48
Use a user-provided feature id when present.
- Very specific: line 52
Before planning, verify the feature has enough scope information: id, title, user_visible_behavior, depends_on, and verification.
- Very specific: line 71
Create or update docs/specs/<feature-id>.md using references/spec-template.md.
- Distinctive: line 90
Keep the spec concise but operational.
- Distinctive: line 101
If a persistent E2E command exists and the feature changes user-visible behavior, authentication, authorization, routing, or API flows, the …
- Distinctive: line 107
If the spec fails this gate, revise it before reporting completion.
“Common” is measured: kept by at least 6 in 10 of the 20 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 Spec
Use this skill to turn one harness feature into an implementation-ready contract for another agent. The output is not a PRD and not implementation code. It is a planning artifact that lets a future implementation session execute with minimal rediscovery, and lets a later validation session judge the result.
All paths in this skill are relative to the repository root.
Hard Rules
- Plan exactly one feature per run.
- Do not implement code.
- Do not modify application source files.
- Do not generate specs for every feature unless the user explicitly asks after this skill finishes.
- Create or update only
docs/specs/<feature-id>.mdby default. - If the feature id is not provided, select the first feature in
feature_list.jsonorder whose status is neitherpassingnoracceptedand whosedepends_onprerequisites are satisfied. - If a feature is too broad to plan cleanly, stop and recommend splitting it in
feature_list.jsoninstead of producing a vague spec. Rough signal: it needs more than one data model plus one user flow, or the spec would clearly exceed the 100-250 line target. - Treat the spec as a contract between agents: planner -> implementer -> validator.
- Prefer concrete repository findings over assumptions. If something was not inspected, say so.
Inputs To Read First
AGENTS.mdPROGRESS.mdfeature_list.json- Existing feature spec if present:
docs/specs/<feature-id>.md - Product/discovery docs as needed:
CONTEXT.mddocs/build-brief.mddocs/domain-model.mddocs/user-and-access-model.mddocs/technical-discovery.mddocs/mvp-scope.mdDESIGN.mdwhen the selected feature has UI or visual behaviordocs/risks-and-open-questions.mddocs/adr/*.md
- Existing application files relevant to the selected feature. Inspect enough of the repo to identify expected file changes, patterns, commands, and risks.
If feature_list.json is missing, stop and tell the user to run the harness-starter skill first.
Workflow
1. Select The Feature
Use a user-provided feature id when present. Otherwise, choose the first feature in feature_list.json order with status other than passing or accepted whose depends_on prerequisites are satisfied. Prefer an in_progress feature over a not_started feature if one exists.
A dependency is satisfied when the referenced feature id exists and has status accepted. For legacy feature lists, a dependency with status passing may be treated as satisfied only when durable evidence shows independent validator acceptance. If depends_on is absent in an older feature list, treat it as [] for backward compatibility. If the first unfinished features are blocked by dependencies, skip them only when looking for a later dependency-ready feature; report the skipped blockers in the summary.
Before planning, verify the feature has enough scope information: id, title, user_visible_behavior, depends_on, and verification. If not, improve the feature entry only if the user explicitly asked for feature-list maintenance; otherwise stop and report the missing fields.
2. Research The Repository
Investigate how to implement the selected feature in this specific repo:
- current app/framework state,
- existing routes, components, modules, tests, scripts, or conventions,
- relevant data models and migrations,
- relevant API boundaries,
- relevant auth/permission patterns,
- verification commands available today,
- persistent E2E commands available today, such as
pnpm test:e2e, when the feature has user-facing or API-flow behavior, - gaps caused by pre-bootstrap or missing infrastructure.
Record inspected files in the spec. Do not pretend to have inspected files that do not exist.
3. Write The Feature Implementation Spec
Create or update docs/specs/<feature-id>.md using references/spec-template.md. If the repo already has accepted specs under docs/specs/, use one as a reference for the right level of detail.
The spec must include:
- source feature metadata,
- goal and non-goals,
- job story or user story,
- acceptance scenarios in Given/When/Then style,
- repository research,
- technical approach,
- expected file changes,
- visual design impact when UI is involved,
- durable documentation impact,
- implementation plan,
- implementation tasks,
- verification plan,
- evidence to capture,
- validator checklist.
Keep the spec concise but operational. A good default target is 100-250 lines. If it grows far beyond that, the feature may need splitting.
4. Quality Gate
Before finishing, check:
- A future implementer can identify exactly what to build without reading this chat.
- A future validator can decide whether the implementation satisfies the spec.
- The plan names concrete files or directories where possible.
- The tasks are ordered and executable.
- Verification includes commands or manual checks available in the repo's current state.
- If a persistent E2E command exists and the feature changes user-visible behavior, authentication, authorization, routing, or API flows, the verification plan should include adding/updating focused E2E coverage or explicitly justify why unit/integration coverage is enough.
- For shell scripts such as
init.sh, the spec states whether the script must execute checks, print guidance, start services, or provide modes. The default harness rule is:init.shexecutes non-blocking startup/verification checks and must not start long-running dev servers. - Durable documentation impact is explicit:
ARCHITECTURE.md,CONSTRAINTS.md,AGENTS.md, and other durable docs are each marked create/update/not needed with a reason. - Non-goals prevent scope creep.
- Unknowns are explicit and do not hide blocking ambiguity.
If the spec fails this gate, revise it before reporting completion.
Output Summary
Report:
- selected feature id,
- spec path,
- whether the feature looked correctly sized,
- key implementation risks,
- next suggested action: usually hand the spec to an implementation agent.
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.

