// 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.
Project-level orchestrator for intake and continuity. Turns a new/ongoing request into a governance decision (reuse vs new task, mapping to Milestone/Feature/Requirement), keeps the project hub consistent (registry/changelog/derived views), and ensures LLM-authored semantic extraction is captured in structured non-AUTO sections. Focuses on planning and coordination, not product code changes.
Project hub synchronizer and validator. Scans the repo (including multiple dev-docs roots), validates project/task metadata against the Project Contract, repairs drift by generating missing task identity meta (.ai-task.yaml) and regenerating derived views, and enforces complete task-feature mapping plus LLM-authored semantic extraction for feature-level governance.
Enable and operate the Context Awareness feature (docs/context contracts + environment registry) so LLMs can work from a verified context layer instead of ad-hoc repo scans.
Enable and operate the Packaging feature (ops/packaging conventions + ctl-pack) for building runnable artifacts (usually container images).
Enable or disable skill packs via ctl-skillpacks and re-sync provider wrappers without manually editing the manifest.
Enable and operate the CI feature (GitHub Actions / GitLab CI) with repeatable templates, artifact conventions, and opt-in delivery enablement.
| name | project-status-reporter |
| description | 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. |
Answer short user questions about current progress with an actionable, read-only report, including semantic focus when requested.
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.
Use this skill when the user asks for semantic focus, cross-feature risk, or decision context already documented in feature-map.md semantic briefs.
Do not use this skill for requests that ask to create/update tasks, change mappings, or repair metadata drift.
| 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 |
| Semantic focus | reference/semantic-focus.md |
main..ai/project/<project>/feature-map.md (Semantic Feature Briefs)dashboard.md is focus index context only, not semantic body sourcenode .ai/scripts/ctl-project-governance.mjs lint --check --project <project>node .ai/scripts/ctl-project-governance.mjs sync --apply --project <project>) in the output but do not execute the write.00-overview.md if neededunknown instead of inferringctl-project-governance sync --apply, no editing dev-docs/** / .ai/project/**)feature-map.mdFollow .ai/project/CONTRACT.md for sources of truth and status semantics.