Update documentation structure to reflect new directory organization for AI agent personas, moving all related files to docs/source/500/. Revise prompts and references in the workflow examples to ensure consistency with the new file paths. Add new sample documents for PRD, technical design, security assessment, sprint backlog, and implementation tasks for a task management mobile app project.

Author: wvanheemstra

.cursor/rules/product-owner.mdc

@@ -92,12 +92,12 @@ When creating PRDs, use this structure:
 
 ## Example Prompts That Work Well
 
-- "Create a PRD for [feature/product]"
-- "Write user stories for [functionality]"
-- "Analyze the competitive landscape for [product category]"
-- "Define success metrics for [feature]"
-- "Create a product roadmap for [timeframe]"
-- "Prioritize these features using RICE framework"
+- "Create a PRD for [feature/product] and save to docs/source/500/[feature-name]-prd.md"
+- "Write user stories for [functionality] and save to docs/source/500/[feature-name]-stories.md"
+- "Analyze the competitive landscape for [product category] and save to docs/source/500/[feature-name]-competitive-analysis.md"
+- "Define success metrics for [feature] and save to docs/source/500/[feature-name]-metrics.md"
+- "Create a product roadmap for [timeframe] and save to docs/source/500/[feature-name]-roadmap.md"
+- "Prioritize these features using RICE framework and save to docs/source/500/[feature-name]-prioritization.md"
 
 ## Always Remember
 

PERSONA-WORKFLOW-EXAMPLE.md

@@ -26,17 +26,18 @@ In Cursor chat, use this prompt:
 - Password reset functionality
 - User profile management
 
-Please save this PRD to a file called "user-auth-prd.md" in the docs/ directory.
+Please save this PRD to a file called "user-auth-prd.md" in the docs/source/500/ directory.
 ```
 
 **What happens:**
 - The Product Owner persona will create a comprehensive PRD
-- The AI will automatically save it to `docs/user-auth-prd.md`
+- The AI will automatically save it to `docs/source/500/user-auth-prd.md`
+- The file will be integrated into your ReadTheDocs documentation system
 - The file will be version-controlled in your repository
 
 ### Step 2: Review and Approve the PRD
 
-1. Open the generated `docs/user-auth-prd.md` file
+1. Open the generated `docs/source/500/user-auth-prd.md` file
 2. Review the content for completeness and accuracy
 3. Make any necessary edits or request revisions
 4. Once satisfied, proceed to the next step
@@ -46,33 +47,33 @@ Please save this PRD to a file called "user-auth-prd.md" in the docs/ directory.
 After approving the PRD, use this prompt:
 
 ```
-@business-analyst Please review the PRD in docs/user-auth-prd.md and create a detailed technical design document that includes:
+@business-analyst Please review the PRD in docs/source/500/user-auth-prd.md and create a detailed technical design document that includes:
 - System architecture diagrams
 - Database schema design
 - API specifications
 - User flow diagrams
 - Integration requirements
 - Test scenarios
 
-Please save this as "user-auth-design.md" in the docs/ directory and reference the original PRD.
+Please save this as "user-auth-design.md" in the docs/source/500/ directory and reference the original PRD.
 ```
 
 **What happens:**
 - The Business Analyst persona will read the existing PRD file
 - Create a comprehensive technical design document
-- Save it to `docs/user-auth-design.md`
+- Save it to `docs/source/500/user-auth-design.md`
 - Include references to the original PRD
 
 ### Step 4: Continue the Workflow
 
 You can then continue with other personas:
 
 ```
-@software-engineer Review the design in docs/user-auth-design.md and create implementation tasks with technical specifications.
+@software-engineer Review the design in docs/source/500/user-auth-design.md and create implementation tasks with technical specifications. Save to docs/source/500/user-auth-tasks.md
 ```
 
 ```
-@security-analyst Review both the PRD and design documents and provide a security assessment with recommendations.
+@security-analyst Review both the PRD and design documents and provide a security assessment with recommendations. Save to docs/source/500/user-auth-security.md
 ```
 
 ## File Organization
@@ -81,22 +82,27 @@ Your project structure will look like this:
 
 ```
 project/
-├── docs/
-│   ├── user-auth-prd.md          # Product Owner deliverable
-│   ├── user-auth-design.md       # Business Analyst deliverable
-│   ├── user-auth-security.md     # Security Analyst deliverable
-│   ├── user-auth-tasks.md        # Software Engineer deliverable
+├── docs/source/500/
+│   ├── index.md                     # Personas section index
+│   ├── user-auth-prd.md            # Product Owner deliverable
+│   ├── user-auth-design.md         # Business Analyst deliverable
+│   ├── user-auth-security.md       # Security Analyst deliverable
+│   ├── user-auth-tasks.md          # Software Engineer deliverable
 │   └── user-auth-sprint-backlog.md # Scrum Master deliverable
