bmad-method 6.2.1-next.5 → 6.2.1-next.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/bmm/agents/bmad-agent-analyst/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-architect/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-dev/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-pm/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-qa/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-quick-flow-solo-dev/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-sm/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-tech-writer/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/agents/bmad-agent-ux-designer/bmad-skill-manifest.yaml +1 -1
- package/src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/step-05-present.md +46 -3
- package/src/bmm/agents/bmad-skill-manifest.yaml +0 -39
package/package.json
CHANGED
|
@@ -10,8 +10,51 @@
|
|
|
10
10
|
|
|
11
11
|
## INSTRUCTIONS
|
|
12
12
|
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
13
|
+
### Generate Suggested Review Order
|
|
14
|
+
|
|
15
|
+
Determine what changed:
|
|
16
|
+
|
|
17
|
+
- **Plan-code-review:** Read `{baseline_commit}` from `{spec_file}` frontmatter and construct the diff of all changes since that commit.
|
|
18
|
+
- **One-shot:** No baseline exists. Use the files you created or modified during implementation.
|
|
19
|
+
|
|
20
|
+
**Plan-code-review:** Append the review order as a `## Suggested Review Order` section to `{spec_file}` **after the last existing section**. Do not modify the Code Map.
|
|
21
|
+
|
|
22
|
+
**One-shot:** Display the review order directly in conversation output.
|
|
23
|
+
|
|
24
|
+
Build the trail as an ordered sequence of **stops** — clickable `path:line` references with brief framing — optimized for a human reviewer reading top-down to understand the change:
|
|
25
|
+
|
|
26
|
+
1. **Order by concern, not by file.** Group stops by the conceptual concern they address (e.g., "validation logic", "schema change", "UI binding"). A single file may appear under multiple concerns.
|
|
27
|
+
2. **Lead with the entry point** — the single highest-leverage file:line a reviewer should look at first to grasp the design intent.
|
|
28
|
+
3. **Inside each concern**, order stops from most important / architecturally interesting to supporting. Lightly bias toward higher-risk or boundary-crossing stops.
|
|
29
|
+
4. **End with peripherals** — tests, config, types, and other supporting changes come last.
|
|
30
|
+
5. **Every code reference is a clickable `vscode://file/` link.** Format each stop as a markdown link: `[short-name:line](vscode://file/absolute/path:line:1)`. Use the file's basename (or shortest unambiguous suffix) as the link text.
|
|
31
|
+
6. **Each stop gets one ultra-concise line of framing** (≤15 words) — why this approach was chosen here and what it achieves in the context of the change. No paragraphs.
|
|
32
|
+
|
|
33
|
+
Format each stop as framing first, link on the next indented line:
|
|
34
|
+
|
|
35
|
+
```markdown
|
|
36
|
+
## Suggested Review Order
|
|
37
|
+
|
|
38
|
+
**{Concern name}**
|
|
39
|
+
|
|
40
|
+
- {one-line framing}
|
|
41
|
+
[`file.ts:42`](vscode://file/absolute/path/to/file.ts:42:1)
|
|
42
|
+
|
|
43
|
+
- {one-line framing}
|
|
44
|
+
[`other.ts:17`](vscode://file/absolute/path/to/other.ts:17:1)
|
|
45
|
+
|
|
46
|
+
**{Next concern}**
|
|
47
|
+
|
|
48
|
+
- {one-line framing}
|
|
49
|
+
[`file.ts:88`](vscode://file/absolute/path/to/file.ts:88:1)
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
When there is only one concern, omit the bold label — just list the stops directly.
|
|
53
|
+
|
|
54
|
+
### Commit and Present
|
|
55
|
+
|
|
56
|
+
1. **Plan-code-review:** Change `{spec_file}` status to `done` in the frontmatter.
|
|
57
|
+
2. If version control is available and the tree is dirty, create a local commit with a conventional message derived from the spec title (plan-code-review) or the intent (one-shot).
|
|
58
|
+
3. Display summary of your work to the user, including the commit hash if one was created. Advise on how to review the changes — for plan-code-review, mention that `{spec_file}` now contains a Suggested Review Order. Offer to push and/or create a pull request.
|
|
16
59
|
|
|
17
60
|
Workflow complete.
|
|
@@ -1,39 +0,0 @@
|
|
|
1
|
-
analyst.agent.yaml:
|
|
2
|
-
canonicalId: bmad-analyst
|
|
3
|
-
type: agent
|
|
4
|
-
description: "Business Analyst for market research, competitive analysis, and requirements elicitation"
|
|
5
|
-
|
|
6
|
-
architect.agent.yaml:
|
|
7
|
-
canonicalId: bmad-architect
|
|
8
|
-
type: agent
|
|
9
|
-
description: "Architect for distributed systems, cloud infrastructure, and API design"
|
|
10
|
-
|
|
11
|
-
dev.agent.yaml:
|
|
12
|
-
canonicalId: bmad-dev
|
|
13
|
-
type: agent
|
|
14
|
-
description: "Developer Agent for story execution, test-driven development, and code implementation"
|
|
15
|
-
|
|
16
|
-
pm.agent.yaml:
|
|
17
|
-
canonicalId: bmad-pm
|
|
18
|
-
type: agent
|
|
19
|
-
description: "Product Manager for PRD creation, requirements discovery, and stakeholder alignment"
|
|
20
|
-
|
|
21
|
-
qa.agent.yaml:
|
|
22
|
-
canonicalId: bmad-qa
|
|
23
|
-
type: agent
|
|
24
|
-
description: "QA Engineer for test automation, API testing, and E2E testing"
|
|
25
|
-
|
|
26
|
-
quick-flow-solo-dev.agent.yaml:
|
|
27
|
-
canonicalId: bmad-quick-flow-solo-dev
|
|
28
|
-
type: agent
|
|
29
|
-
description: "Quick Flow Solo Dev for rapid spec creation and lean implementation"
|
|
30
|
-
|
|
31
|
-
sm.agent.yaml:
|
|
32
|
-
canonicalId: bmad-sm
|
|
33
|
-
type: agent
|
|
34
|
-
description: "Scrum Master for sprint planning, story preparation, and agile ceremonies"
|
|
35
|
-
|
|
36
|
-
ux-designer.agent.yaml:
|
|
37
|
-
canonicalId: bmad-ux-designer
|
|
38
|
-
type: agent
|
|
39
|
-
description: "UX Designer for user research, interaction design, and UI patterns"
|