Workflow: Generating Specs
Use AI agents to generate comprehensive implementation specs from an overview, existing codebase, or live website. Multiple agents can contribute different perspectives — architecture, security, market research — all tracked and attributable.
Getting Started
After creating a project and writing your overview, open the prompt library (sparkle icon in the editor toolbar) and select the Generate tab. Three built-in prompts are available:
- Spec from Overview—You write the overview first, the agent generates functional requirements, UI layout, data model, API spec, and tech stack.
- Spec from Codebase—Agent reads your codebase and reverse-engineers a full specification from the existing code.
- Spec from Website—Agent crawls public pages of a live website and creates an overview, functional requirements, and UI layout.
Multi-Agent Review Strategy
Different AI models have different strengths. Use them together for better specs:
Sequential Review
Generate with one agent (e.g., Claude Opus for deep architecture), then have a second agent (e.g., Claude Sonnet) review via proposals. The proposal system tracks each agent's suggested changes as diffs you can accept or reject.
Specialized Passes
After initial generation, connect different agents for focused reviews: a security-focused LLM to audit the auth section, a market research agent to validate the functional requirements, or a performance specialist to review the data model.
Section Templates
When creating a project, you can choose from pre-built section templates that scaffold the right structure for your use case:
- Full Spec — Overview, Functional Requirements, Layout & UI, Database Model, API Spec, Tech Stack
- Migration — Overview, Current System Analysis, Functional Requirements, Layout & UI, Migration Plan
- Inspiration — Overview, Reference Analysis, Functional Requirements, Layout & UI
- Blank — Start empty, create sections as needed
Custom Prompt Templates
Create your own prompt templates in Settings. Custom templates appear in the prompt library alongside system templates. Use {project_name} and {section_name} as variables that get auto-substituted when copying.