# AI Development Workflows Playbook
**YAML-based workflows** with **smart mini-prompts** for AI agents handling software development and product management tasks.
## π― Quick Access via MCP Server
Use the **AI-powered semantic search** MCP server to find workflows instantly:
- **Search**: Describe your task in natural language
- **Quality Indicators**: π―β
ππ€β show match quality
- **Smart Execution**: Auto-skip steps based on context and prerequisites
## π Available Workflows (9 Total)
| Workflow | Category | Complexity | Steps | Use Case |
|----------|----------|------------|-------|----------|
| [feature-development](#feature-development) | Development | Medium | 14 | Complete feature lifecycle |
| [product-development](#product-development) | Development | High | 15 | Product from idea to launch |
| [quick-fix](#quick-fix) | Development | Low | 4 | Bugs, hotfixes, urgent tasks |
| [code-refactoring](#code-refactoring) | Development | Medium-High | 8 | Architecture improvements |
| [trd-creation](#trd-creation) | Documentation | Medium | 7 | Technical requirements |
| [brd-creation](#brd-creation) | Documentation | Medium | 6 | Business requirements with research |
| [brd-to-trd-translation](#brd-to-trd-translation) | Documentation | Medium | 6 | Business β Technical translation |
| [project-initialization](#project-initialization) | Setup | Medium | 5 | New project context setup |
| [infrastructure-setup](#infrastructure-setup) | Operations | High | 12 | Complete infrastructure deployment |
## π§ Smart Mini-Prompts Architecture
### 25+ Specialized Mini-Prompts by Phase
#### π Business Phase
- **gather-requirements** - Requirements collection and stakeholder analysis
- **document-decisions** - Decision documentation and architectural rationale
- **create-trd** - Technical Requirements Document creation with TRD integration
#### π Analysis Phase
- **feature-analysis** - Feature scope, impact, and complexity analysis
- **architecture-analysis** - System architecture evaluation and planning
- **code-analysis** - Code quality, structure, and technical debt analysis
- **trace-bug-root-cause** - Bug investigation and root cause identification
#### π¨ Development Phase
- **design-architecture** - Solution architecture and technical design
- **ask-clarifying-questions** - Requirements clarification and scope definition
- **code-review** - Code quality review and improvement recommendations
- **implement-feature** - Feature implementation guidance and best practices
#### π Operations Phase
- **deploy-application** - Application deployment procedures and automation
- **monitor-system-health** - System monitoring, alerting, and observability
#### π§ͺ QA Phase
- **create-test-plan** - Test planning, strategy, and coverage analysis
- **execute-tests** - Test execution, automation, and validation
- **validate-requirements** - Requirements validation and acceptance criteria
## π Workflow Details
### Feature Development
**Complete feature development from requirements to deployment**
- **Phases**: Planning β Analysis β Design β Implementation β Testing β Deployment β Reflection
- **Smart Features**: Auto-skips architecture analysis for simple features
- **TRD Integration**: Creates comprehensive technical documentation
- **Best For**: New features, enhancements, complex development tasks
### Product Development
**Comprehensive product development from idea to launch**
- **Phases**: Planning β Analysis β Design β Implementation β Testing β Deployment β Reflection
- **Advanced Features**: Technical analysis, requirements validation, automated testing
- **Complexity**: High - requires extensive planning and validation
- **Best For**: New products, major feature releases, product launches
### Quick Fix
**Fast resolution for bugs, hotfixes, and urgent tasks**
- **Phases**: Planning β Analysis β Implementation β Testing
- **Smart Features**: Auto-skips testing for trivial changes, minimal overhead
- **Speed**: Optimized for emergency situations and simple fixes
- **Best For**: Production bugs, hotfixes, small urgent tasks
### Code Refactoring
**Systematic code improvement and architecture enhancement**
- **Phases**: Analysis β Design β Implementation β Testing β Documentation
- **Focus**: Architecture improvements, performance optimization, technical debt
- **Validation**: Backward compatibility and performance impact assessment
- **Best For**: Technical debt reduction, performance improvements, code modernization
### TRD Creation
**Technical Requirements Document creation from feature ideas**
- **Phases**: Planning β Analysis β Design β Documentation
- **Integration**: Built-in TRD mini-prompt for comprehensive documentation [[memory:2316971]]
- **Smart Features**: Auto-skips architecture analysis for simple features
- **Best For**: Feature planning, technical specification, development preparation
### Project Initialization
**Set up new project context and AI agent documentation**
- **Phases**: Analysis β Planning β Design β Documentation
- **Output**: AGENTS.MD, project navigation, technology stack analysis
- **Smart Features**: Auto-skips steps when sufficient context exists
- **Best For**: New codebases, AI agent setup, project onboarding
## π― Decision Guide
### By Development Stage
| You Have | You Need | Recommended Workflow |
|----------|----------|---------------------|
| Bug/Issue | Quick resolution | **quick-fix** |
| Feature idea | Technical planning | **trd-creation** |
| Technical spec | Working feature | **feature-development** |
| Product idea | Market launch | **product-development** |
| Legacy code | Modern architecture | **code-refactoring** |
| New project | AI setup | **project-initialization** |
### By Complexity Level
| Complexity | Timeframe | Workflows |
|------------|-----------|-----------|
| **Simple** | Hours to 1 day | quick-fix |
| **Standard** | 1-5 days | trd-creation, project-initialization |
| **Complex** | 1-4 weeks | feature-development, code-refactoring |
| **Advanced** | 1+ months | product-development |
## π§ Smart Execution Features
### Intelligent Validation
- **Context Awareness**: Skips steps without required context
- **Prerequisites Check**: Validates dependencies before execution
- **Auto-Skipping**: Bypasses optional steps based on conditions
- **Progress Tracking**: Real-time workflow progress monitoring
### Skip Conditions Examples
- **Architecture Analysis**: Skipped for simple features or when `no_architecture_impact` flag is set
- **Testing**: Skipped for trivial changes in quick-fix when `emergency_hotfix` condition is met
- **Requirements Validation**: Skipped for internal projects when `no_formal_validation_needed` is set
## π Common Workflow Flows
### Emergency Flow
```
Critical Bug β quick-fix β [Optional: feature-development for proper fix]
```
### Feature Development Flow
```
Feature Idea β trd-creation β feature-development β [product-development for major features]
```
### Product Development Flow
```
Product Idea β product-development
```
### New Project Flow
```
New Codebase β project-initialization β [Choose development workflow]
```
### Migration Flow
```
Legacy System β code-refactoring β feature-development
```
## π Getting Started
### 1. Use MCP Server (Recommended)
- Connect to semantic search MCP server
- Describe your task in natural language
- Get workflow recommendations with quality scores
- Follow guided step-by-step execution
### 2. Local Usage
- Copy `playbook/` directory to your project
- Browse workflows in `playbook/workflows/`
- Use mini-prompts from `playbook/mini-prompts/`
- Customize for your team's needs
### 3. Direct Navigation
- **Planning & Documentation**: trd-creation
- **Development**: feature-development, quick-fix, code-refactoring
- **Product & Launch**: product-development
- **Setup & Operations**: project-initialization
## π Success Criteria
### For All Workflows
- β
Requirements clearly defined and documented
- β
All tests pass and quality gates met
- β
No regressions in existing functionality
- β
Documentation updated and current
- β
Requirements validation completed (where required)
### Workflow-Specific Success Metrics
- **Feature Development**: TRD created, feature deployed, requirements validated
- **Product Development**: Product launch successful, technical requirements met
- **Quick Fix**: Issue resolved, no side effects, minimal disruption
---
**π AI Agents Playbook** - Intelligent workflows for modern development teams
**Next Steps**: Use the MCP server for AI-powered workflow discovery, or browse individual workflows for manual execution.