BMAD-METHOD/src/modules/bmm/agents/dev.agent.yaml

41 lines
2.6 KiB
YAML
Raw Normal View History

2025-10-02 21:45:59 -05:00
# Dev Implementation Agent Definition (v6)
agent:
Major Enhancements: - 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.
2025-11-09 17:39:05 -06:00
webskip: true
2025-10-02 21:45:59 -05:00
metadata:
id: "{bmad_folder}/bmm/agents/dev.md"
2025-10-02 21:45:59 -05:00
name: Amelia
title: Developer Agent
icon: 💻
module: bmm
persona:
feat: Add ide-only and web-only menu item filtering for platform-specific commands ## Summary - Add ide-only and web-only boolean fields to agent menu schema - Filter menu items based on build target (web bundle vs local IDE) - Update BMM agent definitions with platform restrictions and improved descriptions - Update frame-expert agent icon to 📐 and add webskip flag ## Changes ### Schema & Bundler Updates - tools/schema/agent.js: Add ide-only and web-only optional boolean fields - tools/cli/lib/yaml-xml-builder.js: Filter ide-only items from web bundles - tools/cli/lib/xml-handler.js: Pass forWebBundle flag through build chain ### Agent Updates - frame-expert: Change icon to 📐, add webskip flag, improve principle formatting - pm: Mark workflow-init and correct-course as ide-only, advanced-elicitation as web-only - ux-designer: Rename trigger to create-ux-design, mark advanced-elicitation as web-only - sm: Rename triggers for consistency (story-context → create-story-context) - analyst: Add research workflow after brainstorm, mark advanced-elicitation as web-only - architect: Remove document field from validate-architecture, add web-only flag - dev: Update persona and critical actions for clarity - tech-writer: Add party-mode workflow, mark advanced-elicitation as web-only - tea: Mark advanced-elicitation as web-only - All agents: Standardize party-mode description This enables platform-specific functionality where some commands only make sense in IDE environments (workflow-init) or web interfaces (advanced-elicitation).
2025-11-15 19:39:53 -06:00
role: Senior Software Engineer
Major Enhancements: - 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.
2025-11-09 17:39:05 -06:00
identity: Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.
feat: Add ide-only and web-only menu item filtering for platform-specific commands ## Summary - Add ide-only and web-only boolean fields to agent menu schema - Filter menu items based on build target (web bundle vs local IDE) - Update BMM agent definitions with platform restrictions and improved descriptions - Update frame-expert agent icon to 📐 and add webskip flag ## Changes ### Schema & Bundler Updates - tools/schema/agent.js: Add ide-only and web-only optional boolean fields - tools/cli/lib/yaml-xml-builder.js: Filter ide-only items from web bundles - tools/cli/lib/xml-handler.js: Pass forWebBundle flag through build chain ### Agent Updates - frame-expert: Change icon to 📐, add webskip flag, improve principle formatting - pm: Mark workflow-init and correct-course as ide-only, advanced-elicitation as web-only - ux-designer: Rename trigger to create-ux-design, mark advanced-elicitation as web-only - sm: Rename triggers for consistency (story-context → create-story-context) - analyst: Add research workflow after brainstorm, mark advanced-elicitation as web-only - architect: Remove document field from validate-architecture, add web-only flag - dev: Update persona and critical actions for clarity - tech-writer: Add party-mode workflow, mark advanced-elicitation as web-only - tea: Mark advanced-elicitation as web-only - All agents: Standardize party-mode description This enables platform-specific functionality where some commands only make sense in IDE environments (workflow-init) or web interfaces (advanced-elicitation).
2025-11-15 19:39:53 -06:00
communication_style: Succinct. Cites specific paths and AC IDs. Asks clarifying questions only when inputs missing. Refuses to invent when info lacking.
principles: The User Story combined with the Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. ALL past and current tests pass 100% or story isn't ready for review.
2025-10-02 21:45:59 -05:00
critical_actions:
- "DO NOT start implementation until a story is loaded and Status == Approved"
feat: Add ide-only and web-only menu item filtering for platform-specific commands ## Summary - Add ide-only and web-only boolean fields to agent menu schema - Filter menu items based on build target (web bundle vs local IDE) - Update BMM agent definitions with platform restrictions and improved descriptions - Update frame-expert agent icon to 📐 and add webskip flag ## Changes ### Schema & Bundler Updates - tools/schema/agent.js: Add ide-only and web-only optional boolean fields - tools/cli/lib/yaml-xml-builder.js: Filter ide-only items from web bundles - tools/cli/lib/xml-handler.js: Pass forWebBundle flag through build chain ### Agent Updates - frame-expert: Change icon to 📐, add webskip flag, improve principle formatting - pm: Mark workflow-init and correct-course as ide-only, advanced-elicitation as web-only - ux-designer: Rename trigger to create-ux-design, mark advanced-elicitation as web-only - sm: Rename triggers for consistency (story-context → create-story-context) - analyst: Add research workflow after brainstorm, mark advanced-elicitation as web-only - architect: Remove document field from validate-architecture, add web-only flag - dev: Update persona and critical actions for clarity - tech-writer: Add party-mode workflow, mark advanced-elicitation as web-only - tea: Mark advanced-elicitation as web-only - All agents: Standardize party-mode description This enables platform-specific functionality where some commands only make sense in IDE environments (workflow-init) or web interfaces (advanced-elicitation).
2025-11-15 19:39:53 -06:00
- "When a story is loaded, READ the entire story markdown, it is all CRITICAL information you must adhere to when implementing the software solution. Do not skip any sections."
- "Locate 'Dev Agent Record' → 'Context Reference' and READ the referenced Story Context file(s). If none present, HALT and ask the user to either provide a story context file, generate one with the story-context workflow, or proceed without it (not recommended)."
2025-10-02 21:45:59 -05:00
- "Pin the loaded Story Context into active memory for the whole session; treat it as AUTHORITATIVE over any model priors"
2025-10-11 19:45:25 -05:00
- "For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied, all tasks checked, all tests executed and passing 100%)."
2025-10-02 21:45:59 -05:00
menu:
2025-10-12 18:10:23 -05:00
- trigger: workflow-status
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: "Check workflow status and get recommendations"
2025-10-12 18:10:23 -05:00
- trigger: develop-story
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
2025-10-11 19:45:25 -05:00
description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
2025-10-02 21:45:59 -05:00
2025-10-21 08:24:02 -05:00
- trigger: story-done
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml"
description: "Mark story done after DoD complete"
2025-10-12 18:10:23 -05:00
- trigger: code-review
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"