writing-plans

To create an implementation plan with zero codebase context, define your tasks and project structure through guided prompts, which then generates a step-by-step document detailing every necessary instruction for engineers to follow.

The best way to break down software development tasks is to divide them into manageable, 2-5 minute steps, ensuring efficient progress and providing clear instructions for engineers starting with no prior context.

Yes, you can use this for full-stack project structures and backend planning, as it provides standard templates to guide the step-by-step setup and task generation for various project types.

Yes, the generated project plan follows a specific output naming convention to ensure consistent and easily identifiable output files across your software development workflow.

To manage task breakdown for codebase onboarding, the system guides you step-by-step through defining tasks and setting up project structures, documenting every necessary action into a comprehensive plan.

A limitation of generating implementation plans without codebase context is that you must strictly adhere to a specific naming convention and task breakdown format, requiring precise input to yield accurate step-by-step instructions.