spec-implementation-plan

What it does

This skill generates a structured implementation plan for software specifications, breaking down requirements into actionable steps. It helps translate high-level design documents or feature requests into a clear roadmap for development teams.

When to use it

• You have a product requirement document (PRD) and need to outline the technical approach before coding begins.
• A stakeholder provides a vague feature request, and you need to define specific milestones and deliverables.
• You are refactoring legacy code and require a phased plan to migrate functionality without disrupting services.
• You want to ensure all edge cases and dependencies identified in a spec are addressed before sprint planning.

Key capabilities

• Parses input specifications or requirements documents to extract core logic and constraints.
• Organizes tasks into logical phases, such as architecture design, development, testing, and deployment.
• Identifies potential risks or missing information within the provided specification.
• Formats output as a readable list of steps suitable for project management tools.

Example prompts

• "Here is our API specification for user authentication: [paste spec]. Create an implementation plan covering database schema changes, endpoint logic, and security testing."
• "I need to migrate our monolithic checkout flow to microservices based on this diagram: [insert image or description]. Outline a step-by-step rollout strategy."
• "Generate a detailed implementation checklist for adding real-time notifications to our mobile app, including backend WebSocket setup and frontend integration."

Tips & gotchas

• The quality of the plan depends heavily on the clarity of your input; provide as much context about constraints (e.g., budget, timeline, tech stack) as possible.
• This tool generates a roadmap, not executable code; you will still need to write the actual implementation logic and perform manual code reviews.