feat(quick-dev): add planning artifact awareness for context-informed specs#2185
feat(quick-dev): add planning artifact awareness for context-informed specs#2185
Conversation
… specs Teach quick-dev step-01 what BMAD phase 1-3 planning artifacts are (PRD, architecture, UX, epics, product brief) so it can selectively load relevant docs instead of guessing from code alone. Remove hard cap of 3 on spec context field, replacing with judgment guidance. Instruct step-03 to explicitly pass context files to the implementation sub-agent.
🤖 Augment PR SummarySummary: Improves the Changes:
🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
📝 WalkthroughWalkthroughUpdated BMAD quick-dev workflow documentation to clarify context-loading behavior across multiple steps. Modified spec-template guidance for the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.md (1)
45-51: Clarify the relationship between loaded artifacts and the spec'scontext:field.Step-01 loads planning artifacts "to form your understanding of the intent" (line 44) and instructs selective loading (line 51), but doesn't explicitly state whether/how these loaded artifacts should populate the
context:field in the spec created later in step-02. The spec-template guidance (line 6 ofspec-template.md) expectscontext:to list "project-wide standards/docs the implementation agent should load."The current flow appears to be: step-01 loads for clarification → step-02 decides what goes into the spec's
context:field → step-03 loads those context files again. If this judgment-based hand-off is intentional, consider a brief clarifying note to reinforce that step-01 loading informs but doesn't dictate the spec'scontext:field.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.md` around lines 45 - 51, The documentation is unclear about whether artifacts loaded in step-01 ("step-01-clarify-and-route.md") should populate the spec's context: field used in step-02 and later loaded again in step-03; add a short clarifying sentence in step-01 (near "load them selectively" / the paragraph referencing "form your understanding of the intent") stating that artifacts loaded in step-01 are for internal clarification only and do not automatically become entries in the spec's context: field — instead, step-02 (the spec creation step) must explicitly decide which project-wide standards/docs to list under context: as described in spec-template.md; reference "step-01", "step-02", "spec-template.md", and the spec field "context:" so readers know the intended hand-off and that step-03 will re-load only those files explicitly included in the spec.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md`:
- Around line 27-28: Clarify that when `{spec_file}` frontmatter contains a
non-empty `context:` list you must load those context files both for sub-agent
handoffs and for direct implementation; specifically, when no sub-agents are
available, include the loaded context content in the direct implementation
prompt/working memory (i.e., prepend or attach the context snippets to the
implementation instruction given to the agent handling `implement`), and
reference the `context:` entries by filename/identifier and their contents so
the implementing code path (direct implement function/step) has access to the
same contextual information as the sub-agent path.
---
Nitpick comments:
In `@src/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.md`:
- Around line 45-51: The documentation is unclear about whether artifacts loaded
in step-01 ("step-01-clarify-and-route.md") should populate the spec's context:
field used in step-02 and later loaded again in step-03; add a short clarifying
sentence in step-01 (near "load them selectively" / the paragraph referencing
"form your understanding of the intent") stating that artifacts loaded in
step-01 are for internal clarification only and do not automatically become
entries in the spec's context: field — instead, step-02 (the spec creation step)
must explicitly decide which project-wide standards/docs to list under context:
as described in spec-template.md; reference "step-01", "step-02",
"spec-template.md", and the spec field "context:" so readers know the intended
hand-off and that step-03 will re-load only those files explicitly included in
the spec.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 9249ff96-3bad-4aed-a46d-a5e30e166796
📒 Files selected for processing (3)
src/bmm-skills/4-implementation/bmad-quick-dev/spec-template.mdsrc/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.mdsrc/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md
Triage Summary2 findings — FIX: 1, DISMISS: 1
|
1 participant
Summary
context:field, replacing with judgment guidanceTest plan
npm run qualitypasses (all linters, tests, skill validation)