CORE SKILL - Must be called by ALL other skills to update project status. Maintains global project state, feature progress, and action log. Triggers on "Show status", "Project status", "What's the status".
THIS SKILL MUST BE INTEGRATED INTO ALL OTHER SKILLS.
Every skill that modifies project state must call status-reporter functions to maintain consistent project status.
docs/project-status.mddocs/features/_index.mddocs/features/FEAT-XXX/status.mddocs/status-log.mddocs/
├── project-status.md <- Global project dashboard
├── status-log.md <- Chronological action log
└── features/
├── _index.md <- All features dashboard
└── FEAT-XXX/
└── status.md <- Individual feature status
EVERY skill must update status at these points:
| Skill | When to Update | What to Update |
|---|---|---|
project-interview | After completing | project-status.md (Phase 0 progress) |
architecture-designer | After each ADR | project-status.md (Phase 0 progress) |
mvp-planner | After creating features | project-status.md, _index.md |
spec-architect | After feature interview | FEAT-XXX/status.md, _index.md |
implementation-planner | After generating plan | FEAT-XXX/status.md, _index.md |
implementer | After EACH task | FEAT-XXX/status.md, _index.md, tasks.md |
fork-feature | After creating fork | FEAT-XXX/status.md |
git-automator | After PR/merge | FEAT-XXX/status.md, _index.md |
Skills should conceptually call these functions:
update_task_complete(feature_id, task_description)update_phase_complete(feature_id, phase_name)update_blocker(feature_id, blocker_description)update_feature_complete(feature_id)STATUS CONSISTENCY RULES
1. NEVER complete an action without updating status
No orphan work - everything is tracked
2. Status updates are ATOMIC
Update ALL relevant files in one go
3. Timestamps are required
Every status change needs a timestamp
4. Progress must be calculable
X/Y format, not vague "almost done"
5. Blockers are visible
Blocked status appears in ALL dashboards
6. Log is append-only
Never delete from status-log.md