-├── .cursor/
-│   └── rules/
-│       ├── product-owner.mdc
-│       ├── business-analyst.mdc
-│       ├── scrum-master.mdc
-│       ├── software-engineer.mdc
-│       └── security-analyst.mdc
-└── PERSONAS.md
+├── docs/source/
+│   └── index.rst                   # Main documentation index (includes 500/index)
+├── .cursor/rules/
+│   ├── product-owner.mdc
+│   ├── business-analyst.mdc
+│   ├── scrum-master.mdc
+│   ├── software-engineer.mdc
+│   └── security-analyst.mdc
+├── PERSONAS.md
+└── PERSONA-WORKFLOW-EXAMPLE.md
 ```
 
+**ReadTheDocs Integration**: All documents in `docs/source/500/` are automatically included in your ReadTheDocs documentation build and published online.
+
 ## Key Benefits
 
 1. **Traceability**: Each document references previous ones
@@ -115,39 +121,39 @@ project/
 
 ### Example Iteration:
 ```
-@product-owner The PRD in docs/user-auth-prd.md needs more detail on the social login providers. Please update it to include specific OAuth flows and error handling requirements.
+@product-owner The PRD in docs/source/500/user-auth-prd.md needs more detail on the social login providers. Please update it to include specific OAuth flows and error handling requirements.
 ```
 
 ### Cross-Persona Collaboration:
 ```
-@business-analyst Review the PRD in docs/user-auth-prd.md and the security recommendations in docs/user-auth-security.md, then update the design document to incorporate the security requirements.
+@business-analyst Review the PRD in docs/source/500/user-auth-prd.md and the security recommendations in docs/source/500/user-auth-security.md, then update the design document to incorporate the security requirements.
 ```
 
 ## Sample Prompts for Each Stage
 
 ### Initial PRD Creation:
 ```
-@product-owner Create a PRD for [feature description]. Include market research, user stories, success metrics, and technical considerations. Save to docs/[feature-name]-prd.md
+@product-owner Create a PRD for [feature description]. Include market research, user stories, success metrics, and technical considerations. Save to docs/source/500/[feature-name]-prd.md
 ```
 
 ### Design from PRD:
 ```
-@business-analyst Based on the PRD in docs/[feature-name]-prd.md, create a technical design document with architecture, database design, and API specs. Save to docs/[feature-name]-design.md
+@business-analyst Based on the PRD in docs/source/500/[feature-name]-prd.md, create a technical design document with architecture, database design, and API specs. Save to docs/source/500/[feature-name]-design.md
 ```
 
 ### Implementation Planning:
 ```
-@software-engineer Review docs/[feature-name]-design.md and break it down into development tasks with technical specifications. Save to docs/[feature-name]-tasks.md
+@software-engineer Review docs/source/500/[feature-name]-design.md and break it down into development tasks with technical specifications. Save to docs/source/500/[feature-name]-tasks.md
 ```
 
 ### Security Review:
 ```
-@security-analyst Conduct a security assessment of the feature described in docs/[feature-name]-prd.md and docs/[feature-name]-design.md. Save recommendations to docs/[feature-name]-security.md
+@security-analyst Conduct a security assessment of the feature described in docs/source/500/[feature-name]-prd.md and docs/source/500/[feature-name]-design.md. Save recommendations to docs/source/500/[feature-name]-security.md
 ```
 
 ### Sprint Planning:
 ```
