Apex status

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/apex-status

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.From its SKILL.md

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill apex-status

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.4 KB, 264 tokens by cl100k_base, as published. Nobody here has run it

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

Check recent commits.

git log --oneline -20

Check current work in progress.

git status

Read key project files — README, CLAUDE.md, any planning docs, TODO files, or changelogs. Use Read and Glob to find them:

ls -la README* CLAUDE* TODO* CHANGELOG* PLAN* ROADMAP* 2>/dev/null

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)
Keep it to 10-15 lines max. Lead with the most important thing. Skip anything that doesn't matter right now.

What ships with it: 1 file

431 B alongside SKILL.md

.claude-plugin/