/status-report - Generate Project Status Report
Generate standardized status reports following CODITECT-STANDARD-STATUS-REPORTING.
System Prompt
EXECUTION DIRECTIVE:
When the user invokes /status-report, you MUST:
- Determine report type from arguments or prompt
- Gather project data by reading relevant documents
- Apply template from CODITECT-STANDARD-STATUS-REPORTING
- Generate report with all required sections
- Save to
docs/status-reports/with correct naming - Run validation to ensure quality compliance
Usage
# Generate initial status report
/status-report --type initial --project HCC
# Generate phase checkpoint
/status-report --type phase --project HCC --phase 2
# Generate sprint review
/status-report --type sprint --project PLATFORM --sprint 23
# Generate board update
/status-report --type board --project CODITECT --quarter 2026-Q1
# Interactive mode (prompts for options)
/status-report
Options
| Option | Description | Default |
|---|---|---|
--type | Report type: initial, phase, sprint, board, investor, incident | interactive |
--project | Project code (e.g., HCC, CODITECT) | current project |
--phase | Phase number (for phase reports) | - |
--sprint | Sprint number (for sprint reviews) | - |
--quarter | Quarter (e.g., 2026-Q1) for board/investor | - |
--output | Output path | docs/status-reports/ |
--dry-run | Preview without saving | false |
Report Types
| Type | Template | Naming Pattern |
|---|---|---|
initial | Initial Status Report | STATUS-REPORT-{PROJECT}-INITIAL.md |
phase | Phase Checkpoint | STATUS-REPORT-{PROJECT}-PHASE-{N}.md |
sprint | Sprint Review | SPRINT-REVIEW-{PROJECT}-S{NN}.md |
board | Board Update | BOARD-UPDATE-{PROJECT}-{YYYY}-Q{N}.md |
investor | Investor Report | INVESTOR-REPORT-{PROJECT}-{YYYY}-Q{N}.md |
incident | Incident Report | INCIDENT-REPORT-{PROJECT}-{ID}.md |
decision | Go/No-Go Decision | DECISION-REPORT-{PROJECT}-{GATE}.md |
Data Gathering
The command gathers data from:
| Source | Data Extracted |
|---|---|
**/PROJECT-PLAN.md | Phases, milestones, budget |
**/MASTER-PROJECT-PLAN.md | Strategic overview |
**/PILOT*.md | Current tasks, progress |
**/CHECKPOINT*.md | Previous checkpoints |
docs/research/** | Research documents count |
docs/market-research/** | Market research documents |
docs/gap-analysis/** | Gap analysis documents |
docs/adrs/** | Architecture decisions |
| Git history | Recent commits, contributors |
Output Structure
Initial Status Report
docs/status-reports/
└── STATUS-REPORT-{PROJECT}-INITIAL.md
├── Executive Summary
├── Key Metrics
├── Current State Summary
├── Core Documents Index
├── Competitive Landscape (if applicable)
├── Financial Summary
├── Critical Gaps
├── Next Steps
├── Decisions Required
├── Risk Register
└── Recommendations
Workflow
Examples
Example 1: Initial Status Report
/status-report --type initial --project HCC
Output:
✅ COMMAND COMPLETE: /status-report
Type: Initial Status Report
Project: HCC (Health Coder Canada)
File: docs/status-reports/STATUS-REPORT-HCC-INITIAL.md
Quality Score: 92/100
Sections: 12/12 required sections present
Example 2: Phase Checkpoint
/status-report --type phase --project HCC --phase 2
Output:
✅ COMMAND COMPLETE: /status-report
Type: Phase Checkpoint
Project: HCC Phase 2 (Research)
File: docs/status-reports/STATUS-REPORT-HCC-PHASE-2.md
Quality Score: 88/100
Example 3: Dry Run Preview
/status-report --type initial --project HCC --dry-run
Output:
📋 DRY RUN: Status Report Preview
# HCC - Initial Status Report
> Report Date: 2026-01-25
> Project: HCC (Health Coder Canada)
> Status: Phase 1 - Strategy
> Recommendation: CONDITIONAL GO
## Executive Summary
...
[Preview continues - not saved]
Validation
Reports are automatically validated against:
| Check | Requirement |
|---|---|
| YAML Frontmatter | Complete with required fields |
| Required Sections | All mandatory sections present |
| Status Indicators | Consistent usage (✅, ⚠️, 🔴) |
| Links | All relative links valid |
| Metrics | Include current, target, status |
| Next Steps | Have owners and dates |
Minimum Quality Score: 90/100
Success Output
✅ COMMAND COMPLETE: /status-report
Type: {Report Type}
Project: {Project Name}
File: {Output Path}
Quality Score: {Score}/100
Sections: {N}/{M} required sections
Links: {X} internal, {Y} validated
Failure Indicators
This command has FAILED if:
- ❌ Project data not found
- ❌ Template application failed
- ❌ Quality score below 80/100
- ❌ Required sections missing
- ❌ Write permission denied
Related
- Standard: CODITECT-STANDARD-STATUS-REPORTING.md
- Skill: status-report-generation
- Agent: status-report-generator
- Validator: scripts/status-report-validator.py
Command Version: 1.0.0 Created: 2026-01-25 Author: CODITECT Core Team