From aura-frog
Analyzes task requirements with dev/QA/UI cross-reviews and generates a detailed requirements document including goals, success criteria, estimates, risks, and questions.
npx claudepluginhub nguyenthienthanh/aura-frog --plugin aura-frogworkflow/# Command: Phase 1 - Understand + Design **Phase:** 1 of 5 **Duration:** 15-30 minutes **Tagline:** "What are we building?" **Last Updated:** 2025-11-26 --- ## 🎯 Purpose 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. --- ## 📋 Phase Objectives 1. **Understand the Task** - Read and analyze user requirements - Identify goals and deliverables - Clarify ambiguous points 2. **Document Requirements** - Create structured requ...
/planOrchestrates multi-agent workflow across analysis and design phases to produce requirements, constraints, NFRs, data model, API contracts, and quickstart guide.
/requirements-authoring-flowGuides AI through requirements authoring workflow (create/update/review/improve) with mandatory user approvals per phase, producing final requirements set, validation pack, and traceability matrix.
/plan-modeCreates multi-agent task hierarchy for planning consultation on a feature, dispatching specialist consultations in parallel and synthesizing an implementation plan (planning only).
/clarify_taskInteractively clarifies tasks or requirements by asking focused questions on objectives, scope, edge cases, constraints, and success criteria, then outputs structured summary.
/sc-planAnalyzes planning tasks or requirements, creates actionable roadmaps, and establishes strategic direction for development work.
Share bugs, ideas, or general feedback.
Phase: 1 of 5 Duration: 15-30 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, frontend, architect, etc.)
tester
frontend (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 deliverables summary
↓
10. Auto-continue to Phase 2 (no approval wait)
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:** lead (Requirements Lead)
- 🤝 **Cross-Review:** [dev-agent] (Technical Feasibility)
- ✅ **Cross-Review:** tester (Testability Check)
- 🎨 **Cross-Review:** frontend (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: Test RED 🔴
**Next Agent:** [dev-agent] (Primary)
We'll write failing tests before implementation (TDD RED phase).
**Token Usage:**
- This phase: [X] tokens (~[Y]K)
- Total used: [A] / 200,000 ([B]%)
- Remaining: [C] tokens
---
**Options:**
- "approve" → Continue to Phase 2 (Test RED)
- "reject: [reason]" → Re-analyze requirements
- "modify: [changes]" → Adjust requirements
- "answer: [responses]" → Answer clarifying questions
⚡ After approval, I'll AUTO-CONTINUE to Phase 2!
**─────────────────────────────────────────────────────────**
🤖 **Agent:** lead | 📋 **System:** Aura Frog v2.2.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_UNDERSTAND_DESIGN.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 5 Status: Active Last Updated: 2026-03-12
Old Name: Requirements Analysis (v4.x compatibility maintained)