planning is agent-read markdown (skill) from ulises-jeremias/agent-toolkit: WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on Best.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Planning and Estimation (WHAT)
Use this skill when work needs planning, breakdown, estimation, or capacity validation before it becomes final backlog content.
## Default guardrails
1. Apply **`output-handshake`** before producing any final planning artifact: ask where it should live and confirm human review.
2. Prefer project-specific planning rules if the repo, ticket system, or engagement pack defines them. Otherwise use this default.
3. If a work item is being created or refined, pair this with **`work-item`** and the relevant atomic skill.
## What to check
- Scope and goal are clear.
- Work is broken down into manageable items; anything estimated at 5+ points should be considered for splitting.
- Acceptance criteria and dependencies are known enough for estimation.
- Estimation technique is explicit: planning poker, T-shirt sizing, Fibonacci, or the team override.
- Capacity considers availability, holidays, meetings, focus factor, dependencies, and historical velocity.
## References
- `references/default-template.md` - default planning and capacity template
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_uxdvsr5zwz5gvhcr
GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/planning
GET https://markdownregistry.com/api/v1/blob/129d731aba0f77ea6dca0bfaa882ae7343a690e7badd9b98357ec9d9e8267eeb
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/adr/SKILL.md · WHAT — Create and maintain Architecture Decision Records (ADRs) per the process. Covers when
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/bug/SKILL.md · WHAT - Draft and review bugs using the Bug Template; classifies whether an issue should be
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/c4-model/SKILL.md · WHAT — C4 model methodology (Context, Container, Component, Code) guidance — what to draw at each level, when, and how…
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/chrome-devtools/SKILL.md · Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and…
serejaris/personal-corp-os · templates/department/skills/planning/SKILL.md · Use when a completed department retro should become accepted outcomes and a full living ISO-week plan, or the user asks…
nerds-odd-e/doughnut · .agents/skills/planning/SKILL.md · Routes planning scope and lifecycle to installed Open Dough guidance. Use for planning, story delivery, and .planning/…
iliaal/ai-skills · skills/planning/SKILL.md · Software implementation planning with optional file-based persistence. Use when asked to plan, when unresolved…
