Skill2.9k estrellas del repoactualizado 5d ago

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.

Ver fuente Repositorio: tons-of-skills-marketplace

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/apex-status && cp -r /tmp/apex-status/plugins/ai-agency/tonone/skills/apex-status ~/.claude/skills/apex-status

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

# 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.

Del mismo repositorio

agency-osSkill

apexSkill

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

apex-planSkill

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

apex-reconSkill

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.

apex-reviewSkill

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

apex-takeoverSkill

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

atlasSkill

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.

atlas-adrSkill

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".