**Version:** 1.0.0
/plugin marketplace add nguyenthienthanh/ccpm-team-agents/plugin install nguyenthienthanh-aura-frog-aura-frog-2@nguyenthienthanh/ccpm-team-agentsworkflow/Version: 1.0.0 Phase: 1 of 9 Duration: 20-45 minutes Tagline: "What are we building?" Last Updated: 2025-11-26
Phase 1 is where we understand the task requirements, goals, and success criteria. This phase ensures everyone (agents and user) is aligned on what needs to be built before diving into implementation.
Understand the Task
Document Requirements
Cross-Review
Development Agent (mobile-react-native, web-reactjs, backend-laravel, etc.)
qa-automation
ui-designer (if UI/UX involved)
File: .claude/logs/workflows/{workflow-id}/phase-1-requirements.md
Sections:
Task Overview
Goals & Objectives
Success Criteria
Technical Requirements
Constraints & Assumptions
Risk Assessment
Initial Estimation
Questions & Clarifications
Cross-Review Feedback
1. PM Orchestrator reads task
ā
2. Analyze requirements
ā
3. Identify goals & success criteria
ā
4. Ask clarifying questions (if needed)
ā
5. Document findings
ā
6. Cross-Review:
- Dev Agent reviews technical feasibility
- QA Agent reviews testability
- UI Designer reviews design needs (if applicable)
ā
7. Incorporate feedback
ā
8. Finalize requirements document
ā
9. Show approval gate
ā
10. Wait for user approval
After completing Phase 1, show this approval gate:
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
šÆ Phase 1: Understand - Approval Needed
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
## We understand what we're building! āØ
*"What are we building?"*
**š¤ Agents Working:**
- šÆ **Primary:** pm-operations-orchestrator (Requirements Lead)
- š¤ **Cross-Review:** [dev-agent] (Technical Feasibility)
- ā
**Cross-Review:** qa-automation (Testability Check)
- šØ **Cross-Review:** ui-designer (Design Review) [if applicable]
**š¤ System:** Aura Frog Team Agents v1.0.0
**š Mode:** Workflow Phase Execution
---
**What We Did:**
- Analyzed task requirements
- Identified goals and success criteria
- Documented technical requirements
- Assessed risks and constraints
- Cross-reviewed with dev, QA, and UI teams
**Deliverables:**
- ā
Requirements Analysis Document
- ā
Success Criteria Defined
- ā
Risk Assessment Complete
**Key Findings:**
- [Finding 1]
- [Finding 2]
- [Finding 3]
**Initial Estimation:**
- Story Points: X points (Complexity Level)
- Time Estimate: Y-Z hours (~W days)
- Confidence: High/Medium/Low
**Cross-Review:**
- ā
Dev Agent: Technically feasible ā
- ā
QA Agent: Testable requirements ā
- ā
UI Designer: Design requirements clear ā [if applicable]
**Clarifying Questions:** [if any]
- Question 1?
- Question 2?
**Next Phase:** Phase 2: Design šļø
**Next Agent:** [dev-agent] (Primary)
We'll design the technical solution architecture.
**Token Usage:**
- This phase: [X] tokens (~[Y]K)
- Total used: [A] / 200,000 ([B]%)
- Remaining: [C] tokens
---
**Options:**
- "approve" ā Continue to Phase 2 (Design)
- "reject: [reason]" ā Re-analyze requirements
- "modify: [changes]" ā Adjust requirements
- "answer: [responses]" ā Answer clarifying questions
ā” After approval, I'll AUTO-CONTINUE to Phase 2!
**āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā**
š¤ **Agent:** pm-operations-orchestrator | š **System:** Aura Frog v1.0.0
**āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā**
Your response:
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Phase 1 is complete when:
Solution: Ask specific clarifying questions before proceeding
Solution: Dev agent suggests investigation or proof-of-concept in Phase 2
Solution: Document trade-offs and ask user to prioritize
Solution: Suggest breaking into smaller tasks/workflows
docs/phases/PHASE_1_REQUIREMENTS_ANALYSIS.MDdocs/APPROVAL_GATES.mddocs/AGENT_IDENTIFICATION.mdcommands/workflow/phase-2.mdcommands/workflow/start.mdFor PM Orchestrator:
For Cross-Review Agents:
For Users:
Phase: 1 of 9 Version: 1.0.0 Status: Active Last Updated: 2025-11-26
Old Name: Requirements Analysis (v4.x compatibility maintained)