**Version:** 1.0.0
/plugin marketplace add nguyenthienthanh/aura-frog/plugin install aura-frog@aurafrogworkflow/Version: 1.0.0
Purpose: Execute Phase 2 - Technical Planning
Trigger: Auto-triggered after Phase 1 approval OR manual /workflow:phase:2
Create detailed technical specification and architecture plan for implementation.
Deliverables:
Primary Agent: Dev agent (mobile-react-native/web-*/backend-laravel)
Actions:
Agents: Dev agent + UI Designer (if UI changes)
Create:
Create comprehensive tech spec document:
# Technical Specification
## Overview
[Brief description]
## Architecture
[Architecture diagram in ASCII/mermaid]
## Components/Modules
### Component 1
- Purpose: ...
- Props: ...
- State: ...
- Dependencies: ...
## File Changes
- CREATE: path/to/new/file.tsx
- UPDATE: path/to/existing/file.tsx
- DELETE: path/to/old/file.tsx
## API Design (if applicable)
### Endpoint 1
- Method: POST
- Path: /api/v1/resource
- Request: {...}
- Response: {...}
## Database Changes (if applicable)
[Schema changes]
## Dependencies
- Add: package@version
- Update: package@version
## Testing Strategy
[High-level test plan]
## Risks & Mitigation
[Potential issues and solutions]
## Estimation
### Story Points
**Total:** X story points (Fibonacci scale)
**Breakdown:**
- Phase 4 (Test Planning): 1 point
- Phase 5a (Write Tests): 2 points
- Phase 5b (Implementation): 5 points
- Phase 5c (Refactor): 2 points
- Phase 6 (Code Review): 1 point
- Phase 7 (QA Verification): 2 points
**Confidence:** High/Medium/Low
**Story Point Reference:**
- 1 point: Trivial (~1-2 hours)
- 2 points: Simple (~2-4 hours)
- 3 points: Moderate (~4-6 hours)
- 5 points: Complex (~1 day)
- 8 points: Very Complex (~2 days)
- 13 points: Extensive (~3 days)
- 21 points: Epic (consider breaking down)
### Time Estimate
- Phase 4-5: X hours
- Phase 6-7: Y hours
- **Total:** Z hours (~W days)
**Velocity Factor:** Based on team velocity (adjust for your team)
Use ASCII art or Mermaid syntax:
┌─────────────────┐
│ Main Component │
└────────┬────────┘
│
┌────┴────┬────────────┬──────────┐
│ │ │ │
┌───▼───┐ ┌──▼──┐ ┌───────▼──┐ ┌────▼────┐
│ Comp1 │ │Comp2│ │ Comp3 │ │ Hook │
└───────┘ └─────┘ └──────────┘ └─────────┘
Or Mermaid:
graph TD
A[Main Component] --> B[Component 1]
A --> C[Component 2]
A --> D[Custom Hook]
B --> E[Sub-component]
Uses templates/tech-spec.md as base template.
Customize for:
Phase 2 is complete when:
═══════════════════════════════════════════════════════════
🎯 PHASE 2 COMPLETE: Technical Planning
═══════════════════════════════════════════════════════════
📊 Summary:
Created technical specification with architecture design
📦 Deliverables:
📄 TECH_SPEC.md (architecture, components, API design)
📊 architecture-diagram.png
📈 Metrics:
- Components to create: 5
- Files to change: 8 files
- New dependencies: 2 packages
- Story Points: 8 points (Complex)
- Estimated effort: 1-2 days (~12-16 hours)
- Confidence: High
✅ Success Criteria:
✅ Architecture clearly defined
✅ Component breakdown complete
✅ File changes identified
✅ Risks assessed
⏭️ Next Phase: Phase 3 - Design Review
───────────────────────────────────────────────────────────
⚠️ ACTION REQUIRED
Type "/workflow:approve" → Proceed to Phase 3
Type "/workflow:reject" → Restart Phase 2
Type "/workflow:modify <feedback>" → Refine tech spec
Your response:
═══════════════════════════════════════════════════════════
User can provide feedback:
/workflow:reject Need to reconsider state management approach
Agent will:
logs/contexts/{workflow-id}/deliverables/
└── PHASE_2_TECH_SPEC.md (comprehensive tech spec)
After approval:
/workflow:phase:3 - Design Review (if UI changes)/workflow:phase:4 - Test PlanningStatus: Active command
Related: workflow:phase:1, workflow:phase:3, workflow:approve