mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
7eb52520fa
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
57 lines
2.0 KiB
YAML
57 lines
2.0 KiB
YAML
# Test Architect workflow: nfr-assess
|
|
name: testarch-nfr
|
|
description: "Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation"
|
|
author: "BMad"
|
|
|
|
# Critical variables from config
|
|
config_source: "{project-root}/.bmad/bmm/config.yaml"
|
|
output_folder: "{config_source}:output_folder"
|
|
user_name: "{config_source}:user_name"
|
|
communication_language: "{config_source}:communication_language"
|
|
document_output_language: "{config_source}:document_output_language"
|
|
date: system-generated
|
|
|
|
# Workflow components
|
|
installed_path: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess"
|
|
instructions: "{installed_path}/instructions.md"
|
|
validation: "{installed_path}/checklist.md"
|
|
template: "{installed_path}/nfr-report-template.md"
|
|
|
|
# Variables and inputs
|
|
variables:
|
|
# NFR category assessment (defaults to all categories)
|
|
custom_nfr_categories: "" # Optional additional categories beyond standard (security, performance, reliability, maintainability)
|
|
|
|
# Output configuration
|
|
default_output_file: "{output_folder}/nfr-assessment.md"
|
|
|
|
# Required tools
|
|
required_tools:
|
|
- read_file # Read story, test results, metrics, logs, BMad artifacts
|
|
- write_file # Create NFR assessment, gate YAML, evidence checklist
|
|
- list_files # Discover test results, metrics, logs
|
|
- search_repo # Find NFR-related tests and evidence
|
|
- glob # Find result files matching patterns
|
|
|
|
# Recommended inputs
|
|
recommended_inputs:
|
|
- story: "Story markdown with NFR requirements (optional)"
|
|
- tech_spec: "Technical specification with NFR targets (recommended)"
|
|
- test_results: "Test execution results (performance, security, etc.)"
|
|
- metrics: "Application metrics (response times, error rates, etc.)"
|
|
- logs: "Application logs for reliability analysis"
|
|
- ci_results: "CI/CD pipeline results for burn-in validation"
|
|
|
|
tags:
|
|
- qa
|
|
- nfr
|
|
- test-architect
|
|
- performance
|
|
- security
|
|
- reliability
|
|
|
|
execution_hints:
|
|
interactive: false # Minimize prompts
|
|
autonomous: true # Proceed without user input unless blocked
|
|
iterative: true
|