cape

Explore a feature or design problem interactively before writing code

Enter the BUILD phase by executing the tracked plan

Create atomic git commits with conventional format

Execute plan tasks iteratively from Linear tracker epics

Verify and close a Linear tracker epic after all tasks are complete

Use this agent when a major implementation step has been completed and needs to be reviewed against the epic contract (requirements, anti-patterns, success criteria) and coding standards.

Use this agent when you need to understand current codebase state, find existing patterns, or verify assumptions about what exists. Dispatched during planning, debugging, bug fixing, task expansion, test analysis, task refinement, and notebox research.

Use this agent to verify claims, assertions, or assumptions against codebase and external evidence before acting on them. Catches hallucinated paths, wrong function signatures, and stale assumptions.

Use this agent when you need current information from the internet, API documentation, library usage patterns, or external knowledge. Dispatched during planning, debugging, and bug fixing.

Use this agent to run tests, pre-commit hooks, or commits without polluting your context with verbose output. Runs commands, captures all output, and returns only summary and failures.

Use BEFORE writing any code for new features, integrations, or system changes. Triggers when the user describes something to build, asks "how should I approach X", is unsure between approaches, or mentions adding/creating/building functionality. Also use when requirements are vague, architecture is unclear, or the task involves design decisions (e.g., choosing libraries, data models, API patterns). Do NOT use for bug fixes, straightforward code cleanup, executing existing plans, or tasks where the implementation path is already clear. This skill researches the codebase, asks Socratic questions, generates competing designs under different constraints, and produces a design summary for `cape:write-plan` to formalize into a Linear tracker epic.

Create atomic git commits with conventional commit format and selective staging. Use whenever the user wants to commit changes — explicit requests ("commit this", "make a commit", "let's commit", "/cape:commit") and implicit ones ("we're done, save this", "wrap this up"). Also use when another cape skill finishes a unit of work and needs to commit. Covers staging decisions, splitting large diffs into separate logical commits, and writing thorough commit messages that explain the change. Do NOT use for pushing, creating PRs, or branch operations.

Meta-skill that activates cape's workflow system. Injected at session start; always active and never manually triggered. Routes every task to the right cape skill and enforces workflow chains: brainstorm before planning, plan before coding, TDD during implementation, diagnosis before fixing. If a cape skill matches the user request, using it is mandatory.

Build from a Linear tracker epic, one task at a time. The counterpart to cape:write-plan: write-plan creates the epic and first sub-issue, execute-plan implements it. Triggers on: "continue", "next task", "resume", "let's go", "work on the plan", a Linear issue ID, or transitioning after planning is complete. Uses the local tracker cache for orientation and refreshes that cache after every Linear write.

Verify and close a Linear tracker epic after all tasks are complete. Use when the user says "finish the epic", "we're done", "close out the epic", all tasks are done and the user wants to close it, or execute-plan detects all success criteria appear met. Runs final verification, checks success criteria with evidence, optionally writes a minimal outcome summary to Linear, and closes the epic.

5 hooks across 3 events