ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
91f6c41be1509025f0c520adab856788ae7a4d0a
BMAD-METHOD/docs/_basement/how-to/brownfield/quick-fix-in-brownfield.md
Alex Verkhovsky 91f6c41be1 docs: radical reduction of documentation scope for v6 beta (#1406) 
* docs: radical reduction of documentation scope for v6 beta

Archive and basement unreviewed content to ship a focused, minimal doc set.

Changes:
- Archive stale how-to workflow guides (will rewrite for v6)
- Archive outdated explanation and reference content
- Move unreviewed content to basement for later review
- Reorganize TEA docs into dedicated /tea/ section
- Add workflow-map visual reference page
- Simplify getting-started tutorial and sidebar navigation
- Add explanation pages: brainstorming, adversarial-review, party-mode,
  quick-flow, advanced-elicitation
- Fix base URL handling for subdirectory deployments (GitHub Pages forks)

The goal is a minimal, accurate doc set for beta rather than
comprehensive but potentially misleading content.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* refactor: restructure BMM and agents documentation by consolidating and flattening index files.

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-25 14:00:26 -06:00

1.7 KiB
Raw Blame History

title, description
title description
How to Make Quick Fixes in Brownfield Projects How to make quick fixes and ad-hoc changes in brownfield projects

Use the DEV agent directly for bug fixes, refactorings, or small targeted changes that don't require the full BMad method or Quick Flow.

When to Use This

  • Bug fixes
  • Small refactorings
  • Targeted code improvements
  • Learning about your codebase
  • One-off changes that don't need planning

Steps

1. Load an Agent

For quick fixes, you can use:

  • DEV agent - For implementation-focused work
  • Quick Flow Solo Dev - For slightly larger changes that still need a tech-spec

2. Describe the Change

Simply tell the agent what you need:

Fix the login validation bug that allows empty passwords

or

Refactor the UserService to use async/await instead of callbacks

3. Let the Agent Work

The agent will:

  • Analyze the relevant code
  • Propose a solution
  • Implement the change
  • Run tests (if available)

4. Review and Commit

Review the changes made and commit when satisfied.

Learning Your Codebase

This approach is also excellent for exploring unfamiliar code:

Explain how the authentication system works in this codebase

Show me where error handling happens in the API layer

LLMs are excellent at interpreting and analyzing code—whether it was AI-generated or not. Use the agent to:

  • Learn about your project
  • Understand how things are built
  • Explore unfamiliar parts of the codebase

When to Upgrade to Formal Planning

Consider using Quick Flow or full BMad Method when:

  • The change affects multiple files or systems
  • You're unsure about the scope
  • The fix keeps growing in complexity
  • You need documentation for the change