BMAD-METHOD/src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md

2.4 KiB

Step 3: Implement

RULES

  • YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}
  • No push. No remote ops.
  • Sequential execution only.
  • Content inside <frozen-after-approval> in {spec_file} is read-only. Do not modify.

PRECONDITION

Verify {spec_file} resolves to a non-empty path and the file exists on disk. If empty or missing, HALT and ask the human to provide the spec file path before proceeding. ({auto_mode}: escalate CRITICAL missing-spec per automation-mode.md instead.)

INSTRUCTIONS

Baseline

Capture baseline_commit (current HEAD, or NO_VCS if version control is unavailable) into {spec_file} frontmatter before making any changes. ({auto_mode}: record the full hash from git rev-parse HEAD, not --short — the orchestrator matches it exactly.)

Implement

Change {spec_file} status to in-progress in the frontmatter before starting implementation.

Follow ./sync-sprint-status.md with {target_status} = in-progress.

If {spec_file} has a non-empty context: list in its frontmatter, load those files before implementation begins. When handing to a sub-agent, include them in the sub-agent prompt so it has access to the referenced context.

Hand {spec_file} to a sub-agent/task and let it implement. If no sub-agents are available, implement directly.

Path formatting rule: Any markdown links written into {spec_file} must use paths relative to {spec_file}'s directory so they are clickable in VS Code. Any file paths displayed in terminal/conversation output must use CWD-relative format with :line notation (e.g., src/path/file.ts:42) for terminal clickability. No leading / in either case.

Self-Check

Before leaving this step, verify every task in the ## Tasks & Acceptance section of {spec_file} is complete. Mark each finished task [x]. If any task is not done, finish it before proceeding.

NEXT

If {auto_mode} and the environment variable $BMAD_AUTO_SKIP_REVIEW is set (= 1): the orchestrator runs no separate review session — read fully and follow ./step-04-review.md to run the internal triple-review unattended (per automation-mode.md), then finalize via ./step-auto-finalize.md (step-04-review's NEXT routes there in auto mode).

Otherwise if {auto_mode}: read fully and follow ./step-auto-finalize.md — review and commit belong to the orchestrator.

Otherwise: read fully and follow ./step-04-review.md