planning-faber-orchestration

To create an implementation plan for agent execution, you synthesize product requirements, technical discovery, and codebase analysis into an agent-executable PLAN.md. This blueprint defines specific file paths, function signatures, and data shapes for the agent to follow.

An agent-executable implementation blueprint is a PLAN.md file detailing exact file modifications, function signatures, and sequencing. It bridges high-level ideas and concrete steps by providing the precise context an autonomous agent needs to write code.

To synthesize PRDs and codebase analysis into actionable steps, integrate the product requirements with an investigation of the existing code. This identifies relevant patterns and produces a detailed plan specifying which files to modify and the order of operations.

Feature planning for agents requires specific file paths and function signatures to ensure precise execution. Addressing this need for detailed, actionable blueprints prevents ambiguity by defining exact data shapes and sequencing for the agent.

You need a PLAN.md for complex software feature development when bridging the gap between high-level ideas and concrete implementation steps. It is required when you have a new feature requirement and must produce specific, actionable blueprints for agentic execution.