Research to Requirements Prompt Template

Use this prompt to convert deep research into an Orchestre-ready requirements.md file.

---

The Prompt

I have conducted deep research for a new software project and need to convert it into a comprehensive requirements.md file for Orchestre MCP to create a development plan. Please transform my research into a structured requirements document following this exact format:

1. PROJECT VISION

Project Name: [Extract from research]
One-line description: [Concise value proposition]
Target users: [Primary and secondary personas]
Core problem being solved: [Clear problem statement]
Success metrics: [Measurable outcomes]

2. TECHNICAL DECISIONS

Based on the research, document each technology choice:

Frontend:
- Framework: [e.g., Next.js 14]
- Rationale: [Why this choice based on research]
- Key libraries: [List with specific versions if mentioned]

Backend:
- Framework: [e.g., Node.js with Express]
- Rationale: [Research-backed reasoning]
- Database: [Type and specific product]
- Why: [Justification from research]

Infrastructure:
- Deployment: [Platform choice]
- Rationale: [Cost/scale/complexity reasoning]
- CDN/Edge: [If applicable]

3. CORE FEATURES

List features with implementation priorities:

Phase 1 (MVP - X weeks):
1. [Feature]: [Description, acceptance criteria]
2. [Feature]: [Description, acceptance criteria]

Phase 2 (Enhancement - X weeks):
1. [Feature]: [Description, acceptance criteria]

Phase 3 (Scale - X weeks):
1. [Feature]: [Description, acceptance criteria]

4. ARCHITECTURE REQUIREMENTS

Architecture pattern: [e.g., Microservices, Monolith, Serverless]
Why: [Research justification]

Data flow:
- [Component A] -> [Component B]: [What data, why]
- Real-time requirements: [WebSockets, SSE, polling?]
- Caching strategy: [Where, what, TTL]

API Design:
- Style: [REST, GraphQL, tRPC]
- Authentication: [Method and provider]
- Rate limiting: [Requirements]

5. INTEGRATIONS

Third-party services:
- [Service name]: [Purpose, API version, critical features needed]
- [Service name]: [Purpose, specific SDK version]

External APIs:
- [API name]: [Use case, rate limits, data needs]

6. PERFORMANCE REQUIREMENTS

Response times:
- Page load: [Target metric]
- API responses: [Target metric]
- Real-time updates: [Latency tolerance]

Scale targets:
- Concurrent users: [Number]
- Data volume: [Size/growth rate]
- Geographic distribution: [Regions]

7. SECURITY REQUIREMENTS

Authentication: [Requirements from research]
Authorization: [Role/permission model]
Data protection: [Encryption, PII handling]
Compliance: [GDPR, HIPAA, SOC2, etc.]
Security headers: [CSP, CORS policies]

8. DEVELOPMENT CONSTRAINTS

Team size: [Number of developers]
Timeline: [Hard deadline or flexible]
Budget constraints: [Infrastructure costs, service limits]
Technical constraints: [Browser support, device targets]
Regulatory: [Industry-specific requirements]

9. QUALITY REQUIREMENTS

Testing:
- Unit test coverage: [Target %]
- E2E test scenarios: [Critical paths]
- Performance testing: [Load test requirements]

Monitoring:
- APM: [Tool preference]
- Error tracking: [Tool preference]
- Analytics: [Business metrics to track]

10. SPECIAL CONSIDERATIONS

[Any unique requirements from research]
[Industry-specific needs]
[Innovation opportunities identified]
[Risk factors to mitigate]

11. ORCHESTRATION HINTS

Suggested Orchestre template: [makerkit/cloudflare/react-native]
Parallel work opportunities: [What can be built simultaneously]
Complex features needing special attention: [List]
Recommended review points: [Critical integration moments]

---

MY RESEARCH RESULTS:

[Paste your research here]

---

Please create a complete requirements.md file that Orchestre can use to generate an optimal development plan. Be specific about versions, include all technical decisions from the research, and ensure every requirement is actionable.

---

Usage Instructions

1. Gather your research: Compile all research from AI agents, technical discussions, or analysis tools
2. Include everything: Architecture diagrams, API documentation, competitor analysis, technical constraints
3. Paste into prompt: Add your research where indicated
4. Review output: Ensure all critical decisions are captured
5. Use with Orchestre:

   # Save the output as requirements.md
   /analyze-project requirements.md
   /generate-plan

Tips for Best Results

• Be specific: Include version numbers, specific products (not just "database")
• Include rationale: Orchestre plans better when it understands "why"
• Mention tradeoffs: If research identified alternatives, include them
• Add constraints early: Budget, time, and team limits shape the plan
• Think in phases: Help Orchestre create incremental delivery plans

Example Research Formats That Work Well

1. Structured reports: Technical feasibility studies
2. Conversation logs: AI agent discussions about architecture
3. Comparison matrices: Technology evaluation spreadsheets
4. Requirement lists: Business requirement documents
5. Technical specs: API documentation, data models
6. Competitive analysis: Feature comparisons, market research

Enhancing the Output

After generating requirements.md, consider:

1. Adding diagrams using mermaid syntax
2. Including code examples for complex integrations
3. Linking to specific documentation
4. Adding acceptance criteria for features
5. Including performance benchmarks from research