Skip to content

fix(quick-dev): replace role statement with step-following mandate#2045

Merged
alexeyv merged 2 commits intomainfrom
fix-quick-dev-workflow-preamble
Mar 18, 2026
Merged

fix(quick-dev): replace role statement with step-following mandate#2045
alexeyv merged 2 commits intomainfrom
fix-quick-dev-workflow-preamble

Conversation

@alexeyv
Copy link
Copy Markdown
Collaborator

@alexeyv alexeyv commented Mar 18, 2026

Summary

  • Removed the "elite developer" role statement ("implement autonomously", "minimum ceremony, maximum signal") which actively encouraged the model to skip workflow steps when it judged the task was simple enough
  • Replaced the verbose goal with a concrete one: "Turn user intent into a hardened, reviewable artifact"
  • Added a one-line critical rule enforcing step-file compliance

Context

During a real session, the model read workflow.md, saw a detailed implementation plan already existed in the repo, and skipped the entire step-file chain -- going straight to implementation without ever loading step 1. The role statement language ("autonomously", "minimum ceremony") was identified as a contributing factor, giving the model a justification to bypass process.

Test plan

  • Run the workflow on a task where a detailed plan already exists -- verify the model follows step 1 instead of jumping to implementation
  • Run on a normal task -- verify no regression in workflow behavior

The "elite developer" role with "implement autonomously" and "minimum
ceremony" language actively encouraged the model to skip workflow steps
when it judged the task was simple enough. Replaced with a concrete goal
and a critical rule enforcing step-file compliance.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@augmentcode
Copy link
Copy Markdown

augmentcode bot commented Mar 18, 2026

🤖 Augment PR Summary

Summary: Updates the Quick Dev New Preview workflow preamble to reduce the chance the agent skips the step-file chain.
Changes: Replaces the prior “elite developer” role statement with a strict step-following mandate and tightens the workflow goal to emphasize producing a hardened, reviewable artifact.

🤖 Was this summary useful? React with 👍 or 👎

Copy link
Copy Markdown

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 1 suggestion posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

**Goal:** Turn user intent into a hardened, reviewable artifact.

**Your Role:** You are an elite developer. You clarify intent, plan precisely, implement autonomously, review adversarially, and present findings honestly. Minimum ceremony, maximum signal.
**CRITICAL:** If a step says "read fully and follow step-XX", you read and follow step-XX. No exceptions.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The quoted trigger phrase ("read fully and follow step-XX") doesn’t match the actual phrasing used in the step files (e.g., Read fully and follow \./step-02-plan.md``), which might leave a loophole for strict/keyword-based interpretation. Consider making this rule apply to any instruction to “Read fully and follow” a step file path, regardless of the exact wording.

Severity: low

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 18, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bed0a9f0-2e7f-4270-899f-974571c8aede

📥 Commits

Reviewing files that changed from the base of the PR and between f3f606a and 96091cb.

📒 Files selected for processing (1)
  • src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/workflow.md

📝 Walkthrough

Walkthrough

Updated workflow documentation for the Quick Dev New Preview process, changing the goals statement from a multi-stage user request flow to a concise objective of turning intent into reviewable artifacts, and revised role guidance to emphasize strict adherence to step instructions with a critical rule about reading and following designated steps.

Changes

Cohort / File(s) Summary
Quick Dev New Preview Workflow
src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/workflow.md
Updated workflow goals and added CRITICAL rule for step-file sequencing; role guidance now emphasizes strict compliance with step instructions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • bmadcode
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: replacing a role statement with a step-following mandate to fix workflow compliance issues.
Description check ✅ Passed The description is well-related to the changeset, explaining the motivation, specific changes made, and test plan for verifying the fix.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-quick-dev-workflow-preamble
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant