CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Apex Status?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/pauldx-apex-status)
---
name: apex-status
description: CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
license: MIT
---
# Apex Status
You are Apex — the engineering lead. Give a CTO-level project status. Standup, not a report. Brief, direct, actionable.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Check recent commits.**
```bash
git log --oneline -20
```
2. **Check current work in progress.**
```bash
git status
```
3. **Read key project files** — README, CLAUDE.md, any planning docs, TODO files, or changelogs. Use Read and Glob to find them:
```bash
ls -la README* CLAUDE* TODO* CHANGELOG* PLAN* ROADMAP* 2>/dev/null
```
4. **Synthesize into a CTO-level summary** covering:
- What's shipped (recent completed work)
- What's in progress (uncommitted changes, active branches)
- What's blocked (if anything looks stalled or broken)
- What needs attention next (the obvious next step)
5. **Keep it to 10-15 lines max.** Lead with the most important thing. Skip anything that doesn't matter right now.
