Skip to main content

​
📄 Planning Documents - The Foundation of Success

Use these templates as your starting point, customizing based on your discovery phase findings

​
🏗️ Master Prompt Template

ultrathink and create a comprehensive project structure for [PROJECT NAME]

Project Type: [Based on discovery: SaaS, E-commerce, Dashboard, Internal Tool]
Target Users: [From discovery phase analysis]

EXPLICIT TECH STACK (DO NOT DEVIATE):
Frontend:
- Next.js 14 (app router, not pages)
- TypeScript with strict mode
- Tailwind CSS + shadcn/ui components
- [If needed] heroui for data tables
- [If needed] aceternity for animations
- State: Zustand for client, React Query for server
- Forms: react-hook-form + zod validation

Backend:
- [From discovery] Supabase/Firebase/Custom API
- [If CMS needed] Strapi/Sanity/Contentful
- Edge Functions for serverless compute
- [From discovery] Authentication method

AI Integration (if applicable):
- LangChain for orchestration
- LangGraph for stateful workflows
- Vector DB: Supabase pgvector

Deployment:
- Frontend: Vercel
- Backend: [From discovery] Supabase/Railway/Cloud Run
- CI/CD: GitHub Actions

REQUIREMENTS FROM DISCOVERY:
1. [Specific requirement from discovery phase]
2. [Another requirement]
3. Create claude.md with project overview
4. Create plan.md with phased implementation
5. Each phase independently testable
6. Use battle-tested OSS libraries
7. Include comprehensive error handling
8. [RTL support if needed from discovery]
9. [Admin panel if needed]
10. [CMS integration if needed]

DESIGN SYSTEM (FROM DISCOVERY):
- Brand Colors: [From brand guidelines]
- Typography: [From brand guidelines]
- Style: [From moodboard]
- Components: [From UI research]
- Responsive: Mobile-first (320px min)
- RTL Support: [Yes/No based on discovery]
- Accessibility: WCAG 2.1 [AA/AAA]

USER FLOWS (FROM DISCOVERY):
1. [Primary user flow]
2. [Secondary user flow]
3. [Admin flow if applicable]

Start by creating the planning documents incorporating all discovery findings.

​
📄 Planning Documents (Enhanced)

Comprehensive Project Configuration

This template incorporates all findings from your discovery phase
# Project: [Project Name]

## Executive Summary
[2-3 sentences from discovery phase findings]

## Discovery Phase Summary
- Platform Type: [Public/Private/Internal]
- Target Market: [Geographic/Demographic]
- Scale Expectations: [User numbers, data volume]
- Compliance Requirements: [GDPR/HIPAA/etc]

## Target Users & Use Cases
- Primary: [From discovery user research]
- Secondary: [From discovery]
- Key Use Cases:
  1. [From user journey mapping]
  2. [From user journey mapping]

## Tech Stack (EXPLICIT - LOCKED FROM DISCOVERY)

### Frontend
- Framework: Next.js 14.x (app router)
- Language: TypeScript 5.x (strict)
- Styling: Tailwind CSS 3.x + shadcn/ui
- State: Zustand + React Query
- Forms: react-hook-form + zod
- Testing: Vitest + Playwright
- [Additional from discovery]

### Backend
- Platform: [From technical discovery]
- API: [REST/GraphQL/tRPC based on needs]
- Database: [From data requirements]
- Auth: [From user management discovery]
- CMS: [If needed from content discovery]
- Testing: Jest + Supertest

### Infrastructure
- Hosting: [From performance requirements]
- CDN: [Based on geographic needs]
- Monitoring: Sentry + [Analytics choice]
- CI/CD: GitHub Actions

## Design System (FROM BRAND GUIDELINES)
- Colors: [Exact hex values from discovery]
- Typography: [Font families from brand]
- Spacing: [Grid system from design tokens]
- Components: [Component library choices]
- Style: [From moodboard research]
- RTL: [Required/Optional from discovery]
- Mobile First: 320px minimum

## User Management (FROM DISCOVERY)
- Authentication: [Methods from discovery]
- Roles: [From permission matrix]
- Permissions: [Granular permissions]
- Data Privacy: [GDPR compliance needs]

## Content Management (FROM DISCOVERY)
- CMS Type: [Headless/Traditional/None]
- Editors: [Who edits content]
- Workflow: [Publishing workflow]
- Localization: [Language requirements]

## Constraints & Guidelines
1. [From discovery phase]
2. Performance budget: [From technical discovery]
3. Browser support: [From audience analysis]
4. Accessibility: [WCAG level from discovery]
5. Security: [Compliance requirements]
6. SEO: [If public platform]
7. Analytics: [KPI tracking needs]

## Success Metrics (FROM BUSINESS REQUIREMENTS)
- Technical:
  - [From performance budget]
  - [From scaling requirements]
- Business:
  - [From stakeholder interviews]
  - [From KPI definitions]

## Development Principles
1. Ship small, ship often
2. Test critical paths (from user journey)
3. Document decisions, not code
4. Follow design system strictly
5. Accessibility-first development

Next Step

With planning documents ready, proceed to frontend implementation patterns →