# Project Status Reporter

> Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs), can include semantic focus extracted from LLM-authored feature briefs, and includes an actionable next command; never modifies repo files. Use when this capability is needed.

- Skill: `tomevault-io/project-status-reporter` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/project-status-reporter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/project-status-reporter/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/project-status-reporter

---


# Project Status Reporter

## Purpose
Answer short user questions about current progress with an actionable, read-only report, including semantic focus when requested.

## Scope
Use `project-status-reporter` 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.
Use `project-status-reporter` when the user asks for semantic focus, cross-feature risk, or decision context already documented in `feature-map.md` semantic briefs.
Do not use `project-status-reporter` for requests that ask to create/update tasks, change mappings, or repair metadata drift.

## Response templates

| Need | Reference |
|------|-----------|
| Task inventory | [reference/task-list.md](reference/task-list.md) |
| Overall progress | [reference/progress-summary.md](reference/progress-summary.md) |
| What to do next | [reference/next-action.md](reference/next-action.md) |
| Blockers | [reference/blocked-items.md](reference/blocked-items.md) |
| Semantic focus | [reference/semantic-focus.md](reference/semantic-focus.md) |

## Process

1. Identify the query type from the user request.
2. Determine the project slug:
   - Use the user-provided project if present.
   - Otherwise default to `main`.
3. Read the corresponding reference document and use its **Data Source** command(s).
   - For semantic questions, read semantic sections in:
     - `.ai/project/<project>/feature-map.md` (`Semantic Feature Briefs`)
   - `dashboard.md` is focus index context only, not semantic body source
4. Optional (recommended for accuracy when hub exists): run
   - `node .ai/scripts/ctl-project-governance.mjs lint --check`
   - If lint reports errors, include a remediation command (`node .ai/scripts/ctl-project-governance.mjs sync --apply`) in the output but do not execute the write.
5. 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.md` if needed
- For semantic output, quote only documented feature briefs; if missing, report `unknown` instead of inferring

## Boundaries
- MUST NOT modify files (no `ctl-project-governance sync --apply`, no editing `dev-docs/**` / `.ai/project/**`)
- MUST NOT invent task details or blocker reasons
- MUST NOT invent semantic intent/risk/scope that is not documented in `feature-map.md`
- MAY suggest repair commands when lint indicates drift

## Contract
Follow `.ai/project/CONTRACT.md` for sources of truth and status semantics.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/willyu1007) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->