bmad-method 4.13.0 → 4.14.0
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/CHANGELOG.md +7 -0
- package/GUIDING-PRINCIPLES.md +0 -33
- package/README.md +3 -2
- package/bmad-core/agents/analyst.md +3 -1
- package/bmad-core/agents/dev.md +3 -2
- package/bmad-core/agents/qa.md +15 -14
- package/bmad-core/data/bmad-kb.md +280 -19
- package/bmad-core/tasks/document-project.md +250 -322
- package/bmad-core/tasks/review-story.md +135 -0
- package/bmad-core/templates/story-tmpl.md +8 -0
- package/bmad-core/workflows/brownfield-fullstack.yml +36 -1
- package/bmad-core/workflows/brownfield-service.yml +36 -1
- package/bmad-core/workflows/brownfield-ui.yml +36 -1
- package/bmad-core/workflows/greenfield-fullstack.yml +36 -1
- package/bmad-core/workflows/greenfield-service.yml +36 -1
- package/bmad-core/workflows/greenfield-ui.yml +36 -1
- package/dist/agents/analyst.txt +227 -17
- package/dist/agents/bmad-master.txt +260 -24
- package/dist/agents/bmad-orchestrator.txt +227 -17
- package/dist/agents/dev.txt +6 -4
- package/dist/agents/pm.txt +25 -7
- package/dist/agents/po.txt +33 -7
- package/dist/agents/qa.txt +153 -14
- package/dist/agents/sm.txt +8 -0
- package/dist/expansion-packs/expansion-creator/agents/bmad-the-creator.txt +4 -12
- package/dist/teams/team-all.txt +635 -48
- package/dist/teams/team-fullstack.txt +476 -30
- package/dist/teams/team-ide-minimal.txt +419 -42
- package/dist/teams/team-no-ui.txt +332 -26
- package/docs/working-in-the-brownfield.md +362 -0
- package/package.json +1 -1
- package/tools/installer/package.json +1 -1
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
# review-story
|
|
2
|
+
|
|
3
|
+
When a developer marks a story as "Ready for Review", perform a comprehensive senior developer code review with the ability to refactor and improve code directly.
|
|
4
|
+
|
|
5
|
+
[[LLM: QA Agent executing review-story task as Senior Developer]]
|
|
6
|
+
|
|
7
|
+
## Prerequisites
|
|
8
|
+
|
|
9
|
+
- Story status must be "Review"
|
|
10
|
+
- Developer has completed all tasks and updated the File List
|
|
11
|
+
- All automated tests are passing
|
|
12
|
+
|
|
13
|
+
## Review Process
|
|
14
|
+
|
|
15
|
+
1. **Read the Complete Story**
|
|
16
|
+
- Review all acceptance criteria
|
|
17
|
+
- Understand the dev notes and requirements
|
|
18
|
+
- Note any completion notes from the developer
|
|
19
|
+
|
|
20
|
+
2. **Focus on the File List**
|
|
21
|
+
- Verify all files listed were actually created/modified
|
|
22
|
+
- Check for any missing files that should have been updated
|
|
23
|
+
|
|
24
|
+
3. **Senior Developer Code Review**
|
|
25
|
+
- Review code with the eye of a senior developer
|
|
26
|
+
- If changes form a cohesive whole, review them together
|
|
27
|
+
- If changes are independent, review incrementally file by file
|
|
28
|
+
- Focus on:
|
|
29
|
+
- Code architecture and design patterns
|
|
30
|
+
- Refactoring opportunities
|
|
31
|
+
- Code duplication or inefficiencies
|
|
32
|
+
- Performance optimizations
|
|
33
|
+
- Security concerns
|
|
34
|
+
- Best practices and patterns
|
|
35
|
+
|
|
36
|
+
4. **Active Refactoring**
|
|
37
|
+
- As a senior developer, you CAN and SHOULD refactor code where improvements are needed
|
|
38
|
+
- When refactoring:
|
|
39
|
+
- Make the changes directly in the files
|
|
40
|
+
- Explain WHY you're making the change
|
|
41
|
+
- Describe HOW the change improves the code
|
|
42
|
+
- Ensure all tests still pass after refactoring
|
|
43
|
+
- Update the File List if you modify additional files
|
|
44
|
+
|
|
45
|
+
5. **Standards Compliance Check**
|
|
46
|
+
- Verify adherence to `docs/coding-standards.md`
|
|
47
|
+
- Check compliance with `docs/unified-project-structure.md`
|
|
48
|
+
- Validate testing approach against `docs/testing-strategy.md`
|
|
49
|
+
- Ensure all guidelines mentioned in the story are followed
|
|
50
|
+
|
|
51
|
+
6. **Acceptance Criteria Validation**
|
|
52
|
+
- Verify each AC is fully implemented
|
|
53
|
+
- Check for any missing functionality
|
|
54
|
+
- Validate edge cases are handled
|
|
55
|
+
|
|
56
|
+
7. **Test Coverage Review**
|
|
57
|
+
- Ensure unit tests cover edge cases
|
|
58
|
+
- Add missing tests if critical coverage is lacking
|
|
59
|
+
- Verify integration tests (if required) are comprehensive
|
|
60
|
+
- Check that test assertions are meaningful
|
|
61
|
+
- Look for missing test scenarios
|
|
62
|
+
|
|
63
|
+
8. **Documentation and Comments**
|
|
64
|
+
- Verify code is self-documenting where possible
|
|
65
|
+
- Add comments for complex logic if missing
|
|
66
|
+
- Ensure any API changes are documented
|
|
67
|
+
|
|
68
|
+
## Append Results to Story File
|
|
69
|
+
|
|
70
|
+
After review and any refactoring, append your results to the story file in the QA Results section:
|
|
71
|
+
|
|
72
|
+
```markdown
|
|
73
|
+
## QA Results
|
|
74
|
+
|
|
75
|
+
### Review Date: [Date]
|
|
76
|
+
### Reviewed By: Quinn (Senior Developer QA)
|
|
77
|
+
|
|
78
|
+
### Code Quality Assessment
|
|
79
|
+
[Overall assessment of implementation quality]
|
|
80
|
+
|
|
81
|
+
### Refactoring Performed
|
|
82
|
+
[List any refactoring you performed with explanations]
|
|
83
|
+
- **File**: [filename]
|
|
84
|
+
- **Change**: [what was changed]
|
|
85
|
+
- **Why**: [reason for change]
|
|
86
|
+
- **How**: [how it improves the code]
|
|
87
|
+
|
|
88
|
+
### Compliance Check
|
|
89
|
+
- Coding Standards: [✓/✗] [notes if any]
|
|
90
|
+
- Project Structure: [✓/✗] [notes if any]
|
|
91
|
+
- Testing Strategy: [✓/✗] [notes if any]
|
|
92
|
+
- All ACs Met: [✓/✗] [notes if any]
|
|
93
|
+
|
|
94
|
+
### Improvements Checklist
|
|
95
|
+
[Check off items you handled yourself, leave unchecked for dev to address]
|
|
96
|
+
|
|
97
|
+
- [x] Refactored user service for better error handling (services/user.service.ts)
|
|
98
|
+
- [x] Added missing edge case tests (services/user.service.test.ts)
|
|
99
|
+
- [ ] Consider extracting validation logic to separate validator class
|
|
100
|
+
- [ ] Add integration test for error scenarios
|
|
101
|
+
- [ ] Update API documentation for new error codes
|
|
102
|
+
|
|
103
|
+
### Security Review
|
|
104
|
+
[Any security concerns found and whether addressed]
|
|
105
|
+
|
|
106
|
+
### Performance Considerations
|
|
107
|
+
[Any performance issues found and whether addressed]
|
|
108
|
+
|
|
109
|
+
### Final Status
|
|
110
|
+
[✓ Approved - Ready for Done] / [✗ Changes Required - See unchecked items above]
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
## Key Principles
|
|
114
|
+
|
|
115
|
+
- You are a SENIOR developer reviewing junior/mid-level work
|
|
116
|
+
- You have the authority and responsibility to improve code directly
|
|
117
|
+
- Always explain your changes for learning purposes
|
|
118
|
+
- Balance between perfection and pragmatism
|
|
119
|
+
- Focus on significant improvements, not nitpicks
|
|
120
|
+
|
|
121
|
+
## Blocking Conditions
|
|
122
|
+
|
|
123
|
+
Stop the review and request clarification if:
|
|
124
|
+
- Story file is incomplete or missing critical sections
|
|
125
|
+
- File List is empty or clearly incomplete
|
|
126
|
+
- No tests exist when they were required
|
|
127
|
+
- Code changes don't align with story requirements
|
|
128
|
+
- Critical architectural issues that require discussion
|
|
129
|
+
|
|
130
|
+
## Completion
|
|
131
|
+
|
|
132
|
+
After review:
|
|
133
|
+
1. If all items are checked and approved: Update story status to "Done"
|
|
134
|
+
2. If unchecked items remain: Keep status as "Review" for dev to address
|
|
135
|
+
3. Always provide constructive feedback and explanations for learning
|
|
@@ -52,6 +52,10 @@ Manual Test Steps: [[LLM: Include how if possible the user can manually test the
|
|
|
52
52
|
[[LLM: (SM Agent) When Drafting Story, leave next prompt in place for dev agent to remove and update - remove this line to the SM]]
|
|
53
53
|
[[LLM: (Dev Agent) Anything the SM needs to know that deviated from the story that might impact drafting the next story.]]
|
|
54
54
|
|
|
55
|
+
### File List
|
|
56
|
+
|
|
57
|
+
[[LLM: (Dev Agent) List every new file created, or existing file modified in a bullet list.]]
|
|
58
|
+
|
|
55
59
|
### Change Log
|
|
56
60
|
|
|
57
61
|
[[LLM: (SM Agent) When Drafting Story, leave next prompt in place for dev agent to remove and update- remove this line to the SM]]
|
|
@@ -59,3 +63,7 @@ Manual Test Steps: [[LLM: Include how if possible the user can manually test the
|
|
|
59
63
|
|
|
60
64
|
| Date | Version | Description | Author |
|
|
61
65
|
| :--- | :------ | :---------- | :----- |
|
|
66
|
+
|
|
67
|
+
## QA Results
|
|
68
|
+
|
|
69
|
+
[[LLM: QA Agent Results]]
|
|
@@ -42,7 +42,42 @@ workflow:
|
|
|
42
42
|
|
|
43
43
|
- workflow_end:
|
|
44
44
|
action: move_to_ide
|
|
45
|
-
notes:
|
|
45
|
+
notes: |
|
|
46
|
+
Planning phase complete! Now transition to IDE Development:
|
|
47
|
+
|
|
48
|
+
1. ENSURE DOCUMENTS ARE IN PROJECT:
|
|
49
|
+
- Copy final prd.md to project's docs/prd.md
|
|
50
|
+
- Copy final architecture.md to project's docs/architecture.md
|
|
51
|
+
- All documents must be in the project before proceeding
|
|
52
|
+
|
|
53
|
+
2. SHARD DOCUMENTS (in IDE):
|
|
54
|
+
- Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
|
|
55
|
+
- Option B: Manual: Drag shard-doc task + docs/prd.md into chat
|
|
56
|
+
- This creates docs/prd/ and docs/architecture/ folders with sharded content
|
|
57
|
+
|
|
58
|
+
3. START DEVELOPMENT CYCLE:
|
|
59
|
+
a. SM Agent (New Chat): @sm → *create
|
|
60
|
+
- Creates next story from sharded docs
|
|
61
|
+
- Review and approve story (Draft → Approved)
|
|
62
|
+
|
|
63
|
+
b. Dev Agent (New Chat): @dev
|
|
64
|
+
- Implements approved story
|
|
65
|
+
- Updates File List with all changes
|
|
66
|
+
- Marks story as "Review" when complete
|
|
67
|
+
|
|
68
|
+
c. QA Agent (New Chat): @qa → review-story
|
|
69
|
+
- Senior dev review with refactoring ability
|
|
70
|
+
- Fixes small issues directly
|
|
71
|
+
- Leaves checklist for remaining items
|
|
72
|
+
- Updates story status (Review → Done or stays Review)
|
|
73
|
+
|
|
74
|
+
d. If QA left unchecked items:
|
|
75
|
+
- Dev Agent (New Chat): Address remaining items
|
|
76
|
+
- Return to QA for final approval
|
|
77
|
+
|
|
78
|
+
4. REPEAT: Continue cycle for all epic stories
|
|
79
|
+
|
|
80
|
+
Reference: data#bmad-kb:IDE Development Workflow
|
|
46
81
|
|
|
47
82
|
flow_diagram: |
|
|
48
83
|
```mermaid
|
|
@@ -43,7 +43,42 @@ workflow:
|
|
|
43
43
|
|
|
44
44
|
- workflow_end:
|
|
45
45
|
action: move_to_ide
|
|
46
|
-
notes:
|
|
46
|
+
notes: |
|
|
47
|
+
Planning phase complete! Now transition to IDE Development:
|
|
48
|
+
|
|
49
|
+
1. ENSURE DOCUMENTS ARE IN PROJECT:
|
|
50
|
+
- Copy final prd.md to project's docs/prd.md
|
|
51
|
+
- Copy final architecture.md to project's docs/architecture.md
|
|
52
|
+
- All documents must be in the project before proceeding
|
|
53
|
+
|
|
54
|
+
2. SHARD DOCUMENTS (in IDE):
|
|
55
|
+
- Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
|
|
56
|
+
- Option B: Manual: Drag shard-doc task + docs/prd.md into chat
|
|
57
|
+
- This creates docs/prd/ and docs/architecture/ folders with sharded content
|
|
58
|
+
|
|
59
|
+
3. START DEVELOPMENT CYCLE:
|
|
60
|
+
a. SM Agent (New Chat): @sm → *create
|
|
61
|
+
- Creates next story from sharded docs
|
|
62
|
+
- Review and approve story (Draft → Approved)
|
|
63
|
+
|
|
64
|
+
b. Dev Agent (New Chat): @dev
|
|
65
|
+
- Implements approved story
|
|
66
|
+
- Updates File List with all changes
|
|
67
|
+
- Marks story as "Review" when complete
|
|
68
|
+
|
|
69
|
+
c. QA Agent (New Chat): @qa → review-story
|
|
70
|
+
- Senior dev review with refactoring ability
|
|
71
|
+
- Fixes small issues directly
|
|
72
|
+
- Leaves checklist for remaining items
|
|
73
|
+
- Updates story status (Review → Done or stays Review)
|
|
74
|
+
|
|
75
|
+
d. If QA left unchecked items:
|
|
76
|
+
- Dev Agent (New Chat): Address remaining items
|
|
77
|
+
- Return to QA for final approval
|
|
78
|
+
|
|
79
|
+
4. REPEAT: Continue cycle for all epic stories
|
|
80
|
+
|
|
81
|
+
Reference: data#bmad-kb:IDE Development Workflow
|
|
47
82
|
|
|
48
83
|
flow_diagram: |
|
|
49
84
|
```mermaid
|
|
@@ -50,7 +50,42 @@ workflow:
|
|
|
50
50
|
|
|
51
51
|
- workflow_end:
|
|
52
52
|
action: move_to_ide
|
|
53
|
-
notes:
|
|
53
|
+
notes: |
|
|
54
|
+
Planning phase complete! Now transition to IDE Development:
|
|
55
|
+
|
|
56
|
+
1. ENSURE DOCUMENTS ARE IN PROJECT:
|
|
57
|
+
- Copy final prd.md to project's docs/prd.md
|
|
58
|
+
- Copy final architecture.md to project's docs/architecture.md
|
|
59
|
+
- All documents must be in the project before proceeding
|
|
60
|
+
|
|
61
|
+
2. SHARD DOCUMENTS (in IDE):
|
|
62
|
+
- Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
|
|
63
|
+
- Option B: Manual: Drag shard-doc task + docs/prd.md into chat
|
|
64
|
+
- This creates docs/prd/ and docs/architecture/ folders with sharded content
|
|
65
|
+
|
|
66
|
+
3. START DEVELOPMENT CYCLE:
|
|
67
|
+
a. SM Agent (New Chat): @sm → *create
|
|
68
|
+
- Creates next story from sharded docs
|
|
69
|
+
- Review and approve story (Draft → Approved)
|
|
70
|
+
|
|
71
|
+
b. Dev Agent (New Chat): @dev
|
|
72
|
+
- Implements approved story
|
|
73
|
+
- Updates File List with all changes
|
|
74
|
+
- Marks story as "Review" when complete
|
|
75
|
+
|
|
76
|
+
c. QA Agent (New Chat): @qa → review-story
|
|
77
|
+
- Senior dev review with refactoring ability
|
|
78
|
+
- Fixes small issues directly
|
|
79
|
+
- Leaves checklist for remaining items
|
|
80
|
+
- Updates story status (Review → Done or stays Review)
|
|
81
|
+
|
|
82
|
+
d. If QA left unchecked items:
|
|
83
|
+
- Dev Agent (New Chat): Address remaining items
|
|
84
|
+
- Return to QA for final approval
|
|
85
|
+
|
|
86
|
+
4. REPEAT: Continue cycle for all epic stories
|
|
87
|
+
|
|
88
|
+
Reference: data#bmad-kb:IDE Development Workflow
|
|
54
89
|
|
|
55
90
|
flow_diagram: |
|
|
56
91
|
```mermaid
|
|
@@ -75,7 +75,42 @@ workflow:
|
|
|
75
75
|
|
|
76
76
|
- workflow_end:
|
|
77
77
|
action: move_to_ide
|
|
78
|
-
notes:
|
|
78
|
+
notes: |
|
|
79
|
+
Planning phase complete! Now transition to IDE Development:
|
|
80
|
+
|
|
81
|
+
1. ENSURE DOCUMENTS ARE IN PROJECT:
|
|
82
|
+
- Copy final prd.md to project's docs/prd.md
|
|
83
|
+
- Copy final architecture.md to project's docs/architecture.md
|
|
84
|
+
- All documents must be in the project before proceeding
|
|
85
|
+
|
|
86
|
+
2. SHARD DOCUMENTS (in IDE):
|
|
87
|
+
- Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
|
|
88
|
+
- Option B: Manual: Drag shard-doc task + docs/prd.md into chat
|
|
89
|
+
- This creates docs/prd/ and docs/architecture/ folders with sharded content
|
|
90
|
+
|
|
91
|
+
3. START DEVELOPMENT CYCLE:
|
|
92
|
+
a. SM Agent (New Chat): @sm → *create
|
|
93
|
+
- Creates next story from sharded docs
|
|
94
|
+
- Review and approve story (Draft → Approved)
|
|
95
|
+
|
|
96
|
+
b. Dev Agent (New Chat): @dev
|
|
97
|
+
- Implements approved story
|
|
98
|
+
- Updates File List with all changes
|
|
99
|
+
- Marks story as "Review" when complete
|
|
100
|
+
|
|
101
|
+
c. QA Agent (New Chat): @qa → review-story
|
|
102
|
+
- Senior dev review with refactoring ability
|
|
103
|
+
- Fixes small issues directly
|
|
104
|
+
- Leaves checklist for remaining items
|
|
105
|
+
- Updates story status (Review → Done or stays Review)
|
|
106
|
+
|
|
107
|
+
d. If QA left unchecked items:
|
|
108
|
+
- Dev Agent (New Chat): Address remaining items
|
|
109
|
+
- Return to QA for final approval
|
|
110
|
+
|
|
111
|
+
4. REPEAT: Continue cycle for all epic stories
|
|
112
|
+
|
|
113
|
+
Reference: data#bmad-kb:IDE Development Workflow
|
|
79
114
|
|
|
80
115
|
flow_diagram: |
|
|
81
116
|
```mermaid
|
|
@@ -51,7 +51,42 @@ workflow:
|
|
|
51
51
|
|
|
52
52
|
- workflow_end:
|
|
53
53
|
action: move_to_ide
|
|
54
|
-
notes:
|
|
54
|
+
notes: |
|
|
55
|
+
Planning phase complete! Now transition to IDE Development:
|
|
56
|
+
|
|
57
|
+
1. ENSURE DOCUMENTS ARE IN PROJECT:
|
|
58
|
+
- Copy final prd.md to project's docs/prd.md
|
|
59
|
+
- Copy final architecture.md to project's docs/architecture.md
|
|
60
|
+
- All documents must be in the project before proceeding
|
|
61
|
+
|
|
62
|
+
2. SHARD DOCUMENTS (in IDE):
|
|
63
|
+
- Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
|
|
64
|
+
- Option B: Manual: Drag shard-doc task + docs/prd.md into chat
|
|
65
|
+
- This creates docs/prd/ and docs/architecture/ folders with sharded content
|
|
66
|
+
|
|
67
|
+
3. START DEVELOPMENT CYCLE:
|
|
68
|
+
a. SM Agent (New Chat): @sm → *create
|
|
69
|
+
- Creates next story from sharded docs
|
|
70
|
+
- Review and approve story (Draft → Approved)
|
|
71
|
+
|
|
72
|
+
b. Dev Agent (New Chat): @dev
|
|
73
|
+
- Implements approved story
|
|
74
|
+
- Updates File List with all changes
|
|
75
|
+
- Marks story as "Review" when complete
|
|
76
|
+
|
|
77
|
+
c. QA Agent (New Chat): @qa → review-story
|
|
78
|
+
- Senior dev review with refactoring ability
|
|
79
|
+
- Fixes small issues directly
|
|
80
|
+
- Leaves checklist for remaining items
|
|
81
|
+
- Updates story status (Review → Done or stays Review)
|
|
82
|
+
|
|
83
|
+
d. If QA left unchecked items:
|
|
84
|
+
- Dev Agent (New Chat): Address remaining items
|
|
85
|
+
- Return to QA for final approval
|
|
86
|
+
|
|
87
|
+
4. REPEAT: Continue cycle for all epic stories
|
|
88
|
+
|
|
89
|
+
Reference: data#bmad-kb:IDE Development Workflow
|
|
55
90
|
|
|
56
91
|
flow_diagram: |
|
|
57
92
|
```mermaid
|
|
@@ -70,7 +70,42 @@ workflow:
|
|
|
70
70
|
|
|
71
71
|
- workflow_end:
|
|
72
72
|
action: move_to_ide
|
|
73
|
-
notes:
|
|
73
|
+
notes: |
|
|
74
|
+
Planning phase complete! Now transition to IDE Development:
|
|
75
|
+
|
|
76
|
+
1. ENSURE DOCUMENTS ARE IN PROJECT:
|
|
77
|
+
- Copy final prd.md to project's docs/prd.md
|
|
78
|
+
- Copy final architecture.md to project's docs/architecture.md
|
|
79
|
+
- All documents must be in the project before proceeding
|
|
80
|
+
|
|
81
|
+
2. SHARD DOCUMENTS (in IDE):
|
|
82
|
+
- Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
|
|
83
|
+
- Option B: Manual: Drag shard-doc task + docs/prd.md into chat
|
|
84
|
+
- This creates docs/prd/ and docs/architecture/ folders with sharded content
|
|
85
|
+
|
|
86
|
+
3. START DEVELOPMENT CYCLE:
|
|
87
|
+
a. SM Agent (New Chat): @sm → *create
|
|
88
|
+
- Creates next story from sharded docs
|
|
89
|
+
- Review and approve story (Draft → Approved)
|
|
90
|
+
|
|
91
|
+
b. Dev Agent (New Chat): @dev
|
|
92
|
+
- Implements approved story
|
|
93
|
+
- Updates File List with all changes
|
|
94
|
+
- Marks story as "Review" when complete
|
|
95
|
+
|
|
96
|
+
c. QA Agent (New Chat): @qa → review-story
|
|
97
|
+
- Senior dev review with refactoring ability
|
|
98
|
+
- Fixes small issues directly
|
|
99
|
+
- Leaves checklist for remaining items
|
|
100
|
+
- Updates story status (Review → Done or stays Review)
|
|
101
|
+
|
|
102
|
+
d. If QA left unchecked items:
|
|
103
|
+
- Dev Agent (New Chat): Address remaining items
|
|
104
|
+
- Return to QA for final approval
|
|
105
|
+
|
|
106
|
+
4. REPEAT: Continue cycle for all epic stories
|
|
107
|
+
|
|
108
|
+
Reference: data#bmad-kb:IDE Development Workflow
|
|
74
109
|
|
|
75
110
|
flow_diagram: |
|
|
76
111
|
```mermaid
|