BMAD Ate My Month: When Spec-Driven Development Is Too Much

说明与用途

自动编码器生成大型 PR，导致昂贵的审查。通过使用固定 SHA 的 Spec Kit 并将工作限制为约 300 行，减少了令牌使用并加速了发布。

问题

Autonomous coding agents produced large, poorly planned pull requests that caused costly review churn and stalled releases.

结果

By replacing BMAD’s encyclopedic planning with a concise, pinned-spec approach, the author reduced review churn, token usage, and restored release velocity.

工作流

• 1. Create a user story issue with a pinned Spec Kit reference (full SHA).
• 2. If a story has >12 tasks, split it before filing.
• 3. For multiple stories, create a parent epic issue with one child issue per story and an integration branch.
• 4. Run the autopilot skill to generate code against the pinned spec.
• 5. Review the PR using a BLOCKING/SHOULD/NIT rubric tied to the spec.
• 6. Merge if all checks pass; otherwise iterate.
• 7. Keep the spec and issue small to avoid large diffs and long review cycles.

证据

I did not adopt another framework. I took the one thing from the spec-driven world that had earned its keep, Spec Kit's way of expressing intent, and forced it into add-autopilot-issue

来源

Every story issue carries a pinned spec reference: Spec: owner/repo@sha:path#user-story-N

来源