Next Step

Purpose

Every other skill in this suite does one stage of the lifecycle well. This skill answers the question that sits between them: "where is the work right now, and which skill continues it?"

It exists for three situations:

1. Resuming — a new session, a handoff, or a return after time away. The plans/ directory holds the state; this skill reads it and picks up the thread.
2. Routing — a request that doesn't obviously map to one skill ("make the app better", "handle this ticket", "we need to improve search"). This skill classifies it and routes it using the canonical routing table.
3. Status — "how far along are we?" answered with computed numbers, not impressions.

It is read-only with one purpose: orient, then hand off. It never writes plan artifacts, never implements, and never skips the skill it routes to.

The Lifecycle

The full lifecycle and the canonical routing table are defined once in shared conventions: