keel-workflowlisted

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.
AWenSu/keel · ★ 0 · AI & Automation · score 75

Install: claude install-skill AWenSu/keel

# /keel-workflow — Development Lifecycle Router Routes any development task to the right stage skill. This file contains routing only — every behavior lives in the routed skill (single source of truth, no inlined copies to go stale). ## Stage detection → route | Signal | Stage | Invoke | |--------|-------|--------| | "I have an idea / want to build X", requirements fuzzy | DISCOVER | `keel-discover` | | Spec/requirements exist, multi-step work ahead | PLAN | `keel-plan` | | Plan exists, large/risky (>8 files, new architecture, production data) | REVIEW | `keel-plan-review` | | Plan exists and is straightforward, or reviewed plan ready | EXECUTE | `keel-execute` | | Implementation done, wrapping up / about to claim done / PR time | FINISH | `keel-finish` | | Idea too big for one session AND the route is still foggy | WAYFIND | `keel-wayfind` (decision map; exits to keel-discover once clear) | | Bug, test failure, unexpected behavior | DEBUG | `keel-debug` (loop-first: no hypothesis without a red repro command) | | Something shipped and you want to know whether it worked | SIGNALS | read the plan's `## Signals` (written at `keel-finish` Part 2d); a negative signal routes to `keel-discover`, a defect routes to `keel-debug` | | Frontend/UI task | UI | `frontend-workflow` (own router; don't mix pipelines) | | Output should be a GitHub issue / backlog item | ISSUE | gstack `spec` | | Very large plan (>15 files, new product surface) needing dual-model review | HEAVY REVIEW | gsta