plan-increment
Skill0 starsChanged 16 days agoMITView on GitHub
Plan an increment from stated capacity, dependencies, and existing artifacts. Use when the user asks for a sprint plan, increment plan, iteration plan, or /plan-increment. Do not invent headcount or dates that are not on the baseline.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Do not invent headcount, velocity, or a commitment date.
- Distinctive: line 36
If capacity is missing, stop.
- Distinctive: line 45
Read AGENTS.md if present.
≈ “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
Plan increment
Fit work to capacity someone stated. This is not write-dev-tasks and not write-status.
Do not invent headcount, velocity, or a commitment date.
Is this the right skill?
| Signal | Do this instead |
| Break a design into tasks | write-dev-tasks |
| Rank the backlog | prioritize-backlog |
| Weekly RAG | write-status |
| Scope change | assess-change |
Required inputs
- Capacity the team already stated this session or in a file (people × time, or a number they use)
- Candidates with artifact paths (tasks, requirements, backlog rank)
- RAID if it exists (dependencies)
If capacity is missing, stop. Forecast without capacity is forbidden.
Human decisions (do not invent)
- Commitment vs forecast
- What is in vs out of the increment
Procedure
- Read
AGENTS.mdif present. Read RAID and the backlog/tasks named. - Find the home:
docs/govern/increment-YYYY-MM-DD.md. - Open references/increment-template.md. Copy every heading. Write
n/awhen unused. - In: only items with a path and a rough size from the user or the task file. Out: everything else.
- Dependencies stay as RAID ids. Do not invent a date.
Output
- Path:
docs/govern/increment-YYYY-MM-DD.md - Template:
references/increment-template.md
Quality bar
- Capacity is sourced (user or file)
- Every in-item has an artifact path
- Commitment vs forecast is
unassignedunless the user set it - Unused headings are
n/a
Done
- Path
- In count / out count
- Next skill:
write-status/triage-blockers/deliver-sliceon item 1
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.