| name | status-writing |
| model | sonnet |
| description | Produces an updated STATUS.md file as a single source of truth for project health — covering current state, active workstreams, blockers, and next steps. Use when: 'create a status file', 'update the project status', 'document where we are', 'what is the current state', 'create a status dashboard'. |
| category | system-health |
| triggers | ["create a status file","update the project status","document where we are","what is the current state","create a status dashboard"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"project_context","type":"string","description":"Current project context — what was done, what is active, what is blocked","required":false}] |
| outputs | [{"name":"status_document","type":"ref","format":"cas-ref","description":"Updated STATUS.md as a single source of truth covering current state, active workstreams, blockers, and next steps"}] |
Status Writer Skill
I. Philosophy
A STATUS.md file is more than a report; it is a Ritual of Bearing Witness. It is a practice of radical honesty about where a project truly is — not where we wish it were, or where it is supposed to be. It is a pause to see clearly, without judgment, the current state of our work.
This ritual combats the natural tendency for entropy and confusion to creep into complex projects. It provides a single, trusted source of truth that grounds conversations and decisions in reality. By maintaining this document with care, we cultivate transparency, accountability, and a shared understanding of our journey.
II. When to Use This Skill
- At the beginning of a new project: to establish the initial state and vision.
- At the start and end of a work session: to frame the day's work and document its outcome.
- During a weekly sync: to facilitate a high-level review of all active projects.
- Whenever there is a significant change in project status (a new blocker emerges, a major milestone is reached).
For the full 10-section comprehensive schema used in handoffs and onboarding, see the status-template skill.
III. The Status Update Workflow
Step 1: Locate or Create the STATUS.md File
Navigate to the root of the project repository. If a STATUS.md file does not exist, create one.
Decision: is this a new file or an update?
- New file: initialize all sections with placeholders and fill them using the steps below.
- Existing file: proceed to Step 2, updating only what has changed.
Step 2: Update the Header
Change the Last Updated date to the current date. Do not change the Author or Status fields unless there is a concrete reason to do so.
Step 3: Review and Update Each Section
Go through each section with these decision rules:
Vision and Purpose: Re-read it. If the purpose has changed, update it. If not, leave it untouched — this section is an anchor, not a changelog.
Current State: This is the most important section. For each area, ask:
- Has it moved from its last emoji status? If yes, update the emoji and the note.
- Has a new area emerged that isn't listed? Add a row.
- Has an area been completed or archived? Remove or mark it done.
Use the emoji key strictly:
✅ complete, 🔄 in progress, ⏸️ paused, ❌ blocked.
