Project Status Reporter
Purpose
Answer short user questions about current progress with an actionable, read-only report.
Scope
Use this skill when the user wants a snapshot of project/task progress (overall or for a specific task) and the answer can be produced by reading existing tracking artifacts. Do not use this skill for requests that ask to create/update tasks, change mappings, or repair metadata drift.
Response templates
| Need | Reference |
|---|---|
| Task inventory | reference/task-list.md |
| Overall progress | reference/progress-summary.md |
| What to do next | reference/next-action.md |
| Blockers | reference/blocked-items.md |
Process
- •Identify the query type from the user request.
- •Determine the project slug:
- •Use the user-provided project if present.
- •Otherwise default to
main.
- •Read the corresponding reference document and use its Data Source command(s).
- •Optional (recommended for accuracy when hub exists): run
- •
node .ai/scripts/ctl-project-governance.mjs lint --check --project <project> - •If lint reports errors, include a remediation command (
node .ai/scripts/ctl-project-governance.mjs sync --apply --project <project>) in the output but do not execute the write.
- •
- •Generate output using the reference template.
Verification
- •Output includes at least one actionable command
- •Status counts match query results
- •Do not guess task details; read
00-overview.mdif needed
Boundaries
- •MUST NOT modify files (no
ctl-project-governance sync --apply, no editingdev-docs/**/.ai/project/**) - •MUST NOT invent task details or blocker reasons
- •MAY suggest repair commands when lint indicates drift
Contract
Follow .ai/project/CONTRACT.md for sources of truth and status semantics.