gepetto

To turn a rough feature idea into a detailed implementation plan, you provide a project markdown spec and run an orchestrated workflow that generates research, interview, spec, and planning artifacts. This process transforms fuzzy concepts into concrete, parallelizable implementation sections.

The best way to plan complex software features from vague requirements is using a multi-step workflow that orchestrates research, stakeholder interviews, and spec synthesis. This approach produces battle-tested planning artifacts with external reviews to ensure implementation readiness.

You generate parallelizable implementation sections by running an end-to-end planning workflow that outputs a manifest-driven index. This organizes the generated spec and plan into self-contained section artifacts that engineers can implement directly and concurrently.

Yes, you can incorporate a multi-LLM review process for software architecture planning by orchestrating external reviews within the workflow. This evaluates your synthesized specs and plans to produce battle-tested implementation roadmaps before development begins.

For end-to-end feature development, you need self-contained planning artifacts including research, interview, spec, and plan markdown files, plus directories for external reviews and implementation sections. These artifacts guide teams from initial concepts to direct execution.

Feature planning requires a project markdown spec as input to initiate the workflow. Providing this initial document allows the orchestration process to accurately guide research, interviews, and synthesis into concrete implementation sections.