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

deferred_work_file	spec_file
{implementation_artifacts}/deferred-work.md

Step One-Shot: Implement, Review, Present

RULES

• YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}
• NEVER auto-push.

INSTRUCTIONS

Implement

Implement the clarified intent directly.

Review

Invoke the bmad-review-adversarial-general skill in a subagent with the changed files. The subagent gets NO conversation context — to avoid anchoring bias. If no sub-agents are available, write the changed files to a review prompt file in {implementation_artifacts} and HALT. Ask the human to run the review in a separate session and paste back the findings.

Classify

Deduplicate all review findings. Three categories only:

• patch — trivially fixable. Auto-fix immediately.
• defer — pre-existing issue not caused by this change. Append to {deferred_work_file}.
• reject — noise. Drop silently.

If a finding is caused by this change but too significant for a trivial patch, HALT and present it to the human for decision before proceeding.

Generate Spec Trace

Write {spec_file} with the following content:

1. Frontmatter — same schema as the full spec template, plus route: 'one-shot':

   ---
   title: '{title derived from intent}'
   type: '{feature | bugfix | refactor | chore}'
   created: '{date}'
   status: 'done'
   route: 'one-shot'
   ---
   

2. Title and Intent — the # {title} heading followed by an ## Intent section with Problem and Approach lines (2–3 sentences total). This is the same summary you already generated for the terminal — reuse it.

3. Suggested Review Order — append as a ## Suggested Review Order section. Build using the same convention as step-05:

   • Order stops by concern, not by file. Lead with the entry point.
   • Every code reference is a clickable spec-file-relative link. Compute each link target as a relative path from {spec_file}'s directory to the changed file. Format: [short-name:line](../../path/to/file.ts#L42) with a #L line anchor. The relative path must be dynamically derived — never hardcode the depth.
   • Each stop gets one ultra-concise line of framing (≤15 words).
   • When there is only one concern, omit the bold label — just list the stops directly.

   Format each stop as framing first, link on the next indented line:

   ## Suggested Review Order
   
   - {one-line framing}
     [`file.ts:42`](../../src/path/to/file.ts#L42)
   

   The ../../ prefix above is illustrative — compute the actual relative path from {spec_file}'s directory to each target file.

Commit

If version control is available and the tree is dirty, create a local commit with a conventional message derived from the intent. If VCS is unavailable, skip.

Present

1. Open the spec in the user's editor so they can click through the Suggested Review Order:
   • Resolve two absolute paths: (1) the repository root (git rev-parse --show-toplevel — returns the worktree root when in a worktree, project root otherwise; if this fails, fall back to the current working directory), (2) {spec_file}. Run code -r "{absolute-root}" "{absolute-spec-file}" — the root first so VS Code opens in the right context, then the spec file. Always double-quote paths to handle spaces and special characters.
   • If code is not available (command fails), skip gracefully and tell the user the spec file path instead.
2. Display a summary in conversation output, including:
   • The commit hash (if one was created).
   • List of files changed with one-line descriptions. Any file paths shown in conversation/terminal output must use CWD-relative format (no leading /) with :line notation (e.g., src/path/file.ts:42) for terminal clickability — this differs from spec-file links which use spec-file-relative paths.
   • Review findings breakdown: patches applied, items deferred, items rejected. If all findings were rejected, say so.
   • A note that the spec is open in their editor (or the file path if it couldn't be opened). Mention that {spec_file} now contains a Suggested Review Order.
   • Navigation tip: "Ctrl+click (Cmd+click on macOS) the links in the Suggested Review Order to jump to each stop."
3. Offer to push and/or create a pull request.

HALT and wait for human input.

Workflow complete.