implementation-plan

To generate an implementation plan from a PRD, you provide the PRD and tech-stack context to automate the creation of a structured plan. This process breaks down features into actionable stories with specific tasks and acceptance criteria.

Breaking down project features into actionable stories involves dividing the main requirements into small, implementable units. Each generated story includes specific tasks and acceptance criteria to ensure all development aspects are considered.

The best way to track progress during feature implementation is to generate a dedicated progress tracking file. This empty tracker is created alongside the implementation plan to monitor development status continuously.

Yes, you need tech-stack context to create a detailed implementation plan effectively. The skill requires both the PRD and the tech-stack context to function properly and generate accurate stories with tasks and acceptance criteria.

Yes, you can automate task breakdown for a new software feature by running the plan generation. It automatically creates a structured implementation roadmap, ensuring all aspects of the feature are divided into implementable stories.

An automated implementation plan includes a structured roadmap of tasks, detailed stories with acceptance criteria, and an empty progress tracker. It provides a clear development path based on your project requirements and tech stack.