Do Spec Plan

Analyze and think hard about the spec: $ARGUMENTS

chrbradley updated 1y ago
Claude CodeGeneric
View source ↗
Analyze and think hard about the spec: $ARGUMENTS

Draft a detailed, step-by-step blueprint for building this project.
Once you have a solid plan, break it down into small, iterative chunks that build on each other.

Look at these chunks and then go another round to break them into small steps. Review the results and make sure that the steps are small enough to be implemented safely with strong testing, but big enough to move the project forward.
Iterate until you feel that the steps are right sized for this project.

From here you should have the foundation to provide a series of prompts for a code-generation LLM that will implement each step in a test-driven manner. Prioritize best practices, incremental progress, and early testing, ensuring no big jumps in complexity at any stage. Make sure that each prompt builds on the previous prompts, and ends with wiring things together. There should be no hanging or orphaned code that isn't integrated into a previous step.

Make sure and separate each prompt section. Use markdown. Each prompt should be tagged as text using code tags. The goal is to output prompts, but context, etc is important as well.

Store the plan in the @.claude-plan folder. Give it a name that clearly indicates which spec file it was generated from.

Maintain Do Spec Plan?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[Do Spec Plan on getagentictools](https://getagentictools.com/loops/chrbradley-do-spec-plan?ref=badge)
npx agentictools info loops/chrbradley-do-spec-plan

The second line is the CLI lookup for this page — handy in READMEs and docs.