Skip to content

/generate-implementation-tutorial - Reference-Based Implementation Tutorial Generator

Purpose

The /generate-implementation-tutorial prompt creates an intelligent implementation guide that references existing documentation rather than duplicating it. It generates a comprehensive tutorial that serves as a navigation roadmap through your project's documentation, pointing to specific sections and files for each implementation step.

How It Actually Works

  1. Deep Requirement Analysis: Parses explicit and implicit requirements from your description
  2. Context Discovery:
    • Checks for existing requirement documents
    • Looks for .orchestre/commands-index.md for available commands
    • Maps documentation structure and quality
    • Builds documentation dependency graph
  3. Reference-Based Planning: Creates a tutorial that points to specific documentation sections
  4. Command Sequencing: Only references commands that actually exist in your project

Key Innovation

NOT a content repository: The implementation tutorial doesn't embed large code blocks or duplicate specifications. Instead, it creates an intelligent execution guide that tells you exactly which documentation to read at each step.

Use Cases

  1. Full Application Development: Navigate complex documentation for complete platforms
  2. Enterprise Applications: Orchestrate multi-tier system development
  3. Documentation-Rich Projects: Leverage existing specifications effectively
  4. Team Alignment: Create navigation guides through project knowledge
  5. Complex Implementations: Break down into documentation-referenced steps

Argument Structure

/generate-implementation-tutorial <project-description> [scale-target] [--options]

Arguments

  1. project-description (required)

    • Comprehensive project vision
    • Target audience and use cases
    • Core features and capabilities
    • Project goals and objectives
  2. scale-target (optional)

    • Expected user base size
    • Transaction volume
    • Geographic distribution
    • Growth projections
  3. options (optional)

    • --compliance: Required compliance (GDPR, HIPAA, SOC2)
    • --integrations: Essential third-party services
    • --team-size: Development team size

Examples

bash
# Standard application
/generate-implementation-tutorial "B2B analytics platform for e-commerce stores"

# With scale considerations
/generate-implementation-tutorial "Global learning management system" "1M users, 50k concurrent"

# With compliance requirements
/generate-implementation-tutorial "Healthcare data platform" --compliance="HIPAA,GDPR"

# Full specification
/generate-implementation-tutorial "Financial planning application" "100k users" --compliance="SOC2"

Adaptation Strategies

Comprehensive Analysis

The prompt performs:

  1. Market Analysis

    • Competitor evaluation
    • Feature differentiation
    • Pricing model optimization
    • Growth strategy alignment
  2. Technical Architecture

    • System design
    • Service boundaries
    • Data architecture
    • Infrastructure planning
  3. Scale Planning

    • Performance requirements
    • Capacity planning
    • Cost optimization
    • Geographic distribution
  4. Security Design

    • Threat modeling
    • Compliance mapping
    • Access control design
    • Data protection strategy

Blueprint Generation

Creates detailed tutorials for:

  • System architecture
  • Database design
  • API specification
  • Security framework
  • DevOps pipeline
  • Monitoring strategy

Phased Implementation

Develops roadmap with:

  • Foundation phase
  • Core features phase
  • Scale preparation
  • Enterprise features
  • Global expansion

Documentation Discovery Phase

The prompt performs comprehensive discovery before generating the tutorial:

1. Command Index Check

  • Looks for .orchestre/commands-index.md first (saves context)
  • Falls back to listing .claude/commands/ if no index
  • Maps available commands with exact syntax
  • Only references commands that actually exist

2. Documentation Architecture Discovery

  • Lists all documentation files in project_docs/
  • Assesses documentation quality and completeness
  • Calculates specs-to-explanation ratio (aims for 70%+ specs)
  • Builds documentation dependency graph

3. Error Handling

If documentation is missing or incomplete:

⚠️ Reference-based implementation tutorial requires comprehensive documentation.

