# Project Status

> Helps Codex create a clear status snapshot for any project: what it is, what already works, what is broken or unfinished, and what should happen next. Use it when you need a readable current-state document for yourself, a teammate, or a client. Trigger on requests like: "собери статус проекта", "обнови project status", "что сейчас с проектом", "status snapshot", "current state of the project".

- Skill: `aggel008/project-status` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add aggel008/project-status`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aggel008/project-status/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: aggel008 (https://skillmd.com/u/aggel008)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/aggel008/project-status

---


# 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](references/report-template.md).

## Workflow

1. Read the latest existing status doc if one exists.
2. 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
3. Prefer observed evidence over assumptions:
   - database counts
   - file paths
   - logs
   - scheduler state
   - test results
   - service state
4. 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