planning-and-task-breakdown SKILL.md skillA
planning-and-task-breakdown from gastonchevarria/god-mode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gastonchevarria/god-mode/planning-and-task-breakdown@git:20260926.2e7e5dbPins git:20260926.2e7e5db in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gastonchevarria/god-mode
- Path
plugins/god-mode-dev/skills/planning-and-task-breakdown/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260926.2e7e5db, committed Sep 26, 2026
- First version recorded
- Sep 26, 2026
- Size
- 7,681 bytes
- Repository stars
- 3
- License
- MIT
Breaks an agreed spec into small, ordered vertical-slice tasks with acceptance criteria and checkpoints, saved under tasks/. Use when asked to "break this down", "make a task list", "what order do we build this?" or "split for parallel agents". Runs no reviews (see autoplan).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Planning and Task Breakdown ## Overview Decompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session. ## When to Use - You have a spec and need to break it into implementable units - A task feels too large or vague to start - Work needs to be parallelized across multiple agents or sessions - You need to communicate scope to a human - The implementation order isn't obvious **When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks. ## The Planning Process ### Step 1: Enter Plan Mode Before writing any code, operate in read-only mode: - Read the spec and relevant codebase sections - Identify existing patterns and conventions - Map dependencies between components - Note risks and unknowns **Do NOT write code during planning.** The output is a plan document saved to `tasks/plan.md` and a task list saved to `tasks/todo.md`, not implementation. ### Step 2: Identify the Dependency Graph …
Read the whole file at its exact version.
How to install
mdr add gastonchevarria/god-mode/planning-and-task-breakdown@sha256:261bcdb32707e670The line at the top of this page pins the label git:20260926.2e7e5db, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pqbtb4uzdoww6t25)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.2e7e5db latest | 2026-09-26 | 2e7e5db | 7,681 B | A | view · diff |
| git:20260926.941aa31 | 2026-09-26 | 941aa31 | 7,632 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7681 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gastonchevarria/god-mode · 3 stars · license MIT · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pqbtb4uzdoww6t25 GET https://markdownregistry.com/api/v1/resolve?ref=gastonchevarria/god-mode/planning-and-task-breakdown GET https://markdownregistry.com/api/v1/blob/261bcdb32707e670389e7a7061881b9f26e2e09b4494e85eef394d82553a6007
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from gastonchevarria/god-mode
Every file in gastonchevarria/god-mode