Initial commit
This commit is contained in:
Zhongwei Li
340
commands/project-init.md
Normal file
340
commands/project-init.md
Normal file
@@ -0,0 +1,340 @@
|
||||
---
|
||||
description: Initialize or validate ProjectMaster configuration for the current directory and its subdirectories
|
||||
---
|
||||
|
||||
# Initialize ProjectMaster Configuration
|
||||
|
||||
When the user runs `/project-init`, perform the following tasks:
|
||||
|
||||
## Task 1: Scan Current Directory
|
||||
|
||||
Scan the current directory and subdirectories to understand the existing structure:
|
||||
|
||||
1. **Check for RULE.md files**:
|
||||
```bash
|
||||
find . -name "RULE.md" -type f
|
||||
```
|
||||
List all RULE.md files found.
|
||||
|
||||
2. **Check for milestones.yaml**:
|
||||
```bash
|
||||
find . -name "milestones.yaml" -type f
|
||||
```
|
||||
|
||||
3. **Check for project directories**:
|
||||
Look for typical project directories:
|
||||
- meetings/
|
||||
- sprints/ or iterations/ or board/
|
||||
- docs/
|
||||
- decisions/
|
||||
|
||||
4. **Identify project structure type**:
|
||||
- Initialized ProjectMaster project (has RULE.md with ProjectMaster metadata)
|
||||
- AkashicRecords project (has RULE.md but no ProjectMaster config)
|
||||
- Uninitialized directory (no RULE.md)
|
||||
- Multiple projects (multiple RULE.md files in different subdirectories)
|
||||
|
||||
## Task 2: Report Current State
|
||||
|
||||
Present findings to the user:
|
||||
|
||||
```
|
||||
📋 ProjectMaster Configuration Scan
|
||||
|
||||
Current directory: {path}
|
||||
|
||||
🔍 Found:
|
||||
- RULE.md files: {count} ({locations})
|
||||
- milestones.yaml: {count} ({locations})
|
||||
- Project directories: {list}
|
||||
|
||||
📊 Assessment:
|
||||
{One of:}
|
||||
- ✅ ProjectMaster project detected at {path}
|
||||
- ⚠️ AkashicRecords project detected (no ProjectMaster config)
|
||||
- ℹ️ No project governance detected
|
||||
- 📁 Multiple projects detected: {count}
|
||||
```
|
||||
|
||||
## Task 3: Offer Actions
|
||||
|
||||
Based on assessment, offer appropriate actions:
|
||||
|
||||
### If ProjectMaster project detected:
|
||||
|
||||
```
|
||||
✅ ProjectMaster is initialized for this project.
|
||||
|
||||
**Configuration**:
|
||||
- Methodology: {from RULE.md}
|
||||
- Team size: {from RULE.md}
|
||||
- Documentation format: {from RULE.md}
|
||||
|
||||
**Health check**:
|
||||
- RULE.md: ✅ Present
|
||||
- milestones.yaml: ✅ Present
|
||||
- README.md: {✅ Present | ⚠️ Missing}
|
||||
- Directory structure: {✅ Complete | ⚠️ Missing directories}
|
||||
|
||||
Would you like to:
|
||||
1. Validate governance (check README.md indexes)
|
||||
2. Update RULE.md configuration
|
||||
3. View project status (/project-status)
|
||||
4. No action needed
|
||||
```
|
||||
|
||||
### If AkashicRecords project (no ProjectMaster config):
|
||||
|
||||
```
|
||||
ℹ️ This directory has AkashicRecords governance but no ProjectMaster configuration.
|
||||
|
||||
Would you like to add ProjectMaster to this project?
|
||||
|
||||
This will:
|
||||
- Add ProjectMaster-specific configuration to RULE.md
|
||||
- Create milestones.yaml
|
||||
- Create project management directories (meetings/, sprints/)
|
||||
- Maintain AkashicRecords compatibility
|
||||
|
||||
Proceed with ProjectMaster initialization?
|
||||
- Yes, initialize ProjectMaster
|
||||
- No, keep as is
|
||||
```
|
||||
|
||||
If yes, activate the `initialize-project` Skill to add ProjectMaster to the existing structure.
|
||||
|
||||
### If no governance detected:
|
||||
|
||||
```
|
||||
ℹ️ This directory is not initialized for ProjectMaster.
|
||||
|
||||
Would you like to initialize project management for this directory?
|
||||
|
||||
This will create:
|
||||
- RULE.md with project governance
|
||||
- Project directory structure (meetings/, sprints/, docs/)
|
||||
- milestones.yaml for milestone tracking
|
||||
- README.md files for navigation
|
||||
|
||||
Proceed with initialization?
|
||||
- Yes, initialize new project
|
||||
- No, cancel
|
||||
```
|
||||
|
||||
If yes, activate the `initialize-project` Skill with guided Q&A.
|
||||
|
||||
### If multiple projects detected:
|
||||
|
||||
```
|
||||
📁 Multiple projects detected:
|
||||
|
||||
1. {path1} - {Project Name or "Unnamed"}
|
||||
2. {path2} - {Project Name or "Unnamed"}
|
||||
3. {path3} - {Project Name or "Unnamed"}
|
||||
|
||||
Which project would you like to work with?
|
||||
- Select project: {1-3}
|
||||
- Initialize new project in current directory
|
||||
- Validate all projects
|
||||
- Cancel
|
||||
```
|
||||
|
||||
Handle user selection and proceed accordingly.
|
||||
|
||||
## Task 4: Validate Governance (if requested)
|
||||
|
||||
If user chooses to validate governance:
|
||||
|
||||
1. **Read RULE.md**:
|
||||
Check that all required fields are present:
|
||||
- methodology
|
||||
- team_size or team_structure
|
||||
- Document Templates section
|
||||
- Auto Workflows section
|
||||
- Directory Structure section
|
||||
|
||||
2. **Check directory structure**:
|
||||
Verify that directories specified in RULE.md exist:
|
||||
```bash
|
||||
ls -ld meetings/ sprints/ docs/ decisions/
|
||||
```
|
||||
|
||||
3. **Check README.md files**:
|
||||
Verify that README.md files exist and are up to date:
|
||||
- Project root README.md
|
||||
- meetings/README.md
|
||||
- sprints/README.md (or appropriate work tracking directory)
|
||||
- docs/README.md
|
||||
|
||||
4. **Check milestones.yaml**:
|
||||
Verify structure and required fields:
|
||||
```yaml
|
||||
project:
|
||||
name: ...
|
||||
start_date: ...
|
||||
milestones:
|
||||
- id: ...
|
||||
name: ...
|
||||
[etc.]
|
||||
```
|
||||
|
||||
5. **Report validation results**:
|
||||
```
|
||||
✅ Governance Validation Report
|
||||
|
||||
**RULE.md**: ✅ All required fields present
|
||||
**Directory Structure**: ✅ All directories exist
|
||||
**README.md Indexes**: {status}
|
||||
- Root: ✅ Present, last updated {date}
|
||||
- meetings/: ✅ Present, last updated {date}
|
||||
- sprints/: ⚠️ Outdated (last updated {date}, {count} new items)
|
||||
- docs/: ❌ Missing
|
||||
**milestones.yaml**: ✅ Valid structure
|
||||
|
||||
Issues found: {count}
|
||||
```
|
||||
|
||||
6. **Offer fixes**:
|
||||
```
|
||||
Would you like to fix issues automatically?
|
||||
- Yes, fix all issues
|
||||
- Let me fix manually
|
||||
```
|
||||
|
||||
If yes:
|
||||
- Create missing README.md files
|
||||
- Update outdated README.md indexes
|
||||
- Fix structural issues
|
||||
|
||||
## Task 5: Execute Chosen Action
|
||||
|
||||
Carry out the user's selected action:
|
||||
- If initialize: Use `initialize-project` Skill
|
||||
- If validate and fix: Perform governance updates
|
||||
- If update RULE.md: Open RULE.md for editing and guide user
|
||||
- If view status: Run `/project-status` command
|
||||
|
||||
## Notes
|
||||
|
||||
- This command provides a quick way to check and initialize ProjectMaster
|
||||
- It integrates with existing AkashicRecords projects
|
||||
- It validates governance health and offers to fix issues
|
||||
- It's safe to run repeatedly - it only makes changes with user confirmation
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Uninitialized directory
|
||||
|
||||
```
|
||||
User: /project-init
|
||||
|
||||
Claude: 📋 ProjectMaster Configuration Scan
|
||||
|
||||
Current directory: /Users/user/my-project
|
||||
|
||||
🔍 Found:
|
||||
- RULE.md files: 0
|
||||
- milestones.yaml: 0
|
||||
- Project directories: None
|
||||
|
||||
📊 Assessment:
|
||||
ℹ️ No project governance detected
|
||||
|
||||
Would you like to initialize project management for this directory?
|
||||
|
||||
This will create:
|
||||
- RULE.md with project governance
|
||||
- Project directory structure
|
||||
- milestones.yaml
|
||||
- README.md files
|
||||
|
||||
Proceed? [Yes/No]
|
||||
|
||||
User: Yes
|
||||
|
||||
Claude: Great! Let's set up your project...
|
||||
[Activates initialize-project Skill with Q&A]
|
||||
```
|
||||
|
||||
### Example 2: Existing ProjectMaster project
|
||||
|
||||
```
|
||||
User: /project-init
|
||||
|
||||
Claude: 📋 ProjectMaster Configuration Scan
|
||||
|
||||
Current directory: /Users/user/ecommerce-redesign
|
||||
|
||||
🔍 Found:
|
||||
- RULE.md files: 1 (./RULE.md)
|
||||
- milestones.yaml: 1 (./milestones.yaml)
|
||||
- Project directories: meetings/, sprints/, docs/, decisions/
|
||||
|
||||
📊 Assessment:
|
||||
✅ ProjectMaster project detected
|
||||
|
||||
**Configuration**:
|
||||
- Methodology: Scrum (2-week sprints)
|
||||
- Team size: 6
|
||||
- Documentation format: Structured with frontmatter
|
||||
|
||||
**Health check**:
|
||||
- RULE.md: ✅ Present
|
||||
- milestones.yaml: ✅ Present
|
||||
- README.md: ✅ Present, updated 2025-11-13
|
||||
- Directory structure: ✅ Complete
|
||||
|
||||
Would you like to:
|
||||
1. Validate governance
|
||||
2. Update RULE.md configuration
|
||||
3. View project status
|
||||
4. No action needed
|
||||
|
||||
User: 1
|
||||
|
||||
Claude: Running governance validation...
|
||||
|
||||
✅ Governance Validation Report
|
||||
All systems healthy! No issues found.
|
||||
```
|
||||
|
||||
### Example 3: Governance validation finds issues
|
||||
|
||||
```
|
||||
User: /project-init
|
||||
|
||||
Claude: [Scans and detects issues]
|
||||
|
||||
⚠️ Governance Validation Report
|
||||
|
||||
**Issues found**: 3
|
||||
|
||||
1. ⚠️ meetings/README.md is outdated
|
||||
- Last updated: 2025-11-01
|
||||
- 8 new meetings since then
|
||||
|
||||
2. ❌ docs/README.md is missing
|
||||
- 5 documentation files exist
|
||||
- No index found
|
||||
|
||||
3. ⚠️ milestones.yaml has invalid entry
|
||||
- milestone-3 references non-existent dependency
|
||||
|
||||
Would you like to fix these automatically?
|
||||
|
||||
User: Yes
|
||||
|
||||
Claude: Fixing issues...
|
||||
|
||||
✅ Updated meetings/README.md with 8 new entries
|
||||
✅ Created docs/README.md with index of 5 files
|
||||
⚠️ milestones.yaml issue requires manual review:
|
||||
milestone-3 depends on "milestone-x" which doesn't exist.
|
||||
Please check milestones.yaml and correct the dependency.
|
||||
|
||||
2 of 3 issues resolved. 1 requires manual attention.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
This command is the entry point for ProjectMaster setup and maintenance. It ensures projects stay healthy and well-governed.
|
||||
920
commands/project-report.md
Normal file
920
commands/project-report.md
Normal file
@@ -0,0 +1,920 @@
|
||||
---
|
||||
description: Generate comprehensive project reports in various formats (summary, sprint, milestone, velocity, full)
|
||||
---
|
||||
|
||||
# Generate Project Report
|
||||
|
||||
When the user runs `/project-report [project-name] [report-type]`, generate a comprehensive report document.
|
||||
|
||||
## Command Syntax
|
||||
|
||||
```
|
||||
/project-report # Interactive: asks for project and type
|
||||
/project-report [project-name] # Interactive: asks for type
|
||||
/project-report [project-name] [type] # Direct: generates specified report
|
||||
```
|
||||
|
||||
**Report Types**:
|
||||
- `summary` - High-level project overview (default)
|
||||
- `sprint` - Current/recent sprint detailed analysis
|
||||
- `milestone` - Milestone progress and roadmap
|
||||
- `velocity` - Team velocity and estimation analysis
|
||||
- `full` - Complete project report (all sections)
|
||||
|
||||
## Task 1: Identify Project and Report Type
|
||||
|
||||
### If no parameters provided:
|
||||
|
||||
1. **Discover projects in workspace**:
|
||||
```bash
|
||||
find . -name "RULE.md" -type f
|
||||
```
|
||||
|
||||
2. **Present project selection**:
|
||||
```
|
||||
📊 Generate Project Report
|
||||
|
||||
Select project:
|
||||
1. {Project 1 Name} ({path})
|
||||
2. {Project 2 Name} ({path})
|
||||
3. {Project 3 Name} ({path})
|
||||
|
||||
Which project? (1-3)
|
||||
```
|
||||
|
||||
3. **Present report type selection**:
|
||||
```
|
||||
Select report type:
|
||||
1. Summary - High-level overview (recommended for stakeholders)
|
||||
2. Sprint - Current sprint detailed analysis
|
||||
3. Milestone - Milestone progress and timeline
|
||||
4. Velocity - Team performance metrics
|
||||
5. Full - Comprehensive report (all sections)
|
||||
|
||||
Which type? (1-5)
|
||||
```
|
||||
|
||||
### If parameters provided:
|
||||
|
||||
Parse and validate:
|
||||
- Project name matches existing project
|
||||
- Report type is valid (summary|sprint|milestone|velocity|full)
|
||||
|
||||
## Task 2: Gather Report Data
|
||||
|
||||
Based on report type, collect relevant information:
|
||||
|
||||
### For All Report Types:
|
||||
|
||||
- Project name and basic info (from RULE.md)
|
||||
- Current date and report generation metadata
|
||||
- Project start date and duration
|
||||
|
||||
### For Summary Report:
|
||||
|
||||
- Methodology and team size
|
||||
- Current sprint/phase status
|
||||
- Milestone completion overview
|
||||
- Key achievements (last 30 days)
|
||||
- Upcoming milestones and deadlines
|
||||
- High-level risks or blockers
|
||||
|
||||
### For Sprint Report:
|
||||
|
||||
- Current or most recent sprint details
|
||||
- Sprint goal and dates
|
||||
- Story breakdown with status
|
||||
- Burndown/velocity data
|
||||
- Team assignments
|
||||
- Blockers and resolutions
|
||||
- Sprint ceremony notes (planning, review, retro)
|
||||
- Comparison with previous sprints
|
||||
|
||||
### For Milestone Report:
|
||||
|
||||
- All milestones with status
|
||||
- Timeline and roadmap
|
||||
- Dependencies between milestones
|
||||
- Progress against targets
|
||||
- Contributing sprints for each milestone
|
||||
- Risk analysis for upcoming milestones
|
||||
|
||||
### For Velocity Report:
|
||||
|
||||
- Historical sprint velocities (last 6-10 sprints)
|
||||
- Average velocity calculation
|
||||
- Velocity trends (improving/declining/stable)
|
||||
- Estimation accuracy analysis
|
||||
- Team capacity over time
|
||||
- Factors affecting velocity
|
||||
- Recommendations for future sprint planning
|
||||
|
||||
### For Full Report:
|
||||
|
||||
All of the above sections combined.
|
||||
|
||||
## Task 3: Generate Report Document
|
||||
|
||||
Create a comprehensive markdown document with proper formatting:
|
||||
|
||||
### Summary Report Format:
|
||||
|
||||
```markdown
|
||||
# Project Report: {Project Name}
|
||||
|
||||
**Report Type**: Summary
|
||||
**Generated**: {YYYY-MM-DD HH:MM}
|
||||
**Report Period**: {project_start} to {current_date}
|
||||
**Project Duration**: {X} months
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
{2-3 paragraph overview of project status, key achievements, and next steps}
|
||||
|
||||
---
|
||||
|
||||
## Project Information
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Project Name** | {name} |
|
||||
| **Methodology** | {Scrum/Kanban/etc.} |
|
||||
| **Team Size** | {size} members |
|
||||
| **Project Start** | {date} |
|
||||
| **Current Phase** | {Sprint X / Phase Y} |
|
||||
| **Status** | {On Track / At Risk / Behind} |
|
||||
|
||||
---
|
||||
|
||||
## Current Status
|
||||
|
||||
### Active Sprint/Phase
|
||||
|
||||
**{Sprint Number}: {Goal}**
|
||||
- Duration: {start_date} to {end_date}
|
||||
- Progress: {X}/{Y} stories completed ({percentage}%)
|
||||
- Status: {On Track | At Risk | Behind}
|
||||
- Days Remaining: {days}
|
||||
|
||||
### Recent Completions
|
||||
|
||||
- ✅ {Item 1}
|
||||
- ✅ {Item 2}
|
||||
- ✅ {Item 3}
|
||||
|
||||
### In Progress
|
||||
|
||||
- 🔄 {Item 1} - @{owner}
|
||||
- 🔄 {Item 2} - @{owner}
|
||||
|
||||
### Blockers
|
||||
|
||||
{If any blockers exist:}
|
||||
- ⚠️ {Blocker description} - {impact}
|
||||
|
||||
{If no blockers:}
|
||||
- None. All work proceeding smoothly.
|
||||
|
||||
---
|
||||
|
||||
## Milestone Progress
|
||||
|
||||
**Overall**: {X}/{Y} milestones completed ({percentage}%)
|
||||
|
||||
### Completed Milestones
|
||||
- ✅ {Milestone 1} - {completion_date}
|
||||
- ✅ {Milestone 2} - {completion_date}
|
||||
|
||||
### In Progress
|
||||
- 🔄 {Milestone name} - {target_date} ({progress}%)
|
||||
- Status: {On Time | At Risk | Delayed}
|
||||
|
||||
### Upcoming (Next 90 Days)
|
||||
- 📅 {Milestone name} - {target_date}
|
||||
- 📅 {Milestone name} - {target_date}
|
||||
|
||||
---
|
||||
|
||||
## Key Achievements (Last 30 Days)
|
||||
|
||||
{Extract from Recent Activity in README.md}
|
||||
|
||||
- {Date}: {Achievement}
|
||||
- {Date}: {Achievement}
|
||||
- {Date}: {Achievement}
|
||||
|
||||
---
|
||||
|
||||
## Upcoming Priorities
|
||||
|
||||
### This Month
|
||||
1. {Priority item 1}
|
||||
2. {Priority item 2}
|
||||
3. {Priority item 3}
|
||||
|
||||
### Next Month
|
||||
1. {Priority item 1}
|
||||
2. {Priority item 2}
|
||||
|
||||
---
|
||||
|
||||
## Risks and Concerns
|
||||
|
||||
{If risks exist:}
|
||||
|
||||
### High Priority
|
||||
- ⚠️ {Risk description}
|
||||
- Impact: {impact}
|
||||
- Mitigation: {mitigation plan}
|
||||
|
||||
### Medium Priority
|
||||
- {Risk description}
|
||||
|
||||
{If no major risks:}
|
||||
|
||||
No significant risks identified. Project is progressing according to plan.
|
||||
|
||||
---
|
||||
|
||||
## Team Performance
|
||||
|
||||
- **Sprint Velocity**: {average} points/sprint
|
||||
- **Completion Rate**: {percentage}% of planned work delivered
|
||||
- **Team Morale**: {from retrospective notes if available}
|
||||
|
||||
---
|
||||
|
||||
## Recommendations
|
||||
|
||||
{Based on analysis, provide 3-5 actionable recommendations}
|
||||
|
||||
1. {Recommendation 1}
|
||||
2. {Recommendation 2}
|
||||
3. {Recommendation 3}
|
||||
|
||||
---
|
||||
|
||||
## Next Steps
|
||||
|
||||
1. {Next step 1}
|
||||
2. {Next step 2}
|
||||
3. {Next step 3}
|
||||
|
||||
---
|
||||
|
||||
**Report Generated by**: ProjectMaster
|
||||
**Last Updated**: {YYYY-MM-DD HH:MM}
|
||||
```
|
||||
|
||||
### Sprint Report Format:
|
||||
|
||||
```markdown
|
||||
# Sprint Report: Sprint {Number}
|
||||
|
||||
**Project**: {Project Name}
|
||||
**Sprint Goal**: {Goal}
|
||||
**Generated**: {YYYY-MM-DD HH:MM}
|
||||
|
||||
---
|
||||
|
||||
## Sprint Overview
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Sprint Number** | {number} |
|
||||
| **Duration** | {start_date} to {end_date} |
|
||||
| **Sprint Length** | {X} weeks |
|
||||
| **Days Elapsed** | {Y} of {Z} days |
|
||||
| **Status** | {Planning / Active / Review / Completed} |
|
||||
|
||||
---
|
||||
|
||||
## Sprint Goal
|
||||
|
||||
{Detailed description of sprint goal}
|
||||
|
||||
---
|
||||
|
||||
## Story Breakdown
|
||||
|
||||
### Summary
|
||||
|
||||
| Status | Count | Story Points |
|
||||
|--------|-------|--------------|
|
||||
| ✅ Completed | {X} | {A} pts |
|
||||
| 🔄 In Progress | {Y} | {B} pts |
|
||||
| ⏸️ Not Started | {Z} | {C} pts |
|
||||
| ⚠️ Blocked | {W} | {D} pts |
|
||||
| **Total** | **{total}** | **{total_pts} pts** |
|
||||
|
||||
### Completed Stories
|
||||
|
||||
{For each completed story:}
|
||||
|
||||
#### ✅ {Story Title}
|
||||
- **Story Points**: {X}
|
||||
- **Assignee**: @{name}
|
||||
- **Completed**: {date}
|
||||
- **Description**: {brief description}
|
||||
- **Acceptance Criteria**: All met
|
||||
|
||||
---
|
||||
|
||||
### In Progress Stories
|
||||
|
||||
{For each in-progress story:}
|
||||
|
||||
#### 🔄 {Story Title}
|
||||
- **Story Points**: {X}
|
||||
- **Assignee**: @{name}
|
||||
- **Progress**: {percentage}%
|
||||
- **Status**: On track / Needs attention
|
||||
- **Next Steps**: {what's next}
|
||||
|
||||
---
|
||||
|
||||
### Blocked Stories
|
||||
|
||||
{If any blockers:}
|
||||
|
||||
#### ⚠️ {Story Title}
|
||||
- **Story Points**: {X}
|
||||
- **Assignee**: @{name}
|
||||
- **Blocker**: {blocker description}
|
||||
- **Impact**: {impact on sprint}
|
||||
- **Resolution Plan**: {plan}
|
||||
- **Owner**: @{resolution_owner}
|
||||
|
||||
---
|
||||
|
||||
## Velocity Analysis
|
||||
|
||||
- **Planned Velocity**: {planned} points
|
||||
- **Actual Velocity**: {actual} points (if sprint completed)
|
||||
- **Completion Rate**: {percentage}%
|
||||
- **Comparison to Average**: {above/below/on par} with team average of {avg} points
|
||||
|
||||
{If sprint active:}
|
||||
- **Projected Velocity**: {projected} points based on current progress
|
||||
- **On Track For**: {percentage}% completion
|
||||
|
||||
---
|
||||
|
||||
## Team Assignments
|
||||
|
||||
{For each team member:}
|
||||
|
||||
### @{member_name}
|
||||
- **Assigned**: {count} stories ({points} points)
|
||||
- **Completed**: {count} stories ({points} points)
|
||||
- **In Progress**: {count} stories
|
||||
- **Utilization**: {percentage}%
|
||||
|
||||
---
|
||||
|
||||
## Daily Progress
|
||||
|
||||
{Summary of daily updates if tracked}
|
||||
|
||||
### Week 1
|
||||
- **Mon**: {summary}
|
||||
- **Tue**: {summary}
|
||||
- **Wed**: {summary}
|
||||
- **Thu**: {summary}
|
||||
- **Fri**: {summary}
|
||||
|
||||
### Week 2
|
||||
- **Mon**: {summary}
|
||||
- ...
|
||||
|
||||
---
|
||||
|
||||
## Sprint Ceremonies
|
||||
|
||||
### Sprint Planning
|
||||
- **Date**: {date}
|
||||
- **Duration**: {X} minutes
|
||||
- **Attendees**: {list}
|
||||
- **Key Decisions**: {summary}
|
||||
- **Meeting Notes**: [Link](path/to/meeting.md)
|
||||
|
||||
{If sprint completed:}
|
||||
|
||||
### Sprint Review
|
||||
- **Date**: {date}
|
||||
- **Demos**: {count} stories demonstrated
|
||||
- **Stakeholder Feedback**: {summary}
|
||||
- **Meeting Notes**: [Link](path/to/meeting.md)
|
||||
|
||||
### Sprint Retrospective
|
||||
- **Date**: {date}
|
||||
- **What Went Well**: {summary}
|
||||
- **What Could Improve**: {summary}
|
||||
- **Action Items**: {list}
|
||||
- **Meeting Notes**: [Link](path/to/meeting.md)
|
||||
|
||||
---
|
||||
|
||||
## Blockers and Resolutions
|
||||
|
||||
{Detailed list of blockers encountered and how they were resolved}
|
||||
|
||||
| Blocker | Reported | Resolved | Duration | Impact |
|
||||
|---------|----------|----------|----------|--------|
|
||||
| {description} | {date} | {date / "Open"} | {days} | {High/Med/Low} |
|
||||
|
||||
---
|
||||
|
||||
## Sprint Health Assessment
|
||||
|
||||
**Overall Health**: {Excellent / Good / Fair / Poor}
|
||||
|
||||
**Indicators**:
|
||||
- Velocity: {On Track / Below / Above}
|
||||
- Blockers: {None / Minor / Significant}
|
||||
- Team Capacity: {Appropriate / Overloaded / Underutilized}
|
||||
- Goal Achievement: {Likely / Uncertain / Unlikely}
|
||||
|
||||
---
|
||||
|
||||
## Recommendations
|
||||
|
||||
{3-5 specific recommendations for this sprint or next}
|
||||
|
||||
1. {Recommendation}
|
||||
2. {Recommendation}
|
||||
3. {Recommendation}
|
||||
|
||||
---
|
||||
|
||||
## Related Links
|
||||
|
||||
- [Sprint Plan Document](path/to/sprint-plan.md)
|
||||
- [Sprint Planning Meeting](path/to/meeting.md)
|
||||
- [Related Milestone](path/to/milestones.yaml)
|
||||
- [Project README](../README.md)
|
||||
|
||||
---
|
||||
|
||||
**Report Generated by**: ProjectMaster
|
||||
**Last Updated**: {YYYY-MM-DD HH:MM}
|
||||
```
|
||||
|
||||
### Milestone Report Format:
|
||||
|
||||
```markdown
|
||||
# Milestone Report: {Project Name}
|
||||
|
||||
**Generated**: {YYYY-MM-DD HH:MM}
|
||||
**Report Period**: {project_start} to {current_date}
|
||||
|
||||
---
|
||||
|
||||
## Milestone Summary
|
||||
|
||||
| Metric | Value |
|
||||
|--------|-------|
|
||||
| **Total Milestones** | {total} |
|
||||
| **Completed** | {completed} ({percentage}%) |
|
||||
| **In Progress** | {in_progress} |
|
||||
| **Planned** | {planned} |
|
||||
| **Delayed** | {delayed} |
|
||||
|
||||
---
|
||||
|
||||
## Timeline Overview
|
||||
|
||||
{Text-based timeline visualization}
|
||||
|
||||
```
|
||||
Q1 2025
|
||||
├── [✅] Alpha Release (2025-02-15) ← Completed on time
|
||||
└── [✅] Internal Testing (2025-03-01) ← Completed 2 days early
|
||||
|
||||
Q2 2025
|
||||
├── [🔄] Beta Release (2025-03-31) ← In Progress (75%)
|
||||
└── [📅] Feature Freeze (2025-04-15) ← Planned (blocked by Beta)
|
||||
|
||||
Q3 2025
|
||||
├── [📅] Public Launch (2025-06-30) ← Planned
|
||||
└── [📅] 1.0 Release (2025-07-31) ← Planned
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Milestone Details
|
||||
|
||||
{For each milestone:}
|
||||
|
||||
### {Status Icon} {Milestone Name}
|
||||
|
||||
**ID**: {milestone-id}
|
||||
**Target Date**: {target_date}
|
||||
**Actual Date**: {actual_date if completed}
|
||||
**Status**: {planned / in_progress / completed / delayed}
|
||||
**Owner**: @{name}
|
||||
|
||||
**Description**:
|
||||
{milestone description}
|
||||
|
||||
**Deliverables**:
|
||||
- [X] {Deliverable 1} (if completed)
|
||||
- [🔄] {Deliverable 2} (if in progress)
|
||||
- [ ] {Deliverable 3} (if pending)
|
||||
|
||||
**Dependencies**:
|
||||
{If dependencies exist:}
|
||||
- Depends on: {dependency names}
|
||||
- Blocks: {dependent milestone names}
|
||||
|
||||
**Contributing Sprints**:
|
||||
- Sprint {X}: {contribution}
|
||||
- Sprint {Y}: {contribution}
|
||||
|
||||
**Progress**: {percentage}%
|
||||
|
||||
**Status**: {On Time / Early / Delayed by X days / At Risk}
|
||||
|
||||
{If completed:}
|
||||
**Completion Report**: [View Report](path/to/completion-report.md)
|
||||
|
||||
---
|
||||
|
||||
{Repeat for each milestone}
|
||||
|
||||
---
|
||||
|
||||
## Dependency Map
|
||||
|
||||
{Visual representation of milestone dependencies}
|
||||
|
||||
```
|
||||
Alpha Release
|
||||
└── Internal Testing
|
||||
└── Beta Release
|
||||
├── Feature Freeze
|
||||
└── Public Launch
|
||||
└── 1.0 Release
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Progress Against Roadmap
|
||||
|
||||
**Original Plan vs. Actual**:
|
||||
|
||||
| Milestone | Planned Date | Actual/Projected | Variance | Status |
|
||||
|-----------|--------------|------------------|----------|--------|
|
||||
| Alpha | 2025-02-15 | 2025-02-15 | On time | ✅ |
|
||||
| Beta | 2025-03-31 | 2025-04-05 | +5 days | ⚠️ |
|
||||
| Launch | 2025-06-30 | 2025-07-10 | +10 days | ⚠️ |
|
||||
|
||||
---
|
||||
|
||||
## Risk Analysis
|
||||
|
||||
### Milestones At Risk
|
||||
|
||||
{For milestones at risk:}
|
||||
|
||||
#### ⚠️ {Milestone Name}
|
||||
- **Risk Level**: {High / Medium / Low}
|
||||
- **Reason**: {why at risk}
|
||||
- **Impact**: {what happens if delayed}
|
||||
- **Mitigation**: {plan to get back on track}
|
||||
- **Owner**: @{responsible person}
|
||||
|
||||
---
|
||||
|
||||
## Recommendations
|
||||
|
||||
{Based on milestone analysis:}
|
||||
|
||||
1. {Recommendation for getting milestones on track}
|
||||
2. {Recommendation for risk mitigation}
|
||||
3. {Recommendation for process improvement}
|
||||
|
||||
---
|
||||
|
||||
**Report Generated by**: ProjectMaster
|
||||
**Last Updated**: {YYYY-MM-DD HH:MM}
|
||||
```
|
||||
|
||||
### Velocity Report Format:
|
||||
|
||||
```markdown
|
||||
# Velocity Report: {Project Name}
|
||||
|
||||
**Generated**: {YYYY-MM-DD HH:MM}
|
||||
**Analysis Period**: {first_sprint_date} to {current_date}
|
||||
**Sprints Analyzed**: {count}
|
||||
|
||||
---
|
||||
|
||||
## Velocity Summary
|
||||
|
||||
| Metric | Value |
|
||||
|--------|-------|
|
||||
| **Average Velocity** | {avg} story points/sprint |
|
||||
| **Highest Velocity** | {max} points (Sprint {X}) |
|
||||
| **Lowest Velocity** | {min} points (Sprint {Y}) |
|
||||
| **Standard Deviation** | {stddev} points |
|
||||
| **Trend** | {Improving / Stable / Declining} |
|
||||
|
||||
---
|
||||
|
||||
## Sprint-by-Sprint Velocity
|
||||
|
||||
| Sprint | Goal | Planned | Actual | Completion % | Status |
|
||||
|--------|------|---------|--------|--------------|--------|
|
||||
| Sprint 1 | {goal} | {planned} | {actual} | {pct}% | {icon} |
|
||||
| Sprint 2 | {goal} | {planned} | {actual} | {pct}% | {icon} |
|
||||
| Sprint 3 | {goal} | {planned} | {actual} | {pct}% | {icon} |
|
||||
| ... | ... | ... | ... | ... | ... |
|
||||
|
||||
**Total Story Points Delivered**: {total} points across {count} sprints
|
||||
|
||||
---
|
||||
|
||||
## Velocity Trend Analysis
|
||||
|
||||
{Text-based trend visualization}
|
||||
|
||||
```
|
||||
Story Points
|
||||
50 │
|
||||
45 │ ●
|
||||
40 │ ● ●
|
||||
35 │●
|
||||
30 │ ●
|
||||
25 │ ●
|
||||
└─────────────────────────
|
||||
S1 S2 S3 S4 S5 S6
|
||||
```
|
||||
|
||||
**Trend**: {Improving / Stable / Declining}
|
||||
|
||||
**Analysis**:
|
||||
{Interpret the trend:}
|
||||
- Sprint 1-2: Ramping up, team finding rhythm
|
||||
- Sprint 3-4: Peak performance, all team members fully onboarded
|
||||
- Sprint 5-6: {Slight decline due to complexity / Maintained pace / etc.}
|
||||
|
||||
---
|
||||
|
||||
## Estimation Accuracy
|
||||
|
||||
**Overall Accuracy**: {percentage}%
|
||||
|
||||
| Sprint | Estimated | Delivered | Accuracy | Notes |
|
||||
|--------|-----------|-----------|----------|-------|
|
||||
| Sprint 1 | {est} | {actual} | {pct}% | {notes} |
|
||||
| Sprint 2 | {est} | {actual} | {pct}% | {notes} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
|
||||
**Observations**:
|
||||
- {Observation about overestimation/underestimation patterns}
|
||||
- {Observation about improving accuracy over time}
|
||||
|
||||
---
|
||||
|
||||
## Factors Affecting Velocity
|
||||
|
||||
{Analyze factors that impacted velocity}
|
||||
|
||||
### Positive Factors
|
||||
- {Factor 1}: Increased velocity by ~{X}% (Sprint {Y})
|
||||
- {Factor 2}: Contributed to higher output
|
||||
|
||||
### Negative Factors
|
||||
- {Factor 1}: Reduced velocity by ~{X}% (Sprint {Y})
|
||||
- {Factor 2}: Caused delays
|
||||
|
||||
### Lessons Learned
|
||||
- {Lesson 1}
|
||||
- {Lesson 2}
|
||||
|
||||
---
|
||||
|
||||
## Team Capacity Analysis
|
||||
|
||||
**Team Size Over Time**:
|
||||
{If team size changed}
|
||||
|
||||
| Period | Team Size | Avg Velocity | Points per Person |
|
||||
|--------|-----------|--------------|-------------------|
|
||||
| Sprint 1-2 | {size} | {velocity} | {per_person} |
|
||||
| Sprint 3-5 | {size} | {velocity} | {per_person} |
|
||||
|
||||
**Observations**:
|
||||
- {How team size changes affected overall velocity}
|
||||
- {Per-person productivity trends}
|
||||
|
||||
---
|
||||
|
||||
## Story Point Distribution
|
||||
|
||||
**By Size**:
|
||||
|
||||
| Size | Count | Percentage | Avg Completion Time |
|
||||
|------|-------|------------|---------------------|
|
||||
| 1 pt | {count} | {pct}% | {X} days |
|
||||
| 2 pts | {count} | {pct}% | {X} days |
|
||||
| 3 pts | {count} | {pct}% | {X} days |
|
||||
| 5 pts | {count} | {pct}% | {X} days |
|
||||
| 8 pts | {count} | {pct}% | {X} days |
|
||||
| 13+ pts | {count} | {pct}% | {X} days |
|
||||
|
||||
**Observations**:
|
||||
- {Most common story size}
|
||||
- {Correlation between size and completion rate}
|
||||
|
||||
---
|
||||
|
||||
## Velocity Predictions
|
||||
|
||||
**For Next Sprint**:
|
||||
- **Conservative Estimate**: {avg - stddev} points
|
||||
- **Expected Estimate**: {avg} points
|
||||
- **Optimistic Estimate**: {avg + stddev} points
|
||||
|
||||
**Recommendation**: Plan for {recommended} story points in Sprint {next}
|
||||
|
||||
**Rationale**: {Based on recent trend and team capacity}
|
||||
|
||||
---
|
||||
|
||||
## Recommendations for Sprint Planning
|
||||
|
||||
{5-7 actionable recommendations based on velocity analysis}
|
||||
|
||||
1. **Story Sizing**: {recommendation about estimations}
|
||||
2. **Capacity Planning**: {recommendation about sprint commitments}
|
||||
3. **Risk Buffer**: {recommendation about buffer time}
|
||||
4. **Team Focus**: {recommendation based on patterns}
|
||||
5. **Process Improvements**: {recommendation for efficiency}
|
||||
|
||||
---
|
||||
|
||||
## Appendix: Data Sources
|
||||
|
||||
- Sprint Plans: {paths to sprint documents}
|
||||
- Sprint Retrospectives: {paths to retro notes}
|
||||
- Team Composition: {source}
|
||||
- Story Point Definitions: {link to estimation guide if exists}
|
||||
|
||||
---
|
||||
|
||||
**Report Generated by**: ProjectMaster
|
||||
**Last Updated**: {YYYY-MM-DD HH:MM}
|
||||
```
|
||||
|
||||
### Full Report:
|
||||
|
||||
Combine all sections above into one comprehensive document with table of contents.
|
||||
|
||||
## Task 4: Save and Present Report
|
||||
|
||||
1. **Create reports directory** (if doesn't exist):
|
||||
```bash
|
||||
mkdir -p reports/
|
||||
```
|
||||
|
||||
2. **Generate filename**:
|
||||
```
|
||||
reports/{report-type}-{project-name-slug}-{YYYY-MM-DD}.md
|
||||
Example: reports/summary-ecommerce-redesign-2025-11-13.md
|
||||
```
|
||||
|
||||
3. **Write report file**:
|
||||
```
|
||||
Use Write tool to create the report document
|
||||
```
|
||||
|
||||
4. **Update governance**:
|
||||
- Add entry to project README.md Recent Activity:
|
||||
```markdown
|
||||
- 2025-11-13: Generated {report-type} report
|
||||
```
|
||||
- Create or update reports/README.md:
|
||||
```markdown
|
||||
# Project Reports
|
||||
|
||||
## Recent Reports
|
||||
- [{Date}: {Report Type}](filename.md) - {Brief description}
|
||||
```
|
||||
|
||||
5. **Present confirmation**:
|
||||
```
|
||||
✅ Report Generated Successfully!
|
||||
|
||||
📄 Report Type: {type}
|
||||
📊 Project: {project name}
|
||||
📅 Generated: {date time}
|
||||
|
||||
📁 Saved to: reports/{filename}.md
|
||||
|
||||
📊 Report includes:
|
||||
{List of sections included}
|
||||
|
||||
💡 Next steps:
|
||||
- View report: Read reports/{filename}.md
|
||||
- Share with team
|
||||
- Generate different report type: /project-report {project} {other-type}
|
||||
|
||||
Would you like me to:
|
||||
- Summarize key findings from the report
|
||||
- Open the report for viewing
|
||||
- Generate another report type
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Reports are markdown documents - easy to read, share, and version control
|
||||
- Reports are timestamped - track project evolution over time
|
||||
- Each report type serves different audiences:
|
||||
- **Summary**: Executives, stakeholders
|
||||
- **Sprint**: Team, Scrum Master
|
||||
- **Milestone**: Project Manager, Product Owner
|
||||
- **Velocity**: Team, for sprint planning
|
||||
- **Full**: Comprehensive record, audits
|
||||
- Reports are generated from live data - always current
|
||||
- Reports become historical record of project progress
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Generate Summary Report
|
||||
|
||||
```
|
||||
User: /project-report
|
||||
|
||||
Claude: 📊 Generate Project Report
|
||||
|
||||
Select project:
|
||||
1. E-Commerce Redesign (./ecommerce-redesign)
|
||||
2. Mobile App (./mobile-app)
|
||||
|
||||
Which project? (1-2)
|
||||
|
||||
User: 1
|
||||
|
||||
Claude: Select report type:
|
||||
1. Summary - High-level overview
|
||||
2. Sprint - Current sprint analysis
|
||||
3. Milestone - Milestone progress
|
||||
4. Velocity - Team performance
|
||||
5. Full - Comprehensive report
|
||||
|
||||
Which type? (1-5)
|
||||
|
||||
User: 1
|
||||
|
||||
Claude: Generating summary report for E-Commerce Redesign...
|
||||
|
||||
[Gathers data, generates report]
|
||||
|
||||
✅ Report Generated Successfully!
|
||||
|
||||
📄 Report Type: Summary
|
||||
📊 Project: E-Commerce Redesign
|
||||
📅 Generated: 2025-11-13 10:30
|
||||
|
||||
📁 Saved to: reports/summary-ecommerce-redesign-2025-11-13.md
|
||||
|
||||
📊 Report includes:
|
||||
- Executive summary
|
||||
- Current sprint status (Sprint 5)
|
||||
- Milestone progress (3/7 completed)
|
||||
- Key achievements (last 30 days)
|
||||
- Risks and recommendations
|
||||
|
||||
Key Finding: Project is on track. Beta Release milestone due in 15 days with 75% progress.
|
||||
|
||||
Would you like me to summarize other key findings?
|
||||
```
|
||||
|
||||
### Example 2: Direct Command
|
||||
|
||||
```
|
||||
User: /project-report ecommerce-redesign velocity
|
||||
|
||||
Claude: Generating velocity report for E-Commerce Redesign...
|
||||
|
||||
[Analyzes last 6 sprints, calculates metrics]
|
||||
|
||||
✅ Velocity Report Generated!
|
||||
|
||||
📊 Key Findings:
|
||||
- Average Velocity: 42 points/sprint
|
||||
- Trend: Stable
|
||||
- Estimation Accuracy: 89%
|
||||
- Recommendation: Plan 40-45 points for Sprint 6
|
||||
|
||||
📁 Full report: reports/velocity-ecommerce-redesign-2025-11-13.md
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
This command transforms project data into actionable insights. Reports provide clarity for decision-making and accountability for progress.
|
||||
483
commands/project-status.md
Normal file
483
commands/project-status.md
Normal file
@@ -0,0 +1,483 @@
|
||||
---
|
||||
description: View comprehensive status of all projects in the workspace including sprints, milestones, team activity, and governance health
|
||||
---
|
||||
|
||||
# Project Status Overview
|
||||
|
||||
When the user runs `/project-status`, provide a comprehensive overview of all project activities, progress, and health.
|
||||
|
||||
## Task 1: Discover Projects
|
||||
|
||||
Scan the workspace to find all ProjectMaster-managed projects:
|
||||
|
||||
1. **Find all RULE.md files**:
|
||||
```bash
|
||||
find . -name "RULE.md" -type f
|
||||
```
|
||||
|
||||
2. **For each RULE.md found**:
|
||||
- Read the file
|
||||
- Check if it has ProjectMaster configuration (methodology field)
|
||||
- Extract project name (from RULE.md or parent directory name)
|
||||
- Note project location
|
||||
|
||||
3. **Identify primary project**:
|
||||
- If in a project directory: That project
|
||||
- If in workspace root with multiple projects: All projects
|
||||
- If single project in workspace: That project
|
||||
|
||||
## Task 2: Gather Project Data
|
||||
|
||||
For each project, collect comprehensive status information:
|
||||
|
||||
### 2.1 Basic Project Info
|
||||
|
||||
From RULE.md:
|
||||
- Project name
|
||||
- Methodology (Scrum, Kanban, Waterfall, etc.)
|
||||
- Team size
|
||||
- Start date
|
||||
|
||||
### 2.2 Current Sprint/Iteration Status
|
||||
|
||||
Read active sprint document:
|
||||
```bash
|
||||
grep -r "status: active" sprints/*/sprint-plan.md
|
||||
```
|
||||
|
||||
Extract:
|
||||
- Sprint number and goal
|
||||
- Start and end dates
|
||||
- Days remaining
|
||||
- Story completion (X/Y stories, A/B points)
|
||||
- Velocity percentage
|
||||
- Blockers (if any)
|
||||
- Team members and assignments
|
||||
|
||||
### 2.3 Milestone Status
|
||||
|
||||
Read milestones.yaml:
|
||||
- Total milestones
|
||||
- Completed milestones
|
||||
- In-progress milestones
|
||||
- Next milestone due
|
||||
- Any delayed milestones
|
||||
- Overall completion percentage
|
||||
|
||||
### 2.4 Recent Activity
|
||||
|
||||
Check Recent Activity section in project README.md:
|
||||
- Last 5-7 activities
|
||||
- Types: meetings, sprint updates, milestone completions, document additions
|
||||
|
||||
### 2.5 Team Activity
|
||||
|
||||
Scan recent content for @mentions:
|
||||
- Who's been active recently
|
||||
- Current assignments
|
||||
- Upcoming responsibilities
|
||||
|
||||
### 2.6 Governance Health
|
||||
|
||||
Quick governance check:
|
||||
- RULE.md present and valid
|
||||
- README.md files up to date
|
||||
- Directory structure intact
|
||||
- milestones.yaml valid
|
||||
|
||||
### 2.7 Upcoming Items
|
||||
|
||||
- Next sprint start (if Scrum)
|
||||
- Upcoming milestones
|
||||
- Scheduled meetings
|
||||
- Deadlines approaching
|
||||
|
||||
## Task 3: Present Status Report
|
||||
|
||||
Format and present the comprehensive status:
|
||||
|
||||
### For Single Project:
|
||||
|
||||
```
|
||||
📊 Project Status: {Project Name}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
📋 PROJECT INFO
|
||||
**Methodology**: {Scrum | Kanban | Waterfall | Agile}
|
||||
**Team**: {size} members
|
||||
**Started**: {start_date}
|
||||
**Status**: {Active | Planning | On Hold}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
🏃 CURRENT SPRINT
|
||||
**Sprint {number}**: {Goal}
|
||||
**Progress**: Day {X} of {Y} ({Z}% elapsed)
|
||||
**Stories**: {completed}/{total} completed ({A}/{B} points)
|
||||
**Velocity**: {percentage}% - {On Track | At Risk | Behind}
|
||||
|
||||
✅ Completed ({count}):
|
||||
- {Story titles}
|
||||
|
||||
🔄 In Progress ({count}):
|
||||
- {Story title} - @{owner}
|
||||
- {Story title} - @{owner}
|
||||
|
||||
⚠️ Blocked ({count}):
|
||||
- {Story title} - {blocker reason}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
🎯 MILESTONES
|
||||
**Overall Progress**: {X}/{Y} milestones ({percentage}%)
|
||||
|
||||
✅ Completed ({count}):
|
||||
- {Milestone name} ({completion_date})
|
||||
|
||||
🔄 In Progress ({count}):
|
||||
- {Milestone name} - {target_date} ({progress}%)
|
||||
|
||||
📅 Upcoming ({count}):
|
||||
- {Milestone name} - {target_date} ({days} days)
|
||||
|
||||
⚠️ At Risk:
|
||||
{If any milestones delayed or at risk}
|
||||
- {Milestone name} - {issue description}
|
||||
|
||||
**Next Milestone**: {Name} ({target_date}, {days_remaining} days)
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
👥 TEAM ACTIVITY
|
||||
{Top 3-5 most active team members in last week/sprint}
|
||||
|
||||
**@{member1}**:
|
||||
- Current: {current story/task}
|
||||
- Completed: {count} stories this sprint
|
||||
- Upcoming: {next assignment}
|
||||
|
||||
**@{member2}**:
|
||||
- Current: {current story/task}
|
||||
- Completed: {count} stories
|
||||
- Blockers: {blocker if any}
|
||||
|
||||
[Continue for other active members]
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
📅 RECENT ACTIVITY
|
||||
{Last 7 days or current sprint}
|
||||
|
||||
- {Date}: {Activity description}
|
||||
- {Date}: {Activity description}
|
||||
- {Date}: {Activity description}
|
||||
- {Date}: {Activity description}
|
||||
- {Date}: {Activity description}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
🔔 UPCOMING
|
||||
**This Week**:
|
||||
- {Upcoming item 1}
|
||||
- {Upcoming item 2}
|
||||
|
||||
**Next Week**:
|
||||
- {Upcoming item 1}
|
||||
|
||||
**Next Month**:
|
||||
- {Milestone or major deliverable}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
🏥 GOVERNANCE HEALTH
|
||||
RULE.md: ✅ Valid
|
||||
milestones.yaml: ✅ Valid
|
||||
README indexes: ✅ Up to date ({last_updated})
|
||||
Directory structure: ✅ Complete
|
||||
|
||||
**Overall Health**: {Excellent | Good | Needs Attention}
|
||||
|
||||
{If issues exist:}
|
||||
⚠️ Issues:
|
||||
- {Issue description}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
💡 QUICK ACTIONS
|
||||
- Update sprint progress: "Sprint {number} progress update"
|
||||
- Check milestone: "Milestone status for {next_milestone}"
|
||||
- Find content: "Find meetings about {topic}"
|
||||
- Generate report: "/project-report"
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
```
|
||||
|
||||
### For Multiple Projects (Workspace Overview):
|
||||
|
||||
```
|
||||
📊 Workspace Status: {count} Projects
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
📁 PROJECT: {Project 1 Name}
|
||||
Location: {path}
|
||||
Status: {Active | On Hold}
|
||||
Current: Sprint {X} - {Goal} ({progress}%)
|
||||
Next Milestone: {Name} ({date})
|
||||
Health: ✅ Good
|
||||
[Quick summary - 2-3 lines]
|
||||
|
||||
───────────────────────────────────────────────────────
|
||||
|
||||
📁 PROJECT: {Project 2 Name}
|
||||
Location: {path}
|
||||
Status: {Active}
|
||||
Current: Sprint {Y} - {Goal} ({progress}%)
|
||||
Next Milestone: {Name} ({date})
|
||||
Health: ⚠️ Needs Attention (README outdated)
|
||||
[Quick summary - 2-3 lines]
|
||||
|
||||
───────────────────────────────────────────────────────
|
||||
|
||||
[Continue for each project]
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
📊 WORKSPACE SUMMARY
|
||||
|
||||
**Total Projects**: {count}
|
||||
**Active**: {count}
|
||||
**Total Sprints in Progress**: {count}
|
||||
**Upcoming Milestones (Next 30 days)**: {count}
|
||||
**Team Members Across Projects**: {count unique}
|
||||
|
||||
**Activity Level**: {High | Medium | Low}
|
||||
- Total activities last 7 days: {count}
|
||||
- Most active project: {name}
|
||||
|
||||
**Health Status**:
|
||||
- ✅ Healthy: {count} projects
|
||||
- ⚠️ Needs Attention: {count} projects
|
||||
- ❌ Issues: {count} projects
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
💡 ACTIONS
|
||||
- View specific project: "Show status for {project_name}"
|
||||
- Detailed report: "/project-report {project_name}"
|
||||
- Validate all: "/project-init" (in each project directory)
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
```
|
||||
|
||||
### For Project in Planning Phase (No Active Sprint):
|
||||
|
||||
```
|
||||
📊 Project Status: {Project Name}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
📋 PROJECT INFO
|
||||
**Status**: Planning / Setup
|
||||
**Methodology**: {methodology}
|
||||
**Team**: {size} members
|
||||
**Initialized**: {date}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
🏃 SPRINT STATUS
|
||||
No active sprint.
|
||||
|
||||
**Backlog**: {count} items ready
|
||||
- {Item 1}
|
||||
- {Item 2}
|
||||
- {Item 3}
|
||||
|
||||
💡 Ready to start? Try:
|
||||
"Start sprint 1 for {theme}"
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
🎯 MILESTONES
|
||||
**Defined**: {count} milestones
|
||||
**Target**: {first_milestone} ({target_date})
|
||||
|
||||
📅 Roadmap:
|
||||
- {Milestone 1} - {date}
|
||||
- {Milestone 2} - {date}
|
||||
- {Milestone 3} - {date}
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
|
||||
💡 GET STARTED
|
||||
1. Plan your first sprint: "Start sprint 1"
|
||||
2. Schedule kickoff: "Create meeting notes for kickoff"
|
||||
3. Refine backlog: "Add user story for {feature}"
|
||||
|
||||
═══════════════════════════════════════════════════════
|
||||
```
|
||||
|
||||
## Task 4: Handle User Follow-ups
|
||||
|
||||
After presenting status, be ready to handle common follow-ups:
|
||||
|
||||
### Common Follow-up Requests:
|
||||
|
||||
**"Show more details on {sprint/milestone/team member}"**
|
||||
- Activate appropriate Skill (manage-sprint, track-milestone) to provide detailed view
|
||||
|
||||
**"What's blocking us?"**
|
||||
- Extract and present all blockers from sprints and milestones
|
||||
|
||||
**"Who's working on what?"**
|
||||
- Present detailed team assignment breakdown
|
||||
|
||||
**"Show me last week's activity"**
|
||||
- Time-filtered activity view
|
||||
|
||||
**"Generate a report"**
|
||||
- Redirect to `/project-report` command
|
||||
|
||||
**"What should we focus on?"**
|
||||
- Analyze status and provide recommendations based on:
|
||||
- Blockers needing resolution
|
||||
- At-risk milestones
|
||||
- Sprint health
|
||||
- Upcoming deadlines
|
||||
|
||||
## Task 5: Provide Recommendations
|
||||
|
||||
Based on status analysis, offer actionable recommendations:
|
||||
|
||||
### If Sprint Behind Schedule:
|
||||
```
|
||||
⚠️ Recommendation: Sprint {number} is behind schedule
|
||||
|
||||
Current: {X}% complete with {Y}% time remaining
|
||||
|
||||
Suggestions:
|
||||
- Review blockers in next standup
|
||||
- Consider descoping lower-priority stories
|
||||
- Allocate additional resources to critical stories
|
||||
- Plan time for recovery in next sprint
|
||||
```
|
||||
|
||||
### If Milestone at Risk:
|
||||
```
|
||||
⚠️ Recommendation: {Milestone name} at risk
|
||||
|
||||
Target: {date} ({days} days)
|
||||
Progress: {percentage}% ({behind/on track})
|
||||
|
||||
Suggestions:
|
||||
- Prioritize milestone-critical stories
|
||||
- Review sprint allocations
|
||||
- Consider extending milestone deadline
|
||||
- Add checkpoint meeting: "Create meeting for milestone review"
|
||||
```
|
||||
|
||||
### If No Recent Activity:
|
||||
```
|
||||
ℹ️ Notice: Low activity in last {days} days
|
||||
|
||||
Last activity: {date} - {description}
|
||||
|
||||
Suggestions:
|
||||
- Resume work: "Start sprint {number}"
|
||||
- Update project status
|
||||
- Archive if project completed
|
||||
- Mark project on hold if paused
|
||||
```
|
||||
|
||||
### If Governance Issues:
|
||||
```
|
||||
⚠️ Governance needs attention
|
||||
|
||||
Issues:
|
||||
- README indexes outdated
|
||||
- {count} directories missing README
|
||||
- milestones.yaml has validation errors
|
||||
|
||||
Suggestion:
|
||||
Run "/project-init" to validate and fix governance
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- This command provides executive-level visibility into project health
|
||||
- It aggregates data from multiple sources (RULE.md, sprints, milestones, meetings)
|
||||
- It highlights both progress and issues
|
||||
- It's safe to run frequently - read-only operation
|
||||
- It works for single projects or workspace with multiple projects
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Healthy Active Project
|
||||
|
||||
```
|
||||
User: /project-status
|
||||
|
||||
Claude: 📊 Project Status: E-Commerce Redesign
|
||||
|
||||
[Shows complete status with all sections]
|
||||
|
||||
Current Sprint: On Track ✅
|
||||
Next Milestone: 15 days away
|
||||
Team: Fully assigned
|
||||
Governance: Healthy ✅
|
||||
|
||||
Overall: Project is progressing well. Keep momentum!
|
||||
```
|
||||
|
||||
### Example 2: Project with Issues
|
||||
|
||||
```
|
||||
User: /project-status
|
||||
|
||||
Claude: 📊 Project Status: Mobile App
|
||||
|
||||
[Shows status]
|
||||
|
||||
⚠️ Alerts:
|
||||
- Sprint 5 at 50% complete with only 2 days remaining
|
||||
- 2 stories blocked on external dependencies
|
||||
- Beta Release milestone at risk (3 days behind)
|
||||
|
||||
Recommendations:
|
||||
1. Review blockers urgently
|
||||
2. Descope non-critical Sprint 5 stories
|
||||
3. Reassess Beta Release date
|
||||
|
||||
Would you like to:
|
||||
- Review blocked stories in detail
|
||||
- Update milestone dates
|
||||
- Generate risk report
|
||||
```
|
||||
|
||||
### Example 3: Multiple Projects
|
||||
|
||||
```
|
||||
User: /project-status
|
||||
|
||||
Claude: 📊 Workspace Status: 3 Projects
|
||||
|
||||
PROJECT: E-Commerce Redesign
|
||||
✅ Healthy | Sprint 5 (75%) | Beta: 15 days
|
||||
|
||||
PROJECT: Mobile App Rewrite
|
||||
⚠️ At Risk | Sprint 3 (40%) | MVP: OVERDUE
|
||||
|
||||
PROJECT: Internal Tools
|
||||
✅ Healthy | Kanban (12 cards active) | No milestones
|
||||
|
||||
SUMMARY:
|
||||
2 of 3 projects healthy
|
||||
1 project needs immediate attention (Mobile App)
|
||||
|
||||
Focus: Mobile App MVP is overdue. Review?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
This command is the project dashboard - quick visibility into everything that matters.
|
||||
Reference in New Issue
Block a user