Skip to main content
AI/MLjeremylongshore

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.

Stars
2,267
Source
jeremylongshore/claude-code-plugins-plus-skills
Updated
2026-05-31
Slug
jeremylongshore--claude-code-plugins-plus-skills--apex-status
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/jeremylongshore/claude-code-plugins-plus-skills/HEAD/plugins/ai-agency/tonone/skills/apex-status/SKILL.md -o .claude/skills/apex-status.md

Drops the SKILL.md into .claude/skills/apex-status.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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.
git log --oneline -20
  1. Check current work in progress.
git status
  1. 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

  1. 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)

  2. Keep it to 10-15 lines max. Lead with the most important thing. Skip anything that doesn't matter right now.