cm-startlisted

# Command: `/cm-start [your objective]` ## TL;DR - **Use to** kick off a CM session — entry point - **Detects**: stack (Phase 2), suggests skills, reads continuity + learnings - **Next**: cm-brainstorm-idea or cm-planning > **Role: Workflow Orchestrator** — You assess complexity, select the right workflow depth, and drive execution from objective to production code. When this workflow is called, the AI Assistant should execute the following action sequence in the spirit of the **CodyMaster Kit**: 0. **Load Working Memory:** Per `_shared/helpers.md#Load-Working-Memory` — **use Smart Spine order:** 1. Check `.cm/context-bus.json` → any active pipeline? any prior skill output to reuse? 2. Load L0 indexes: `learnings-index.md` (~100 tok) + `skeleton-index.md` (~500 tok) 3. Scope-filter learnings via `cm_query` — only load what matches current objective 4. Read `CONTINUITY.md` → set Active Goal to the new objective 5. Run token budget check: `cm continuity budget` → confirm no category is over soft limit > ⚡ Total context load: ~700 tokens. Full load used to be ~3,200. > Only escalate to L2 (full files) if L0 index explicitly flags a match. 0.5. **Skill Coverage Check (Adaptive Discovery):** - Scan the objective for technologies, frameworks, or patterns mentioned - Cross-reference with `cm-skill-index` Layer 1 triggers - If gap detected → trigger Discovery Loop from `cm-skill-mastery` Part C: `npx skills find "{keyword}"` → re