skill
cortex-command
Structured feature lifecycle for Claude Code: human-driven spec, agent-driven execution
Set up
Skills are installed by placing their folder where your agent loads skills.
The download comes from github.com/charleshall888/cortex-command itself, not from our server, so what you get is exactly what its author published.
Install instructions come from the README
README
synced Oct 25, 2026Cortex Command
Cortex Command is an AI workflow framework for Claude Code built on a single insight: autonomous execution is only as good as the specification that precedes it.
The front half of the lifecycle is human-driven — discovery maps the problem space, /cortex-core:refine clarifies scope and earns an approved spec, and /cortex-core:build drives that spec through plan, implement, review, and complete. (/cortex-core:dev reads a ticket's status and routes it to whichever half it needs.) Once scope is genuinely clear, run /cortex-core:build for interactive development or queue refined items for /cortex-overnight:overnight and wake up to a morning report with PRs ready to review. For a visual of the full pipeline, see docs/agentic-layer.md.
Prerequisites
- Claude Code CLI
- macOS (primary supported platform)
Quickstart
# 1. Install the cortex CLI (bootstrap installs `uv` first if missing)
curl -fsSL https://raw.githubusercontent.com/charleshall888/cortex-command/main/install.sh | sh
# 2. In Claude Code, add the marketplace and install plugins
claude /plugin marketplace add charleshall888/cortex-command
claude /plugin install cortex-core@cortex-command # Base skills + hooks
claude /plugin install cortex-backlog@cortex-command # RECOMMENDED - markdown backlog backend (required by overnight)
claude /plugin install cortex-overnight@cortex-command # OPTIONAL - autonomous overnight runs (requires cortex-backlog)
# 3. In each project, before running /refine or /build. Required per-project setup.
# Registers Cortex's umbrella path with the repo's Claude Code sandbox;
# installs validation rules, settings, demo-commands, etc.
cd <your-project>
cortex init
- Recommended: turn on Auto-Update Marketplace Plugins so the cortex CLI stays in sync with the cortex-overnight plugin. See docs/internals/auto-update.md for the two-layer architecture, component map, and release ritual.
Full setup guide: docs/setup.md.
Plugin roster
| Plugin | Description |
|---|---|
| cortex-core | REQUIRED - Interactive Claude Code skills, hooks, and CLI utilities from cortex-command for day-to-day development workflows |
| cortex-backlog | RECOMMENDED - Plain-markdown backlog tickets the cortex CLI reads and writes directly; the default backlog backend and a prerequisite for cortex-overnight. A repo can point its config at another backend (e.g. GitHub Issues), but markdown is the token-cheapest, fastest default |
| cortex-overnight | OPTIONAL - Integrates the cortex MCP server and overnight skill runner hooks to drive autonomous lifecycle execution; requires cortex-backlog (or another configured backlog backend) |
| android-dev-extras | Android development skills vendored from Google's Android Skills (Apache 2.0): R8 analyzer, edge-to-edge migration, and Android CLI orchestration |
Documentation
| Guide | Covers |
|---|---|
docs/agentic-layer.md | Full skill and hook inventory, workflow diagrams, lifecycle phase map |
docs/setup.md | Installation, plugins, customization |
docs/setup.md#authentication | Authentication setup (API key vs. OAuth token) |
docs/setup.md#upgrade--maintenance | Upgrade & maintenance (CLI reinstall, plugin update, foot-guns) |
docs/overnight.md | Autonomous overnight runner -- planning, execution, deferral, morning review |
docs/dashboard.md | Web dashboard for monitoring overnight sessions |
docs/backlog.md | Backlog YAML schema, readiness gates, overnight eligibility |
docs/interactive-phases.md | What to expect at each lifecycle phase -- questions, artifacts, flow |
docs/skills-reference.md | Per-skill detailed reference |