prd-to-kanban
Skill4 starsChanged 7 months agoMITView on GitHub
Convert a PRD, design doc, or feature requirements into work/kanban.md and work/SUBAGENT.md for multi-agent implementation planning. Planning only. Sub-command: install for Claude Code trigger rules.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ThomasDixini/AI-Workflow-For-Projectstheir own version, first seen Jul 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ThomasDixini/AI-Workflow-For-Projects★ 1same 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.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the shared implementation instructions at plugins/prd-to-kanban/SKILL.md and follow them exactly.
- Very specific: line 12
If plugins/prd-to-kanban/SKILL.md is unavailable, use this fallback:
- Distinctive: line 15
Use verifiable acceptance criteria for every task.
- Distinctive: line 16
Put frozen contract/schema work in Wave 0.
- Very specific: line 18
Keep SUBAGENT.md under 80 lines with project summary, stack, frozen contracts, write scopes, and subagent reporting conventions.
≈ “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
PRD to Kanban
This is the standalone skill entry for prd-to-kanban.
Read the shared implementation instructions at plugins/prd-to-kanban/SKILL.md and follow them exactly. That file is the source of truth for triggers, output format, task granularity, acceptance criteria, dependency layering, and handoff rules.
If plugins/prd-to-kanban/SKILL.md is unavailable, use this fallback:
- Convert the PRD or requirements into two files:
<project>/work/kanban.mdand<project>/work/SUBAGENT.md. - Plan only. Do not implement tasks.
- Use verifiable acceptance criteria for every task.
- Put frozen contract/schema work in Wave 0.
- Compute dependency layers, parallelism windows, and the critical path.
- Keep
SUBAGENT.mdunder 80 lines with project summary, stack, frozen contracts, write scopes, and subagent reporting conventions. - Report the generated paths. Do not open files or launch external viewers unless the user explicitly asks.
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.