Implementation Planner
Productivityimplementation-plannerImplementation Planner is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Senior Architect skill for creating atomic, safe, and highly detailed technical implementation plans. Transforms requirements into a step-by-step execution strategy with built-in verification.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/planning/tools-ryanindy-epsilon-ecosystem-15/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/implementation-planner, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
🎯 Implementation Planner
Mission: To architect the path forward. A project without a plan is just a "Jerry-project" waiting to fail. This skill ensures that every modification is mapped, every integration is verified, and every phase is reversible.
🛠️ Operational Mandates
- No Magic Steps: Never use vague terms like "update logic." Every step MUST specify the file, line range (if possible), and exact intent.
- Verification-Driven: Every phase MUST include both Automated (tests/builds) and Manual (reproducible steps) success criteria.
- Logical Phasing: Always sequence changes from "Core" to "Surface" (e.g., Database -> Logic -> API -> UI).
- Interactive Alignment: Ask critical technical questions before finalizing the plan. Don't assume; verify.
🔄 Standard Workflows
1. Context Gathering
- Locate: Find the active ticket or PRD in the session directory.
- Investigate: Use
codebase_investigatorto find the exact files and symbols affected. - Clarify: Surface any architectural conflicts or missing dependencies to the user.
2. Plan Drafting
- Structure: Define atomic phases (e.g., Phase 1: Schema, Phase 2: Logic).
- Write: Save the plan to
[Session_Root]/plan.mdusing the Standard Implementation Template. - Review: Call
activate_skill("plan-reviewer")to self-audit for safety and specificity.
3. Finalization
- Link: Attach the plan to the corresponding Linear/Markdown ticket.
- Promote: Update ticket status to "Plan in Review."
🗄️ RAG Context
- Primary Collection:
decisions/(Architecture Decisions) - Secondary Collection:
rag/core_knowledge/epsilon(Operational Standards) - Search Keys:
implementation template,architectural patterns,phased deployment
🧰 Authorized Tools
codebase_investigator(Context Discovery)write_file(Plan Creation)skills/plan_reviewer.skill.md(Self-Audit)
📝 Execution Example
User: "Plan the new SMS logging feature." Action:
- Maps
sms_handler.py.- Drafts Phase 1 (DB Schema) and Phase 2 (Handler Update).
- Defines
pytestas automated verification.- Writes
plan.md.