Skip to main content
The Agent Action Plan (AAP) is the blueprint Blitzy follows during code generation. What the AAP says is what the code does. Review it carefully.
After you submit a generation prompt, Blitzy produces an AAP - a structured breakdown of every file change, dependency, and design decision it will execute. Review this plan before approving it for code generation. An incomplete AAP produces incomplete code. Fix issues here, not after generation.
Jump to: What to Review | How to Refine | Decision Framework

​
What to Review

Check each AAP section for real content. Placeholders like “TBD” or “To be determined” are not acceptable.
  • Clear statement of what will be built or changed, and why
  • Matches your original prompt intent without reinterpreting scope
  • No ambiguity about the expected outcome
  • Accurately reflects the current state of your codebase
  • References the correct existing files, modules, and patterns
  • Identifies constraints and dependencies that affect implementation
  • Technical approach and architecture decisions are explicit
  • Specifies methods, libraries, and patterns by name
  • Consistent with your development guide and existing architecture
  • Every file to be created or modified is listed with specific changes
  • Logic and behavior changes are described, not just structural changes
  • Edge cases and error handling are addressed
  • External libraries, APIs, and internal modules are identified
  • Version constraints are specified where relevant
  • No surprise dependencies that were not in your prompt
  • In-scope and out-of-scope items are explicitly listed
  • Matches the scope you intended, nothing silently added or dropped
  • Preservation requirements for existing code are stated
  • Critical constraints and non-negotiable requirements are captured
  • Project-specific conventions or restrictions are reflected
  • Every directive from your prompt is present and unweakened
  • The intent of every custom rule you added appears in the AAP (Blitzy paraphrases rules, so check for intent, not exact wording)
  • Blitzy may also surface rules it inferred from your codebase - review these alongside your explicit rules
  • No custom rules were omitted entirely
A rule may be absent from the AAP if it conflicts with another rule, contradicts a codebase convention, or overlaps with an existing requirement. This is expected, not a bug. Compare your project’s rules list on the platform against the AAP. If a rule was dropped and you still need it, add it back through prompt refinement or inline editing before approving.

​
How to Refine

If the AAP needs changes, choose a refinement path based on the scope of the problem.
Best for - Broad changes, missing sections, or when multiple sections need rework.Update your generation prompt to address the gaps, then regenerate the AAP. The entire plan is rebuilt from scratch.An LLM can help you revise the prompt. Feed it your original prompt and describe what the AAP got wrong:

​
Decision Framework

Golden Rules

Best practices for writing precise prompts

Project Guide Review

Next step after AAP approval and code generation

Generation Prompts

Write generation prompts for Blitzy