Documentation check results:
- project_docs/ directory: [exists/missing]
- Key specification files: [list]
- Coverage assessment: [complete/partial/minimal]

Would you like me to:
A) List needed documentation
B) Generate traditional embedded tutorial
C) Create hybrid tutorial with discovery steps

Memory Usage

Generated Structure

project-blueprint/
├── CLAUDE.md                    # Project vision document
├── .orchestre/
│   ├── tutorials/
│   │   └── implementation-tutorial.md  # Reference-based implementation guide
│   └── documentation-map.md          # Documentation structure and dependencies

Implementation Tutorial Document Structure

markdown
# Implementation Tutorial: {{projectName}}

**Generated by Orchestre**: {{timestamp}}
**Based on requirements**: "{{projectRequirements}}"

## Progress Tracker
- [ ] Phase 1: Foundation (0/5 steps)
- [ ] Phase 2: Core Features (0/8 steps)  
- [ ] Phase 3: Advanced Features (0/6 steps)
- [ ] Phase 4: Production Readiness (0/4 steps)

## Part 1: Philosophy & Architecture
[Project-specific principles and decisions]

## Part 2: Step-by-Step Implementation

### Phase 1: Foundation Setup

#### Step 1.1: Project Initialization
**Documentation**: 
- Primary: `project_docs/setup-guide.md` sections 1.1-1.3
- Supporting: `CLAUDE.md` for project context

**Your Prompt**:

/create


**Expected Outcome**: Working development environment
**Validation**: Run `npm dev` successfully

#### Step 1.2: Database Setup
**Documentation**:
- Primary: `project_docs/database-schema.md` section 2
- Reference: `security-model.md` for RLS policies

[Continue with reference-based steps...]

## Part 3: Validation Checklists
[Specific validation steps with doc references]

## Part 4: Documentation Map
- Database specs: `database-schema.md` sections 1-4
- UI/UX specs: `ui-architecture.md` sections 2-3
- Agent configs: `agent-config.md` complete
- Integration details: `integration-specs.md` section 5
- Advanced filtering
- Export capabilities

### Phase 4: Scale & Polish (Weeks 21-24)
- Performance optimization
- Security hardening
- Documentation
- Launch preparation

Workflow Examples

Enterprise Application Development

bash
# 1. Generate implementation tutorial
/generate-implementation-tutorial "CRM for healthcare providers" --compliance="HIPAA"

# 2. Review and refine
/orchestrate "Refine CRM architecture for regional data residency"

# 3. Begin implementation
/execute-task "Implement Phase 1: HIPAA-compliant infrastructure"

# 4. Add enterprise features
/add-enterprise-feature "advanced-audit-logs" "HIPAA compliance tracking"

Platform Migration Planning

bash
# 1. Create migration blueprint
/generate-implementation-tutorial "Modernize legacy ERP to cloud-native architecture" "50k users"

# 2. Analyze current system
/discover-context ./legacy-system

# 3. Plan migration phases
/execute-task "Create detailed data migration strategy"

Startup to Scale Journey

bash
# 1. Start with comprehensive tutorial
/generate-implementation-tutorial "AI-powered code review platform" "grow to 100k users"

# 2. Build MVP from tutorial
/compose-saas-mvp "Code review platform with basic AI features"

# 3. Scale following blueprint
/execute-task "Implement Phase 2: Advanced AI analysis features"

Intelligent Features

Architecture Decisions

Documents key decisions:

  • Technology choices with rationale
  • Trade-offs considered
  • Alternative approaches
  • Future migration paths
  • Cost implications

Scalability Planning

Addresses scale from day one:

  • Database sharding strategy
  • Caching architecture
  • CDN implementation
  • Service mesh design
  • Auto-scaling policies

Security Framework

Comprehensive security design:

  • Zero-trust architecture
  • Encryption strategy
  • Access control matrix
  • Compliance mappings
  • Incident response tutorial

Cost Optimization

