tonone-ai/tonone / bundle/engineering-team/skills/apex-status
apex-status
VerifiedCTO-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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
SKILL.md
View on GitHub---
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
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [engineering, orchestration, status]
---
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
# 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |