decompose-prd
Skill1 starsChanged 2 months agoMITView on GitHub
Convert a PRD into atomic implementation tasks with dependencies, file ownership, requirement traceability, verification methods, and parallelization safety.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- agentic-uxSkill
- benchmarkSkill
- capability-routerSkill
- codex-adapterSkill
- context-handoffSkill
- create-prdSkill
- creative-direction-sprintSkill
- design-criticSkill
- design-engineering-qualitySkill
- design-intakeSkill
- design-opsSkill
- design-system-auditSkill
- design-systemSkill
- design-tokensSkill
- discoverSkill
- harness-evolutionSkill
- interaction-designSkill
- loop-engineeringSkill
- parallel-planSkill
- performance-uxSkill
- polishSkill
- product-design-routerSkill
- project-onboardingSkill
- research-ledgerSkill
- responsive-auditSkill
- security-gateSkill
- self-improvement-loopSkill
- specialist-routerSkill
- strategizeSkill
- token-auditSkill
- user-needsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 51
Write JSON Lines to: docs/40-execution/TASKS.jsonl
≈ “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.
Files
Decompose PRD
Input
Read:
- PRD
- acceptance criteria
- architecture
- design system
- current state
Task quality bar
Every task needs:
idtitlegoalrequirement_idsacceptance_idsownerdepends_onstatusfiles_ownedverificationrisknotes
Atomicity
A task should be:
- understandable independently,
- verifiable independently,
- small enough for one bounded loop,
- free of hidden cross-team ownership.
Parallelization
Mark a task parallel-safe only if:
- dependencies are satisfied,
- file ownership does not overlap,
- shared mutable state is not being changed concurrently,
- merge order is defined.
Output
Write JSON Lines to:
docs/40-execution/TASKS.jsonl
Then update:
docs/40-execution/PARALLELIZATION.md
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.