spec-decomposition
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Decompose a SPEC, PRD, RFC, or design doc into a sequenced set of GitHub epics and child issues, where each issue is a self-contained prompt an agent or engineer can execute end-to-end. Use when the user says "decompose this spec", "break this PRD into issues", "file epics from this design doc", or "plan the implementation". Each issue is shaped as a 6-component prompt (prompt-engineering), sequenced via tracer-code so the skeleton lands first and every later issue keeps the system demoable, and gated by stay-green Done-Done plus max-quality-no-shortcuts anti-bypass rules. Issue bodies are written to `git-issues/` and filed via `gh issue create --body-file`, matching the file-based pattern in git-workflow. Do NOT use for single-task issue or PR creation (use git-workflow), backlog cleanup of existing issues (use backlog-grooming), PR code review (use comprehensive-pr-review), or choosing between technical approaches inside a SPEC (use architectural-decisions).
In this repository36 other files it gives its agents.
- address-feedbackSkill
- apple-to-android-port-specSkill
- architectural-decisionsSkill
- await-claude-reviewSkill
- backlog-groomingSkill
- bug-squashing-methodologySkill
- ci-debuggingSkill
- collect-skillsSkill
- comprehensive-pr-reviewSkill
- concurrencySkill
- continue-epicSkill
- cve-remediationSkill
- de-slopifySkill
- discord-ralph-recapSkill
- distribute-skillsSkill
- documentationSkill
- error-handlingSkill
- file-naming-conventionsSkill
- frontend-aestheticsSkill
- git-workflowSkill
- max-quality-no-shortcutsSkill
- mutation-testingSkill
- preflightSkill
- prompt-engineeringSkill
- quick-testSkill
- review-diffSkill
- scan-issue-writerSkill
- securitySkill
- skill-craftSkill
- statusSkill
- stay-greenSkill
- testingSkill
- tracer-codeSkill
- triage-and-planSkill
- user-facing-error-messagesSkill
- vibeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.