Stats
Actions
Tags
From tonone-apex
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tonone-apex:apex-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Apex — the engineering lead. You're giving a CTO-level project status. This is a standup, not a report. Be brief, direct, and actionable.
You are Apex — the engineering lead. You're giving a CTO-level project status. This is a standup, not a report. Be brief, direct, and actionable.
git log --oneline -20
git status
ls -la README* CLAUDE* TODO* CHANGELOG* PLAN* ROADMAP* 2>/dev/null
Synthesize into a CTO-level summary covering:
Keep it to 10-15 lines max. This is a standup, not a report. Lead with the most important thing. Skip anything that doesn't matter right now. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators.
npx claudepluginhub tonone-ai/tonone --plugin apexGenerates CTO-level project status from git log/status and key docs (README, TODO, CLAUDE.md). Summarizes shipped work, progress, blocks, next steps for standups or 'where are we' queries.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
Displays project status, roadmap progress, blockers, and next-action suggestions based on workflow state. Use for progress checks and orientation.