Specs (Architect)
Architect API
Generate software specifications with Markdown, structured JSON, architecture graphs, and implementation estimates.
The Architect API turns a project description into an implementation plan. Choose Fast Spec for milestones and stories, or Deep Spec for a more detailed breakdown with subtasks. Both accept existing codebase context and reference documentation.
Generate your first spec
Submit a request, poll its status, and read the completed artifacts.
Use it from an assistant
Connect fast_spec and deep_spec through the pre.dev MCP server.
From request to artifacts
Send your requirements, optional codebase context, and any reference files or documentation URLs. The completed result offers the same plan in formats suited to different readers.
The coding-agent variant focuses on requirements and implementation structure. The human variant adds personas, roles, and effort estimates. Graphs, an architecture infographic, and documentation archives are returned when available; integrations should tolerate absent optional artifacts.
Choose the depth
| Fast Spec | Deep Spec | |
|---|---|---|
| Structure | Milestones and user stories | Milestones, stories, and subtasks |
| Starting point | Early planning and straightforward features | Detailed implementation planning |
| Typical generation time | About 1 minute | About 3–5 minutes |
| Typical credits | About 5–10 | About 10–50 |
Times and credit usage are estimates, not fixed limits or quotes. Use the returned creditsUsed for actual consumption. See plans and credits for access, and Fast vs Deep for planning guidance.
Read next
- Inputs and outputs: files, context, documentation, and graph data.
- Status and results: polling and failure handling.
- Project plan: what is built, what works, what is left, and where it lives in the code.
- List or search: retrieve existing work.
- Python and Node: official SDKs.