Verified:GitHub

implementation-plan-writer

Converts requirements and architecture decisions into ordered implementation plans with dependencies and validation gates.

Updated Jul 7, 2026

Search Tags:#planning #requirements #validation #dependencies #task breakdown #implementation plan #sequencing

Ready to run

npx skills add https://github.com/vmitsaras/Agent-Skills --skill implementation-plan-writer-vmitsaras

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-plan-writer
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/project-planning/implementation-plan-writer
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill implementation-plan-writer-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD, technical design, or architecture decision into an executable sequence of tasks is error-prone: dependencies get missed, validation is bolted on at the end, and coding agents or teams receive ambiguous handoffs. This Skill produces a dependency-ordered implementation plan without writing any code. ## Core Features & Use Cases - Dependency-Ordered Task Breakdown: Sequences work from prerequisites through data contracts, core logic, UI, testing, rollout, and cleanup, with each step carrying goals, dependencies, and acceptance criteria. - Risk and Validation Planning: Surfaces assumptions, open questions, migration risks, rollback steps, and integrates testing checkpoints into the sequence rather than as a final afterthought. - Use Case: You have an architecture decision record and a feature brief for a new API integration. Provide them to the Skill and receive a structured plan with a critical path, parallelizable work, risk mitigations, and immediate next actions ready to hand to a coding agent. ## Quick Start Turn these requirements and architecture notes into an ordered implementation plan without writing any code.

Frequently Asked Questions about implementation-plan-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn requirements into an implementation plan?▼

Provide your requirements, PRD, architecture decisions, or feature brief and ask for an implementation plan. The Skill extracts functional behavior and constraints, then sequences tasks by dependency with goals, deliverables, and acceptance criteria for each step.

How to break a technical design into tasks for a coding agent?▼

Hand the design document to the Skill and request an execution plan for an agent. It produces ordered work packages with explicit dependencies, validation gates, ownership boundaries, and immediate next actions an agent can start from safely.

Does the implementation plan include actual code?▼

No, the output is a planning artifact only. The Skill deliberately avoids writing code, diffs, or snippets, describing intended edits at the task level unless you separately request implementation after the plan is complete.

When should I not use an implementation plan writer?▼

Avoid it when you need immediate code changes, a high-level roadmap rather than implementation steps, or a reconciliation of an existing plan against repository progress. It also requires requirements clear enough to sequence or permission to state assumptions.

How does the plan handle risky database migrations?▼

Risky migrations get dedicated steps including backup, rollback, dry-run, and verification checkpoints. The Skill places data model and contract changes before dependent features and flags migration risks in a dedicated risks and mitigations table.