ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

fix internal project skills and rename to prefix with bmad-os

This commit is contained in:
Brian Madison 2026-02-04 17:04:34 -06:00
parent 89d0c34eb7
commit 5276d58b2c
6 changed files with 14 additions and 458 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
.claude/skills/changelog-social/SKILL.md
View File

@ -1,5 +1,5 @@
---
name: changelog-social
name: bmad-os-changelog-social
description: Generate social media announcements for Discord, Twitter, and LinkedIn from the latest changelog entry. Use when user asks to create release announcements, social posts, or share changelog updates. Reads CHANGELOG.md in current working directory. Reference examples/ for tone and format.
disable-model-invocation: true
---
@ -154,7 +154,13 @@ Read the appropriate example file before generating to match the established sty
## Output Format
Present both announcements in clearly labeled sections:
**CRITICAL: ALWAYS write to files** - Create files in `_bmad-output/social/` directory:
1. `{repo-name}-discord-{version}.md` - Discord announcement
2. `{repo-name}-twitter-{version}.md` - Twitter post
3. `{repo-name}-linkedin-{version}.md` - LinkedIn post (if applicable)
Also present a preview in the chat:
```markdown
## Discord Announcement
@ -166,4 +172,7 @@ Present both announcements in clearly labeled sections:
[paste Twitter content here]
```
Files created:
- `_bmad-output/social/{filename}`
Offer to make adjustments if the user wants different emphasis, tone, or content.

2
.claude/skills/draft-changelog/SKILL.md
View File

@ -1,5 +1,5 @@
---
name: draft-changelog
name: bmad-os-draft-changelog
description: Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
disable-model-invocation: true
---

2
.claude/skills/gh-triage/SKILL.md
View File

@ -1,5 +1,5 @@
---
name: gh-triage
name: bmad-os-gh-triage
description: Fetch all GitHub issues via gh CLI and use AI agents to deeply analyze, cluster, and prioritize issues
license: MIT
disable-model-invocation: true

2
.claude/skills/release-module/SKILL.md
View File

@ -1,5 +1,5 @@
---
name: release-module
name: bmad-os-release-module
description: Automates the complete release process for npm modules - version bump, changelog, git tag, npm publish, GitHub release
disable-model-invocation: true
---

20
.claude/skills/release-module/prompts/instructions.md
View File

@ -42,26 +42,6 @@ Publish the package.
Create release with changelog notes using `gh release create`.
### Step 10: Create Social Announcement
Create a social media announcement file at `_bmad-output/social/{repo-name}-release.md`.
Format:
```markdown
# {name} v{version} Released
## Highlights
{2-3 bullet points of key features/changes}
## Links
- GitHub: {release-url}
- npm: {npm-url}
```
### Step 11: Confirm Completion
Show npm, GitHub, and social announcement file paths.
## Error Handling
Stop immediately on any step failure. Inform user and suggest fix.

433
src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md
View File

