sprint-tasks
Skill4 starsChanged 26 days agoNo licenceView on GitHub
Decompose a plan document (a PLAN.md, PRD, design doc, or any written statement of a goal) into individual, numbered sprint tasks, each in a fixed ticket shape — user story, context, scope, requirements, acceptance criteria, Definition of Done, dependencies, references, delivery fields, and a Proof of value — preceded by a manifest and a parallel execution plan showing which tasks can be worked simultaneously (e.g. by separate Claude instances acting as parallel developers). Use when the user says \"break this plan into tasks\", \"turn this into tickets\", \"decompose this into sprint tasks\", hands over a plan/PRD and asks what the tickets look like, asks for a backlog from a goal, or wants to know what can be run in parallel, and when a wave of tasks is about to be built — each wave goes to parallel subagents. Requires a `SPEC.md`: every task names the requirements it discharges, and a sprint is measured by which requirements it turns green, so if no spec exists this skill stops and drafts one with the user first. This skill only reads the plan, it never writes or owns it. Each task's Proof of value section follows the dedicated value-proof procedure, not written inline from scratch.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- block-diagramSkill
- brainstormSkill
- buildSkill
- call-treeSkill
- checkpoint-commitsSkill
- code-proofSkill
- code-tidySkill
- codifySkill
- coding-standardsSkill
- consistencySkill
- escalateSkill
- experimentSkill
- explainSkill
- hparam-priorsSkill
- minimal-coverSkill
- ml_loggingSkill
- notesSkill
- outlineSkill
- plan-docSkill
- prior-workSkill
- project-briefSkill
- proof-of-valueSkill
- recapSkill
- reflectSkill
- repo-layoutSkill
- reportSkill
- rl-env-mvpSkill
- run-triageSkill
- schema-diagramSkill
- sequence-diagramSkill
- sft-env-mvpSkill
- skill-auditSkill
- skills-repo-accessSkill
- spec-docSkill
- test-planSkill
- tldrSkill
- tune-loopSkill
- tune-preflightSkill
- tune-reportSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 7 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
8
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.