vibe-coding-project-plan

To generate a development plan, this Skill reads and interprets your requirements.md file, inspects existing code for implementation gaps, and outputs a structured plan.md detailing project scope, phases, and file changes.

Transitioning requirements into implementation steps involves analyzing your requirements.md to identify codebase gaps, then creating a comprehensive plan.md that outlines development phases, necessary file modifications, and open questions before coding begins.

This project planning approach works with existing codebases by inspecting current code to identify implementation gaps against your requirements. It updates or creates a plan.md to bridge the gap between current state and required features.

To outline scope and file changes before Vibe Coding, the Skill analyzes your requirements file and existing project structure, producing a plan.md that defines the development boundaries, sequential phases, and specific files needing modification.

You need to create a project plan when your project is ready to transition from defining requirements in requirements.md to actual implementation, ensuring you have a structured roadmap of phases and file changes before development begins.

Automating a Vibe Coding project plan requires a pre-existing requirements.md file to function. It relies on analyzing your current codebase and requirements, so incomplete requirement definitions will result in a less comprehensive plan.md output.