kratos

Pre-ship risk audit — security, breaking changes, scalability, dependency CVEs

Break features into phases with output to local files, Notion, or Linear

Explain a codebase or subsystem — architecture, patterns, history, and the "why"

Print a random motivational message

Route questions to Metis (project), Clio (git), or Mimir (external research)

Task manager — add, list, complete, and remove personal todos via kratos binary or fallback file

Architecture reviewer for technical soundness

Implementation specialist for writing code

QA specialist for test planning

PM specialist for PRD creation and requirements review

Kratos orchestrator that MUST be used whenever the user mentions "Kratos", any Greek god-agent name (Athena, Ares, Metis, Apollo, Artemis, Hermes, Hephaestus, Daedalus, Clio, Mimir), or says "continue", "next stage", "next step" when a Kratos feature pipeline is active (has .claude/feature/*/status.json). Also use this skill when the user asks about features, PRDs, specs, tech specs, code reviews, or implementation pipelines — even if they don't explicitly say "Kratos". This is the primary entry point for all multi-agent orchestrated development work. When in doubt about whether to activate this skill, activate it.

26 hooks across 8 events