development-lifecycle-router-maintainer

What problem does it solve?

It resolves ambiguity about where a Rudder development request fits in the lifecycle (intake → requirements → advisor/UI → implementation → verification → review → handoff) by selecting the right downstream skill/workflow and defining concrete stage exit criteria.

Core Features & Use Cases

• Lifecycle stage classification with routing: Automatically chooses the earliest blocking stage and routes to the smallest matching maintainer workflow (e.g., debug, UI design, component lab, recovery, performance benchmark, release).
• Review-gated stage completion: Requires spawned reviewer evidence by default after each routed stage artifact exists, and blocks handoff when spawned reviewers are unavailable instead of substituting self-review.
• Evidence-first operational guardrails: Builds a routing packet (git state, relevant ids, changed-file ownership, local session evidence when provided) and records an evidence ledger for terminal product proof, substitutions, and blockers.
• Use case examples: When a user asks for an end-to-end dev flow with reviewer rounds, requests uncertain stage entry (“requirements vs design vs coding”), needs recovery from interrupted runs/worktrees, or wants a safe path for destructive/ambiguous cleanup.

Quick Start

Use this skill when you describe a vague or end-to-end Rudder development request and want the agent to select the lifecycle stage, route to the right workflow, and enforce spawned reviewer gates after each stage artifact.