Built-in cost awareness:

  • Resource utilization planning
  • Multi-region strategy
  • Reserved capacity planning
  • Cost monitoring setup
  • Optimization opportunities

Generated Artifacts

1. Technical Specifications

  • API documentation (OpenAPI)
  • Database schema (ERD)
  • Service contracts
  • Event schemas
  • Error catalogs

2. Architecture Diagrams

  • System overview
  • Service dependencies
  • Data flow diagrams
  • Deployment topology
  • Security boundaries

3. Implementation Guides

  • Service templates
  • Coding standards
  • Testing strategies
  • Deployment procedures
  • Monitoring setup

4. Operational Runbooks

  • Deployment checklist
  • Monitoring alerts
  • Incident response
  • Backup procedures
  • Disaster recovery

5. Team Resources

  • Onboarding guides
  • Architecture decisions
  • Best practices
  • Knowledge base
  • Training materials

Blueprint Variations

Multi-Region Platform

bash
/generate-implementation-tutorial "Global video platform" "10M users across 5 regions"

Includes:

  • Geographic distribution
  • Data residency compliance
  • Edge optimization
  • Regional failover
  • Latency optimization

AI-Powered Application

bash
/generate-implementation-tutorial "AI sales assistant platform" --integrations="openai,anthropic"

Includes:

  • ML pipeline architecture
  • Model versioning
  • Training infrastructure
  • Inference optimization
  • Feedback loops

Marketplace Platform

bash
/generate-implementation-tutorial "B2B software marketplace" "1000 vendors, 100k buyers"

Includes:

  • Multi-sided architecture
  • Payment splitting
  • Review & rating system
  • Search infrastructure
  • Vendor management

Integration Points

With Other Prompts

  • ← /orchestrate: Refine initial analysis
  • → /execute-task: Implement phases
  • → /add-enterprise-feature: Add capabilities
  • → /security-audit: Validate security

With Development Process

  • Integrates with Agile/Scrum
  • Supports GitOps workflows
  • Enables Infrastructure as Code
  • Facilitates continuous delivery

Best Practices

  1. Comprehensive Vision

    bash
    # Good: Complete picture
    /generate-implementation-tutorial "B2B procurement platform with supplier network, 
    RFQ management, and spend analytics" "Fortune 500 customers"
    
    # Limited: Too narrow
    /generate-implementation-tutorial "Procurement tool"
  2. Realistic Planning

    bash
    # Good: Phased approach
    /generate-implementation-tutorial "Video streaming platform" "Start with 10k, 
    scale to 1M users"
    
    # Unrealistic: No growth path
    /generate-implementation-tutorial "Netflix competitor" "1B users day one"
  3. Technical Depth

    bash
    # Good: Specific requirements
    /generate-implementation-tutorial "IoT data platform" --integrations="mqtt,aws-iot"
    --compliance="ISO-27001"
    
    # Vague: No specifics
    /generate-implementation-tutorial "IoT platform"

Advanced Planning

Compliance-First Design

bash
/generate-implementation-tutorial "Financial advisory platform" --compliance="SOC2,PCI-DSS,GDPR"
# Generates architecture with compliance built into every layer

Acquisition-Ready Architecture

bash
/generate-implementation-tutorial "Platform with acquisition potential" "Clean architecture for due diligence"
# Creates well-documented, modular system ready for acquisition

Platform Ecosystem

bash
/generate-implementation-tutorial "Developer platform with marketplace" "API-first, plugin ecosystem"
# Designs extensible platform with third-party integration capabilities

Tips

  1. Think Big, Start Focused: Plan for scale but implement incrementally
  2. Document Everything: The blueprint is your north star
  3. Validate Assumptions: Test architectural decisions early
  4. Maintain Flexibility: Tutorials should adapt to learnings
  5. Involve Stakeholders: Share blueprints for alignment

Built with ❤️ for the AI Coding community, by Praney Behl