- Created dev-tdd.agent.yaml in proper BMAD format with array-based prompts
- Added complete TDD workflow (dev-story-tdd) with RED-GREEN-REFACTOR cycles
- Included workflow.yaml, instructions.md, README.md, and checklist.md
- Removed incorrectly formatted agent files from test directories
- Agent now conforms to BMAD compilation requirements and will generate proper XML
The agent implements strict TDD methodology with:
- Test-first development enforcement
- RED-GREEN-REFACTOR cycle automation
- RVTM traceability integration
- Story Context as single source of truth
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| README.md | ||
| instructions.md | ||
| project-context.md | ||
| workflow.yaml | ||
README.md
| last-redoc-date |
|---|
| 2025-10-01 |
Project Brainstorming Workflow
This workflow facilitates structured ideation for non-game software projects through systematic exploration of problem spaces, solution architectures, and implementation strategies. Unlike traditional requirement gathering, it employs creative techniques to uncover non-obvious approaches and identify innovative solutions that address core business needs while considering technical constraints and organizational capabilities.
The workflow operates through a project-specific context framework that captures business objectives, technical environment, stakeholder needs, and organizational constraints. It generates multiple solution vectors through parallel ideation tracks: architectural approaches, user experience paradigms, integration patterns, and value delivery mechanisms. Each track produces concrete proposals that are evaluated against feasibility, impact, and alignment with strategic objectives.
Critical differentiators include its focus on solution innovation rather than requirement enumeration, emphasis on technical-business alignment from inception, and structured approach to surfacing hidden assumptions. The workflow produces actionable outputs that directly feed into Product Brief development, ensuring that creative exploration translates into concrete planning artifacts.
Usage
bmad bmm 1-analysis brainstorm-project
Inputs
- Project Context Document: Business objectives, technical environment, stakeholder landscape, organizational constraints, success criteria, and known pain points
- Problem Statement (optional): Core business challenge or opportunity driving the project
Outputs
- Solution Architecture Proposals: Multiple technical approaches with trade-off analysis and feasibility assessments
- Value Delivery Framework: Prioritized feature concepts aligned with business objectives and user needs
- Risk and Opportunity Analysis: Identified technical dependencies, integration challenges, and innovation opportunities
- Strategic Recommendation: Synthesized direction with rationale and implementation considerations