project-status

Project Status Skill

This skill scans the SE artifacts and tickets to determine where a project stands and what should happen next.

Process

1. Check artifacts: Verify which SE documents exist:
   • .clasi/design/overview.md
   • .clasi/design/usecases.md
   • docs/architecture/ (versioned architecture documents)
2. Check sprints: Scan clasi/sprints/ for active sprints and clasi/sprints/done/ for completed sprints.
3. Scan tickets: For each active sprint, read ticket files in tickets/ and tickets/done/. Extract frontmatter status.
4. Determine stage:
   • No overview → Project not initialized
   • Overview but no use cases → Initiation in progress
   • Use cases but no architecture → Architecture needed
   • Architecture exists, no active sprint → Ready for sprint planning
   • Active sprint with open tickets → Implementation in progress
   • Active sprint, all tickets done → Sprint ready to close
   • No active sprint, done sprints exist → Maintenance mode
5. Report progress:
   • Artifacts: which exist, their status
   • Sprint: active sprint name, status, branch
   • Tickets: count by status (open, in-progress, done)
   • Next action: what should be done next
6. Identify blockers: Missing dependencies, in-progress tickets without plans, tickets with unmet depends-on.

Output

A structured status report showing current stage, artifact status, ticket progress, and recommended next action.