writing-project-plan

To create an implementation plan from a feature spec, provide the feature name to generate a task-by-task breakdown detailing files to modify, code structure, testing strategy, and cross-functional responsibilities.

Work breakdown structure in project management decomposes broad requirements into actionable, granular tasks. This skill generates structured task decomposition with clear ownership, milestones, and documentation across engineering, design, and QA.

Writing an execution-ready project plan involves detailing every step from initial setup to verification. This skill produces comprehensive plans including file templates, risk notes, rollback steps, and commit guidance for development teams.

Yes, you can use this for cross-functional product development planning. It aligns product, design, and QA activities by detailing specific responsibilities and milestones to ensure collaborators know exactly what to build and how to verify success.

The best way to document task decomposition for a new requirement is to generate promotion-ready documentation that includes complete development plans, testing strategies, and step-by-step implementation guidance with clear task granularity.

No specific dependencies are required to generate feature planning documentation. You simply provide a feature name or requirement spec, and the skill outputs the comprehensive implementation plan without needing external components.