@ -1,433 +0,0 @@
---
validationTarget: 'PRD Workflow Structure'
validationDate: '2026-01-08'
inputDocuments: []
validationStepsCompleted: ['discovery', 'frontmatter-validation', 'content-validation', 'documentation-validation', 'integration-validation', 'corrections-applied']
validationStatus: COMPLETE - PRODUCTION READY
---
# PRD Workflow Validation Report
**Workflow Being Validated:** _bmad/bmm/workflows/2-plan-workflows/create-prd
**Validation Date:** 2026-01-08
**Validator:** BMAD Workflow Validation System
---
## Executive Summary
This validation report assesses the PRD workflow structure against BMAD workflow standards. The PRD workflow is a tri-modal workflow system with Create, Validate, and Edit phases.
---
## 1. File Structure & Size Analysis
### Folder Structure
```
prd/
├── workflow.md (main workflow file)
├── steps-c/ (Create steps - 12 files)
├── steps-v/ (Validation steps - 13 files)
├── steps-e/ (Edit steps - 5 files)
├── data/
│ └── prd-purpose.md
└── templates/
└── prd-template.md
```
**✅ Structure Status**: PASS - All required folders present
### File Size Analysis
#### Steps-C (Create Steps) - 12 files
| File | Lines | Status |
| ------------------------ | ----- | ------------------- |
| step-01-init.md | 191 | ⚠️ Approaching limit |
| step-01b-continue.md | 153 | ✅ Good |
| step-02-discovery.md | 197 | ⚠️ Approaching limit |
| step-03-success.md | 226 | ⚠️ Approaching limit |
| step-04-journeys.md | 213 | ⚠️ Approaching limit |
| step-05-domain.md | 193 | ⚠️ Approaching limit |
| step-06-innovation.md | 226 | ⚠️ Approaching limit |
| step-07-project-type.md | 225 | ⚠️ Approaching limit |
| step-08-scoping.md | 228 | ⚠️ Approaching limit |
| step-09-functional.md | 231 | ⚠️ Approaching limit |
| step-10-nonfunctional.md | 242 | ⚠️ Approaching limit |
| step-11-polish.md | 217 | ⚠️ Approaching limit |
| step-12-complete.md | 185 | ✅ Good |
#### Steps-V (Validation Steps) - 13 files
| File | Lines | Status |
| ---------------------------------------------- | ----- | ------------------- |
| step-v-01-discovery.md | 217 | ⚠️ Approaching limit |
| step-v-02-format-detection.md | 191 | ⚠️ Approaching limit |
| step-v-02b-parity-check.md | 209 | ⚠️ Approaching limit |
| step-v-03-density-validation.md | 174 | ✅ Good |
| step-v-04-brief-coverage-validation.md | 214 | ⚠️ Approaching limit |
| step-v-05-measurability-validation.md | 228 | ⚠️ Approaching limit |
| step-v-06-traceability-validation.md | 217 | ⚠️ Approaching limit |
| step-v-07-implementation-leakage-validation.md | 205 | ⚠️ Approaching limit |
| step-v-08-domain-compliance-validation.md | 243 | ⚠️ Approaching limit |
| step-v-09-project-type-validation.md | 263 | ❌ Exceeds limit |
| step-v-10-smart-validation.md | 209 | ⚠️ Approaching limit |
| step-v-11-holistic-quality-validation.md | 264 | ❌ Exceeds limit |
| step-v-12-completeness-validation.md | 242 | ⚠️ Approaching limit |
| step-v-13-report-complete.md | 231 | ⚠️ Approaching limit |
#### Steps-E (Edit Steps) - 5 files
| File | Lines | Status |
| ------------------------------- | ----- | ------------------- |
| step-e-01-discovery.md | 206 | ⚠️ Approaching limit |
| step-e-01b-legacy-conversion.md | 208 | ⚠️ Approaching limit |
| step-e-02-review.md | 249 | ⚠️ Approaching limit |
| step-e-03-edit.md | 253 | ❌ Exceeds limit |
| step-e-04-complete.md | 168 | ✅ Good |
#### Data & Templates
| File | Lines | Status |
| ------------------------- | ----- | ------------------- |
| data/prd-purpose.md | 197 | ⚠️ Approaching limit |
| templates/prd-template.md | 10 | ✅ Good |
| workflow.md | 114 | ✅ Good |
### File Size Statistics
- **Total Files**: 32 markdown files
- **✅ Good (<200 lines)**: 6 files (18.8%)
- **⚠️ Approaching limit (200-250)**: 23 files (71.9%)
- **❌ Exceeds limit (>250)**: 3 files (9.4%)
- **Average lines per file**: 213.3 lines
### ⚠️ Recommendations
1. **Files Exceeding 250-line limit**:
- `step-v-09-project-type-validation.md` (263 lines) - Consider splitting into sub-steps
- `step-v-11-holistic-quality-validation.md` (264 lines) - Consider splitting into sub-steps
- `step-e-03-edit.md` (253 lines) - Consider splitting into sub-steps
2. **Files Approaching Limit**:
- Many files are in the 200-250 line range
- Monitor these files as further additions may push them over the limit
- Consider proactive refactoring where appropriate
---
## 2. Frontmatter Structure Validation
### Files Checked: 29 total files
**✅ Overall Status:** ALL VALID - One Issue Fixed
#### Main Workflow (workflow.md)
**Required Fields Present:**
- ✅ `name`: "prd"
- ✅ `description`: "PRD tri-modal workflow"
- ✅ `nextStep`: "./steps-c/step-01-init.md"
- ✅ `validateWorkflow`: "./steps-v/step-v-01-discovery.md"
- ✅ `editWorkflow`: "./steps-e/step-e-01-discovery.md" (FIXED - was assess-workflow.md)
#### Create Steps (steps-c)
- ✅ All 13 files have proper name, description, nextStepFile
- ✅ Proper sequencing from step-01 through step-12
- ✅ Consistent output file references
#### Validation Steps (steps-v)
- ✅ All 13 files have complete frontmatter
- ✅ Proper sequential chain maintained
- ✅ No broken internal references
#### Edit Steps (steps-e)
- ✅ All files have required fields
- ✅ Proper routing with altStepFile references
### ✅ All Issues Resolved
**1. Broken Edit Workflow Reference:**
```yaml
# Current (INCORRECT):
editWorkflow: './steps-e/step-e-01-assess-workflow.md'
# Should be:
editWorkflow: './steps-e/step-e-01-discovery.md'
```
**2. Step Numbering Gap:**
- Original `step-11-complete.md` was deleted
- Sequence now: step-10 → step-11-polish → step-12-complete
- Creates confusion in step numbering
### ✅ YAML Syntax
- No YAML syntax errors detected
- All frontmatter properly formatted
- Consistent structure across files
### Status
✅ **ALL ISSUES RESOLVED** - Only cosmetic improvements remain:
1. **✅ FIXED**: Edit workflow path corrected in workflow.md
2. **⚠️ OPTIONAL**: Address step numbering gap for clarity
3. **⚠️ OPTIONAL**: Rename step-01b-continue.md to step-01a-continue.md for consistency
---
## 3. Step File Content Validation
### Content Quality Assessment: 4.5/5 - EXCELLENT
#### Files Reviewed: 10 representative files across all modes
#### ✅ Strengths
**1. Comprehensive Structure:**
- Clear step goal sections in all files
- Detailed mandatory execution rules
- Well-defined execution protocols
- Context boundaries clearly specified
- Mandatory sequence with numbered steps
- System success/failure metrics present
**2. BMAD Compliance:**
- ✅ JIT loading references consistently mentioned
- ✅ State tracking requirements documented
- ✅ Append-only building instructions present
- ✅ Critical rules properly emphasized with emojis
- ✅ Sequential enforcement clearly stated
**3. Instructional Quality:**
- Clear, unambiguous instructions
- Proper menu handling rules (where applicable)
- Excellent continuation checks
- Strong role definition for each mode
**4. Role Clarity:**
- Create Mode: "Product-focused PM facilitator"
- Validate Mode: "Validation Architect and Quality Assurance Specialist"
- Edit Mode: "PRD improvement specialist"
#### ⚠️ Minor Improvement Opportunities
**1. Header Formatting:**
- Some inconsistency in header level usage across files
- Recommend standardizing H2/H3 usage
**2. Edit Mode Completeness:**
- Edit mode has fewer steps (5 vs 12/13 for other modes)
- Documentation marks it as "Future" but implementation exists
#### Recommendations
1. **LOW PRIORITY**: Standardize header formatting across all step files
2. **LOW PRIORITY**: Complete remaining edit mode steps for parity
3. **MAINTAIN**: Current excellent quality standards
---
## 4. Documentation Validation
### Documentation Completeness: ✅ COMPREHENSIVE
#### Main Components Present
- ✅ Workflow Definition (workflow.md)
- ✅ Purpose Document (data/prd-purpose.md)
- ✅ Template (templates/prd-template.md)
- ✅ Three Mode Implementations (Create: 12, Validate: 13, Edit: 5 steps)
#### Clarity Assessment: ✅ EXCELLENT
**Strong Points:**
1. Clear mode determination (commands, flags, menu selection)
2. Detailed routing instructions for each mode
3. Comprehensive workflow architecture explanation
4. Well-defined critical rules with visual emphasis
5. Professional presentation with consistent formatting
#### ⚠️ Minor Issues Found
**1. Step Count Mismatch:**
- workflow.md mentions "11 steps" for Create mode
- Actually implements 12 steps
- Could confuse users
**2. Edit Mode Status:**
- workflow.md calls Edit mode "Future"
- Edit mode steps are actually implemented
- Should reflect current status
**3. Template Completeness:**
- PRD template is minimal (10 lines)
- Could benefit from section placeholders
**4. Missing README:**
- No onboarding documentation for new users
- Not critical but would be helpful
#### Recommendations
**HIGH PRIORITY:**
1. Fix step count reference to match implementation (12 steps)
2. Update edit mode documentation to "Implemented"
**MEDIUM PRIORITY:**
3. Enhance PRD template with section structure
4. Add quick-start README for new users
**LOW PRIORITY:**
5. Add troubleshooting section
6. Document external dependencies (domain-complexity.csv, project-types.csv)
---
## 5. Integration & Compatibility Validation
### Integration Status: 85% Ready
#### ✅ Successfully Integrated Components
**1. Agent Menu Registration:**
- ✅ Registered in PM agent menu
- ✅ Trigger: `PR` or fuzzy match on `prd`
- ✅ Command: `/bmad:bmm:workflows:create-prd`
- ✅ Proper workflow path configuration
**2. External Workflow References:**
- ✅ Party-mode workflow: Exists at `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
- ✅ Advanced-elicitation task: Exists at `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`
**3. Directory Structure:**
- ✅ Complete step architecture (all 3 modes)
- ✅ All referenced step files exist
- ✅ Data files available
#### ✅ Configuration & Installation - WORKING AS DESIGNED
**1. BMM Config Reference:**
- Path: `{project-root}/_bmad/bmm/config.yaml`
- **Status:** ✅ Correct installation-time placeholder
- Resolves to actual config during workflow installation
- **Note:** This is expected behavior, not an issue
**2. Planning Artifacts Folder:**
- Reference: `{planning_artifacts}/prd.md`
- **Status:** ✅ Correct installation-time placeholder
- Created/resolved during workflow installation
- **Note:** This is expected behavior, not an issue
**3. Edit Mode Implementation:**
- Current: 5 steps (Discovery, Legacy Conversion branch, Review, Edit, Complete)
- **Status:** ✅ Functionally complete
- Edit mode is inherently simpler than create mode (targeted improvements vs full creation)
- Uses subprocesses for complex operations
- Validation integration ensures quality
- **Note:** Edit workflow is complete and well-designed
#### Configuration Analysis
**Placeholder Usage:**
- `{project-root}`: ✅ Properly used
- `{planning_artifacts}`: ⚠️ Referenced but folder missing
- `{nextStep}`, `{validateWorkflow}`, etc: ✅ Properly resolved
#### Recommendations
**✅ ALL CRITICAL ISSUES RESOLVED:**
The only true critical issue (edit workflow path) has been fixed. All other items flagged as "critical" were actually working as designed (installation-time placeholders).
**LOW PRIORITY:**
3. Add CLI command registration for standalone execution (optional enhancement)
4. Consider adding workflow to additional agent menus (UX designer, architect)
5. Create standalone execution documentation (nice-to-have)
6. Address step numbering gap if desired (cosmetic)
---
## 6. Executive Summary & Overall Assessment
### Overall Validation Status: ✅ PRODUCTION-READY
#### Validation Scores by Category
| Category | Status | Score | Notes |
| -------------------------- | ----------- | ------ | --------------------------------------------- |
| **File Structure & Size** | ⚠️ WARNINGS | 7/10 | 3 files exceed 250-line limit, 23 approaching |
| **Frontmatter Validation** | ✅ PASS | 9/10 | One broken path reference |
| **Step Content Quality** | ✅ EXCELLENT | 9.5/10 | High-quality instructional design |
| **Documentation** | ✅ EXCELLENT | 9/10 | Comprehensive, minor inconsistencies |
| **Integration** | ✅ PASS | 9/10 | All paths correct (one issue fixed) |
| **BMAD Compliance** | ✅ EXCELLENT | 9.5/10 | Strong adherence to standards |
**Overall Score: 9.2/10 - EXCELLENT**
#### ✅ Critical Action Items - ALL RESOLVED
**ONLY ONE TRUE CRITICAL ISSUE EXISTED - NOW FIXED:**
1. **✅ FIXED: Edit Workflow Path**
- File: `workflow.md` ✓ RESOLVED
- Changed from: `./steps-e/step-e-01-assess-workflow.md`
- Changed to: `./steps-e/step-e-01-discovery.md`
**Items incorrectly flagged as critical (actually working as designed):**
- ✅ Configuration path references (installation-time placeholders)
- ✅ Planning artifacts folder (installation-time placeholder)
#### High Priority Improvements
2. **⚠️ Split Large Step Files** (>250 lines):
- `step-v-09-project-type-validation.md` (263 lines)
- `step-v-11-holistic-quality-validation.md` (264 lines)
- `step-e-03-edit.md` (253 lines)
3. **⚠️ Update Documentation Inconsistencies**:
- Fix step count reference (11 → 12 steps in create mode)
- Update edit mode status (Future → Implemented)
#### Medium Priority Enhancements
4. **Enhance PRD Template** (currently minimal at 10 lines)
5. **Add quick-start README** for new users
6. **Address step numbering gap** (cosmetic - missing step-11-complete.md)
#### Edit Mode Status - FUNCTIONALLY COMPLETE ✅
The edit workflow is **complete and well-designed** with 5 steps:
- Discovery → Legacy Conversion (branch) → Review → Edit → Complete
- Edit mode is inherently simpler than create mode (targeted improvements vs full creation)
- Uses subprocesses for complex operations
- Integrates with validation workflow
**No additional steps needed.**
### Key Strengths
✅ **Excellent step file quality** - Clear, well-structured instructions
✅ **Comprehensive validation system** - 13 dedicated validation steps
✅ **Strong BMAD compliance** - JIT loading, state tracking, sequential enforcement
✅ **Tri-modal architecture** - Create, Validate, Edit all implemented
✅ **Professional documentation** - Clear, consistent, well-presented
✅ **Proper agent integration** - Registered in PM agent menu
### Areas for Improvement (Optional)
⚠️ **File size management** - Many files approaching limits (maintainability consideration)
⚠️ **Documentation consistency** - Minor discrepancies in counts/status (cosmetic)
✅ **Edit mode** - Functionally complete, no additional steps needed
### Conclusion
The PRD workflow is **well-designed and fully compliant** with BMAD standards. The step file architecture is exemplary, the content quality is excellent, and the documentation is comprehensive. The only critical issue (edit workflow path) has been **resolved**, and all other flagged items were actually working as designed (installation-time placeholders).
**Current Status: ✅ PRODUCTION-READY**
**Recommended Optional Enhancements:**
1. Split the 3 files exceeding 250-line limit (maintainability)
2. Update documentation inconsistencies (step counts, edit mode status)
3. Enhance PRD template and add quick-start README (user experience)
The PRD workflow is ready for production use and fully compliant with BMAD workflow standards.
---
**Validation Completed:** 2026-01-08
**Validation Method:** Systematic subprocess analysis with maximum context coverage
**Validator:** BMAD Workflow Validation System (Wendy - Workflow Building Master)