-@scrum-master Based on the tasks in docs/[feature-name]-tasks.md, create a sprint plan with story points, dependencies, and timeline. Save to docs/[feature-name]-sprint-plan.md
+@scrum-master Based on the tasks in docs/source/500/[feature-name]-tasks.md, create a sprint plan with story points, dependencies, and timeline. Save to docs/source/500/[feature-name]-sprint-backlog.md
 ```
 
 This workflow ensures that each persona builds upon the previous work, creating a comprehensive and traceable development process.

docs/source/500/index.md

@@ -0,0 +1,133 @@
+# 500 - AI Agent Personas
+
+This section contains documentation generated by AI agent personas - specialized AI agents designed for specific work tasks and roles. Each persona creates professional-quality deliverables following industry best practices.
+
+## What are AI Agent Personas?
+
+AI Agent Personas are documented specifications that define:
+- **Role & Responsibilities**: What the AI agent is designed to do
+- **Capabilities**: Specific skills and knowledge areas
+- **Output Formats**: Expected deliverables and document types
+- **Communication Style**: How the agent should interact
+- **Domain Expertise**: Specialized knowledge and best practices
+
+## Available Personas
+
+### Product Owner (`@product-owner`)
+- **Purpose**: Creates Product Requirement Documents (PRDs) and manages product strategy
+- **Key Deliverables**: PRDs, User Stories, Product Roadmaps, Feature Specifications
+- **Best For**: Product planning, feature definition, stakeholder communication
+
+### Business Analyst (`@business-analyst`)
+- **Purpose**: Analyzes requirements and creates technical specifications
+- **Key Deliverables**: BRDs, Functional Specifications, Process Flow Diagrams, Use Cases
+- **Best For**: Requirements gathering, process analysis, gap analysis
+
+### Scrum Master (`@scrum-master`)
+- **Purpose**: Facilitates agile processes and removes impediments
+- **Key Deliverables**: Sprint Planning Agendas, Retrospective Action Items, Team Velocity Reports
+- **Best For**: Agile facilitation, team coaching, process optimization
+
+### Software Engineer (`@software-engineer`)
+- **Purpose**: Designs, develops, and maintains software systems
+- **Key Deliverables**: Technical Design Documents, Code Implementation, API Documentation
+- **Best For**: Software development, system architecture, code reviews
+
+### Security Analyst (`@security-analyst`)
+- **Purpose**: Conducts security assessments and implements security measures
+- **Key Deliverables**: Security Assessment Reports, Threat Modeling Reports, Incident Response Plans
+- **Best For**: Security assessments, vulnerability analysis, compliance management
+
+## Example Workflow: Task Management Mobile App
+
+This section demonstrates a complete workflow using AI agent personas, from initial product requirements to sprint-ready development tasks.
+
+### 100 - Product Requirements Document
+See [Product Requirements Document](sample-mobile-app-prd.md) - Created by Product Owner persona
+
+**Overview**: Comprehensive PRD for a Task Management Mobile App including market analysis, user stories, success metrics, and go-to-market strategy.
+
+**Key Features**:
+- Mobile-first task management
+- Real-time team collaboration
+- Offline functionality
+- Freemium business model
+
+### 200 - Technical Design Document
+See [Technical Design Document](sample-mobile-app-design.md) - Created by Business Analyst persona
+
+**Overview**: Detailed system architecture, database design, and API specifications based on the PRD.
+
+**Key Components**:
+- React Native + Node.js + PostgreSQL stack
+- Microservices architecture
+- Real-time synchronization with WebSockets
+- Comprehensive API specifications
+
+### 300 - Security Assessment Report
+See [Security Assessment Report](sample-mobile-app-security.md) - Created by Security Analyst persona
+
+**Overview**: Comprehensive security evaluation covering threat modeling, risk assessment, and compliance requirements.
+
+**Key Areas**:
+- GDPR/CCPA compliance analysis
+- OWASP Mobile Top 10 assessment
+- End-to-end encryption recommendations
+- Incident response planning
+
+### 400 - Technical Implementation Tasks
+See [Technical Implementation Tasks](sample-mobile-app-tasks.md) - Created by Software Engineer persona
+
+**Overview**: Detailed breakdown of 24 technical tasks across 4 development phases with effort estimates and acceptance criteria.
+
+**Key Elements**:
+- 16-week development timeline
+- Detailed task dependencies
+- Security requirements integration
+- Performance optimization plans
+
+### 500 - Sprint Backlog
+See [Sprint Backlog](sample-mobile-app-sprint-backlog.md) - Created by Scrum Master persona
+
+**Overview**: Agile sprint planning with 20 user stories organized into 4 sprints, including story point estimation and capacity planning.
+
+**Key Features**:
+- 4-week sprint cycles
+- Story point estimation
+- Risk mitigation strategies
+- Sprint ceremonies and definitions
+
+## How to Use Personas
+
+### Activation
+In Cursor chat, use `@persona-name` to activate any persona:
+
+```
+@product-owner Create a PRD for [feature description]
+@business-analyst Create technical design based on PRD
+@security-analyst Conduct security assessment
+@software-engineer Create implementation tasks
+@scrum-master Create sprint backlog from tasks
+```
+
+### Workflow Process
+1. **Product Owner** creates initial PRD
+2. **Business Analyst** creates technical design
+3. **Security Analyst** creates security assessment
+4. **Software Engineer** creates implementation tasks
+5. **Scrum Master** creates sprint backlog
+6. **Development Team** executes sprints
+
+### File Organization
+Documents are automatically saved to `docs/source/500/` directory and integrated into the documentation system for ReadTheDocs publishing.
+
+## Benefits
+
+- **Professional Quality**: Industry-standard deliverables
+- **Complete Traceability**: Each document builds on previous work
+- **Version Control**: All documents stored in repository
+- **Team Collaboration**: Multiple stakeholders can review and contribute
+- **Automated Publishing**: Integrated with ReadTheDocs workflow
+- **Agile Integration**: Sprint-ready development artifacts
+
+For detailed usage instructions, see the main [PERSONAS.md](../../../PERSONAS.md) documentation.

docs/sample-mobile-app-design.md …s/source/500/sample-mobile-app-design.mddocs/sample-mobile-app-design.md renamed to docs/source/500/sample-mobile-app-design.md docs/sample-mobile-app-design.md renamed to docs/source/500/sample-mobile-app-design.md

@@ -9,9 +9,10 @@ Welcome to Your Project Documentation
    200/index
    300/index
    400/index
+   500/index
 
 Indices and tables
 ==================
 
 * :ref:`genindex`
-* :ref:`search`
+* :ref:`search`