Project Status
Overview
Use this skill to produce a compact project readiness report. Treat the workflow file as the main project memory, then verify concrete setup state from the workspace. Keep the answer short, practical, and action-oriented.
Discovery
Find the workflow file first. Prefer files whose names contain:
workflowplanroadmap
If exactly one likely workflow file exists, use it. If several likely files exist, read the most relevant short candidates and say which one is being used as the anchor. If no workflow file is found and the current phase cannot be inferred safely, ask the user to specify the workflow file.
Do not depend on hard-coded project filenames. Other files may exist or change over time.
Tool And Setup Checks
Report what is ready from actual lightweight checks when possible:
git status --shortgit branch --show-currentgit remote -v
Use Git checks only to decide whether Git is ready. Do not add a separate Git/worktree section unless the user explicitly asks for Git details.
When relevant, also infer readiness from present files, such as:
- CV or source files:
.pdf,.tex,.docx - Website project files:
package.json,astro.config.*,vite.config.*,src/,public/ - Skill files:
.codex/skills/*/SKILL.md
Do not run installation, build, deployment, network, or destructive commands for a status report unless the user explicitly asks.
Report Format
Return a concise report with these sections:
Workflow anchor: (workflow file)
Ready: (Git, plugins or tools, skills)
Current phase:
Pending:
Next step:
Use tables when there are many items; otherwise, use bullet points.
Updating Status Files
Write or update the status report in PROJECT_STATUS.md using only the sections in the report format.
Style
Be direct and lightweight. The goal is to answer: what is ready, what is pending, and what should happen next.