POST /deep-spec
Generate an ultra-detailed, comprehensive project specification.Overview
- Cost: 50 credits
- Use Cases: Complex systems, enterprise applications, critical projects
- Processing Time: ~2-3 minutes (sync) or instant return (async)
- Output: Exhaustive analysis, detailed architecture, comprehensive planning
Subscription Required
Deep Spec requires Solo Premium or Enterprise subscription.Endpoint
Headers
For JSON requests:Request Body
Parameters
For JSON requests:Parameter | Type | Required | Description |
---|---|---|---|
input | string | ✅ | Description of what you want to build |
outputFormat | string | ❌ | "url" (default) - returns hosted URL, or "markdown" - returns raw markdown in response |
currentContext | string | ❌ | CRITICAL: Existing project/codebase context. When provided, generates feature addition spec. When omitted, generates full new project spec with setup, deployment, docs, maintenance |
docURLs | string[] | ❌ | Optional: Array of documentation URLs that Architect will reference when generating specifications. Useful for API documentation, design systems, or existing project docs |
async | boolean | ❌ | false (default) - wait for completion, or true - return immediately with requestId for status polling |
Parameter | Type | Required | Description |
---|---|---|---|
file | File | ❌ | Optional: File to be parsed as input (e.g., existing code, documentation, requirements). Can be used alone or combined with input text |
input | string | ❌ | Optional: Additional text description when using file upload. Can be empty string if using only file |
outputFormat | string | ❌ | "url" (default) - returns hosted URL, or "markdown" - returns raw markdown in response |
docURLs | string[] | ❌ | Optional: Array of documentation URLs that Architect will reference when generating specifications. Useful for API documentation, design systems, or existing project docs |
async | boolean | ❌ | false (default) - wait for completion, or true - return immediately with requestId for status polling |
Deep Spec vs Fast Spec
Feature | Fast Spec | Deep Spec |
---|---|---|
Cost | 10 credits | 50 credits |
Processing Time | 30-40 sec | 2-3 min |
Structure | Milestones → Stories | Milestones → Stories → Subtasks |
Detail Level | Comprehensive | Ultra-detailed |
Best For | MVPs, prototypes | Enterprise, complex systems |
Feature Analysis | ✅ | ✅✅✅ |
Architecture Depth | ✅ | ✅✅✅ |
Risk Analysis | ✅ | ✅✅✅ |
User Stories | ✅ | ✅✅✅ |
Example Requests
New Enterprise Project
Complex Feature Addition
Async Processing
Example: With Documentation URLs
Example: With File Upload
Example: File Upload with Existing Context
Response
Success Response (Sync Mode)
Field | Type | Description |
---|---|---|
endpoint | string | Endpoint used: "deep_spec" |
input | string | Original input text provided |
status | string | Completion status: "completed" when successful |
success | boolean | Whether the request succeeded |
output | any | Primary output - the hosted spec URL or markdown content |
outputFormat | string | Format used: "url" or "markdown" |
outputFileUrl | string | URL where the spec file is hosted (downloadable markdown) |
executionTime | number | Processing time in milliseconds |
predevUrl | string | pre.dev project URL where you can view and edit the spec |
lovableUrl | string | Deep link to Lovable.dev with auto-submit prompt to implement the spec |
cursorUrl | string | Deep link to Cursor with prompt to download and implement the spec |
v0Url | string | Deep link to Vercel v0 with prompt to implement the spec |
boltUrl | string | Deep link to Bolt.new with prompt to implement the spec |
outputFormat: "markdown"
:
Success Response (Async Mode)
Immediate response whenasync: true
:
Field | Type | Description |
---|---|---|
specId | string | Unique ID to poll for status (use with /api/spec-status/:specId ) |
status | string | Initial status: "pending" |
Output Structure: Milestones → Stories → Subtasks
Deep Spec follows a three-level hierarchy for comprehensive implementation planning:- ✅ High-level milestones group related features
- ✅ Detailed user stories with comprehensive acceptance criteria
- ✅ Granular implementation subtasks (DB, API, Frontend, Testing, Docs)
- ✅ Subtasks categorized by layer (DB, Infra, FE, API, Backend, QA, Docs)
- ✅ Task-level complexity estimates for precise planning
What Makes Deep Spec Different
Deep Spec provides enterprise-grade analysis that goes far beyond Fast Spec:Enhanced Feature Analysis
- Detailed user journey mapping for each feature
- Comprehensive edge case analysis
- Advanced user story elaboration with detailed acceptance criteria
- Cross-feature dependency mapping
Advanced Architecture Planning
- Detailed system design diagrams (when applicable)
- Comprehensive database schema design
- Advanced security architecture planning
- Scalability modeling and capacity planning
- Performance optimization strategies
Extensive Risk Assessment
- Detailed technical risk analysis with mitigation strategies
- Comprehensive security threat modeling
- Regulatory compliance mapping (GDPR, HIPAA, SOX, etc.)
- Operational risk assessment and business continuity planning
Enterprise-Ready Planning
- Detailed implementation roadmap with critical path analysis
- Resource allocation recommendations
- Stakeholder communication strategies
- Change management planning
- Training and documentation requirements
When to Use Deep Spec
Enterprise Applications
- Healthcare platforms with regulatory requirements
- Financial systems with compliance needs
- Large-scale SaaS platforms with complex workflows
- Mission-critical internal tools
Complex System Requirements
- Multi-tenant architectures
- Real-time processing systems
- High-throughput applications
- Systems requiring 99.9%+ uptime
Large Team Coordination
- Projects with 5+ developers
- Cross-functional team collaboration
- Extended development timelines (6+ months)
- Projects requiring detailed handoffs
Code Examples
cURL - Enterprise Healthcare Platform
Python - Financial Services Platform
JavaScript - Complex SaaS Application
Deep Spec Output Structure
1. Executive Summary & Business Case
- Detailed problem statement and solution approach
- Success metrics and KPIs
- Stakeholder analysis
- High-level timeline and milestones
2. Comprehensive Feature Catalog
- Detailed feature specifications with user stories
- Complex workflow documentation
- Integration requirements mapping
- Third-party service dependencies
3. Enterprise Architecture Design
- System architecture diagrams
- Database design specifications
- API design and integration patterns
- Security architecture blueprint
4. Implementation Strategy
- Detailed development phases with dependencies
- Critical path identification
- Risk mitigation strategies
- Quality assurance approach
5. Operational Considerations
- Deployment strategy and environment planning
- Monitoring and alerting requirements
- Backup and disaster recovery planning
- Support and maintenance guidelines
Best Practices for Deep Spec
Input Quality for Complex Projects
- Detailed business requirements - Include specific compliance needs
- Technical constraints - Existing systems, performance requirements
- Scale expectations - User numbers, data volume, transaction rates
- Integration landscape - Existing tools, APIs, third-party services
Planning for Enterprise Projects
- Allocate sufficient time - Deep specs can take 2-3 minutes
- Use async mode for the best experience with complex inputs
- Review thoroughly - Deep specs contain extensive detail requiring careful review
- Share with stakeholders - Use as a comprehensive project brief
Cost Considerations
- Higher investment upfront - 50 credits vs 10 for Fast Spec
- Significant time savings downstream - Reduces costly rework and scope changes
- Better resource allocation - Clear requirements prevent over/under-engineering
Next: Check Status Endpoint
Authorizations
API key for authentication. Get your API key from https://pre.dev/projects/playground (Solo) or https://pre.dev/enterprise/dashboard?page=api (Enterprise). Use format: Bearer YOUR_API_KEY
Body
Description of what you want to build or the feature you want to add
"Build a SaaS project management tool with team collaboration and real-time updates"
Output format: 'url' returns a hosted URL (default), 'markdown' returns raw markdown content
url
, markdown
CRITICAL: Existing project/codebase context. When provided, generates feature addition spec. When omitted, generates full new project spec with setup, deployment, docs, maintenance
"Existing Next.js app with Supabase, has auth, task CRUD, team features"
Optional array of documentation URLs that Architect will reference when generating specifications
[
"https://docs.pre.dev",
"https://docs.stripe.com"
]
If true, returns immediately with requestId for status polling. If false (default), waits for completion
Response
Specification generated successfully
- Option 1
- Option 2
Which endpoint was used
fast_spec
, deep_spec
Original input text provided
Completion status
completed
Whether the request succeeded
Primary output - the hosted spec URL or markdown content
Format used
url
, markdown
URL where the spec file is hosted (downloadable markdown)
Processing time in milliseconds
pre.dev project URL where you can view and edit the spec
Deep link to Lovable.dev with auto-submit prompt to implement the spec
Deep link to Cursor with prompt to download and implement the spec
Deep link to Vercel v0 with prompt to implement the spec
Deep link to Bolt.new with prompt to implement the spec