mit einem Klick
project-status-reporter
// Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs) and includes an actionable next command; never modifies repo files.
// Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs) and includes an actionable next command; never modifies repo files.
Use only in repos that still include the `init/` bootstrap kit to produce Stage A/B/C artifacts, update skill pack selection, and sync provider skill wrappers.
Create a goal-aligned macro-level roadmap artifact (dev-docs/active/<task>/roadmap.md) by asking clarifying questions and recording assumptions; planning only (no code changes).
Build a complete, production-embedded Agent module for a real feature request (API + optional worker/sdk/cron/pipeline), including blueprint, scaffolded runtime, prompt pack, docs, and registry entry. Enforces explicit user approvals, no-secrets-in-repo, fixed API route names (run/health), and conversation/memory strategy decisions.
Entry workflow for LLM engineering tasks (provider integration, calling wrapper, routing profiles, prompt templates, cost/telemetry, credentials/config keys). Routes to one procedure and enforces required verification.
Define and execute a distinctive visual direction for net-new UI or brand refresh work (art direction, typography, color, motion, composition), then deliver a polished reference implementation. Primary intent: creative design direction and visual differentiation; pairs well with style-frontend-ui and build-react-components for engineering hardening.
GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.
| name | project-status-reporter |
| description | Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs) and includes an actionable next command; never modifies repo files. |
Answer short user questions about current progress with an actionable, read-only report.
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.
| 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 |
main.node .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 neededctl-project-governance sync --apply, no editing dev-docs/** / .ai/project/**)Follow .ai/project/CONTRACT.md for sources of truth and status semantics.