AWenSu

keel-debug

Use when something is broken, throwing, failing, flaky, or slow and the cause is not already known — a disciplined diagnosis loop that forbids guessing before a reproduction exists. Debug lane of the keel pipeline; replaces the superpowers:systematic-debugging routing.

keel-discover

Use when starting any feature, change, or project whose requirements are not yet nailed down — turns a vague idea into a user-approved, evidence-grounded spec before any code is written, including a prior-art scan of what already exists outside the repo. Also the re-entry point when shipped work's Signals came back negative — the requirement was wrong, not the code. Stage 1 of the keel pipeline; hands off to keel-plan.

keel-execute

Use when a reviewed plan is ready to implement — orchestrates subagent-driven execution with per-task review and a crash-safe progress ledger, or falls back to inline execution when subagents aren't available. Stage 4 of the keel pipeline; hands off to keel-finish.

keel-finish

Use when implementation appears complete, before claiming done, committing final work, or opening a PR — enforces fresh verification evidence for every claim, exercises the change end-to-end, names the signals that would later show it worked or that the requirement was wrong, then integrates the branch. Stage 5 (final) of the keel pipeline.

keel-plan-review

Use after keel-plan produces a plan for large or risky work — runs multi-lens automated review (business, engineering, plus design/DX/security when in scope) with adversarial verification, auto-deciding routine choices and escalating only genuine judgment calls. Stage 3 of the keel pipeline; hands off to keel-execute.

keel-plan

Use when you have an approved spec or clear requirements for a multi-step task, before touching code — produces a plan file precise enough that an engineer with zero codebase context could execute it. Stage 2 of the keel pipeline; hands off to keel-plan-review (large tasks) or keel-execute.

keel-wayfind

Use when a piece of work is too big for one session AND the route to it is still foggy — chart it as a local map of decision tickets, then resolve them one per session until the way is clear. Pre-stage of the keel pipeline; hands off to keel-discover or keel-plan once the fog is gone.

keel-workflow

Software development lifecycle orchestrator — detects the current stage and routes to the matching keel-* pipeline skill (keel-discover → keel-plan → keel-plan-review → keel-execute → keel-finish), with lanes for debugging, UI work, issue-driven work, and heavyweight review. Pure router; contains no duplicated skill content.