development-lifecycle-router-maintainer

Development Lifecycle Router Maintainer

Use this skill as a routing layer: choose the current lifecycle stage, name the exit bar, and hand off to the smallest capable maintainer skill or normal coding workflow.

The reason this skill exists is to prevent two expensive mistakes:

• jumping from a complaint into implementation before the correct stage is known
• calling a stage complete without the product proof or reviewer evidence that the user's request actually requires

Keep this file thin. Load the reference files below only when the current route needs them.

Reference Map

• references/route-selection.md: stage classifier, narrow-skill routing, meta-request precedence, and skill-optimization boundaries.
• references/verification-review.md: verifier gates, terminal product proof, spawned reviewer policy, reviewer lenses, agent prompt templates, and evidence ledger.
• references/special-routes.md: recovery, component lab, performance benchmark, runtime/provider contracts, and hard real-local validation.
• references/handoff-git.md: git safety, final handoff shape, acceptance blockers, and common route templates.

Fast Start

Before editing files, running long checks, spawning reviewers, or committing:

1. Inspect git status --short --branch.
2. Classify the current stage.
3. State the selected route and downstream owner in one concise update.
4. Name the artifact or proof required to leave the current stage.
5. For development work, state the full loop before editing: implementation, writer checks, verifier, final reviewers, reconciliation, and handoff. Development work enters spawn-required mode by default; the user does not need to separately ask for subagents, review, or verification.
6. Decide which references are needed for this route and read only those.

For obvious narrow requests, do not expand a lifecycle plan. Say the route, load the narrow skill, and execute it.

Non-Use Gate

Use the narrow maintainer directly when all of these are true: