Menu
Break down a coding task into a structured implementation plan with clear steps, file identification, and risk assessment.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | planning |
| description | Break down a coding task into a structured implementation plan with clear steps, file identification, and risk assessment. |
Use this skill when starting a new coding task to create a thorough implementation plan.
grep to find code related to the taskUse write_todos to create a structured plan:
write_todos([
"1. <specific change in specific file>",
"2. <next specific change>",
"3. Write tests for <feature>",
"4. Run test suite and fix failures",
"5. Review all changes"
])
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
Read the user's coding preferences from /memory/coding-prefs.md before making non-trivial style decisions, and append new preferences when the user gives durable feedback.
Searches arXiv for preprints and academic papers, retrieves abstracts, and filters by topic. Use when the user asks to find research papers, search arXiv, look up preprints, find academic articles in physics, math, CS, biology, statistics, or related fields.
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, or tool integrations. Use this skill when the user asks to: (1) create a new skill, (2) make a skill, (3) build a skill, (4) set up a skill, (5) initialize a skill, (6) scaffold a skill, (7) update or modify an existing skill, (8) validate a skill, (9) learn about skill structure, (10) understand how skills work, or (11) get guidance on skill design patterns. Trigger on phrases like "create a skill", "new skill", "make a skill", "skill for X", "how do I create a skill", or "help me build a skill".
Take a note.
Summarise text into a one-paragraph summary.