sm:stage-manage

To orchestrate productive build sessions, you can use a stage management workflow that reads repository context and monitors builder activity to surface timely process suggestions, preventing premature implementation and preserving design intent.

The best workflow signals to watch for during interactive development include new unvalidated ideas, chunking without validation, drift, and untested assumptions, which indicate a need for validation, shaping, or staging interventions.

You start a session by invoking the stage manager command, which reads your project context, counts session history thresholds, and surfaces a single non-blocking follow-up skill suggestion formatted with a consistent tone and output layout.

Yes, stage management works with existing repository files by reading top-level project files such as README.md, CLAUDE.md, and replit.md, along with optional practitioner mirrors like session-journal.md, to personalize the session opening.

Yes, you can decline workflow suggestions during a development session without blocking progress because the orchestration rules enforce one non-blocking suggestion at a time and explicitly respect declined suggestions for the remainder of the session.