aggel008 Project Status
This skill writes a one-date status report for a project.
Use it when:
- you need to understand the current state quickly
- you want to document progress after a work session
- a repo has drifted and you need a reality-based snapshot
- you want a handoff document for another person
Main benefit:
- turns a messy repo into a readable status picture
- separates facts from assumptions
- makes next steps obvious
The default output path is:
docs/project_status_YYYY-MM-DD.md
Use the current local date unless the user specifies another one.
For a recommended section structure, read report-template.md.
Workflow
- Read the latest existing status doc if one exists.
- Read only the files and runtime evidence needed to answer:
- what the project is trying to become
- what already works
- what is actually true on disk today
- what is misaligned
- what should happen next
- Prefer observed evidence over assumptions:
- database counts
- file paths
- logs
- scheduler state
- test results
- service state
- Write a crisp operator-facing snapshot in prose and flat bullets.
Rules
- Distinguish accepted product direction from accidental implementation drift.
- Explicitly separate facts from interpretation.
- Include paths for important artifacts and runtime entry points.
- Do not inflate the report with code-level detail.
- When the current build is partially misaligned, say so directly.
Output Standard
A good status report should let someone answer, without opening the code:
- what this project is
- what shape it is meant to have
- what is already working
- what is currently live
- what is still wrong or incomplete
- what the next execution priorities are