codymaster 4.1.0

package/skills/cm-skill-index/SKILL.md

@@ -0,0 +1,318 @@
+---
+name: cm-skill-index
+description: "Progressive Disclosure skill index — efficient skill loading in 3 layers. Layer 1 (index, ~100 tokens) always loaded. Layer 2 (summary, ~300 tokens) loaded on context need. Layer 3 (full SKILL.md) loaded on execution only."
+---
+
+# Skill Index — Progressive Disclosure Engine
+
+> **Save 90%+ tokens.** Agents scan the index first, load full skills only when executing.
+> Inspired by Loki Mode's 3-Layer Progressive Disclosure memory architecture.
+
+## The Problem
+
+Traditional approach: Load every SKILL.md to decide which skill to use.
+- 30+ skills × ~3000 tokens each = **90,000+ tokens just for discovery**
+- Agent only needs ~500 tokens to make the choice
+- **89,500 tokens wasted on reading full skills**
+
+## The Solution: 3-Layer Loading
+
+```
+┌────────────────────────────────────────────────┐
+│ LAYER 1: INDEX (~100 tokens per skill)          │
+│ Always loaded. Quick scan. "What exists?"        │
+│ Name + Domain + Triggers + 1-line summary       │
+└─────────────────────┬──────────────────────────┘
+                      │ (match found?)
+                      v
+┌────────────────────────────────────────────────┐
+│ LAYER 2: SUMMARY (~300 tokens per skill)        │
+│ Load when choosing. "Is this the right one?"     │
+│ Description + When to use + Integration table   │
+└─────────────────────┬──────────────────────────┘
+                      │ (confirmed?)
+                      v
+┌────────────────────────────────────────────────┐
+│ LAYER 3: FULL SKILL.md (1500-5000 tokens)       │
+│ Load ONLY during execution. "How to use it."     │
+│ Complete instructions, examples, red flags       │
+└────────────────────────────────────────────────┘
+```
+
+## Layer 1: Skill Index
+
+**Always loaded by agents at session start.** Maximum 100 tokens per skill.
+
+### Engineering Swarm 🔧
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-tdd` | test, TDD, red-green-refactor | Red-Green-Refactor cycle before any implementation |
+| `cm-debugging` | bug, error, fix, debug, broken | Root cause analysis before fixing. 5-phase investigation |
+| `cm-quality-gate` | deploy, ship, verify, quality, gate | 6-gate verification: static analysis → blind review → ship |
+| `cm-test-gate` | test setup, CI, test infrastructure | Setup 4-layer test gate for any project type |
+| `cm-code-review` | review, PR, feedback, branch | Request reviews, handle feedback, complete branches |
+
+### Operations Swarm ⚙️
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-safe-deploy` | deploy, staging, production, release | Multi-gate deploy pipeline with rollback strategy |
+| `cm-identity-guard` | git push, deploy, Cloudflare, Supabase, account | Verify identity before any push/deploy to prevent wrong-account |
+| `cm-git-worktrees` | branch, isolate, worktree, parallel | Isolated git worktrees for feature work |
+| `cm-terminal` | command, terminal, run, execute | Safe terminal execution with progress logging |
+
+### Security Swarm 🔒
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-secret-shield` | secret, token, leak, security, scan, pre-commit, gitleaks, rotate | Defense-in-depth: pre-commit hooks, repo scanning, token lifecycle |
+
+### Product Swarm 🎨
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-brainstorm-idea` | analyze, enhance, improve, initiative, evaluate, review product | Strategic analysis gate: 9 Windows + Double Diamond → 2-3 qualified options |
+| `cm-planning` | plan, design, brainstorm, feature | Brainstorm intent → write implementation plan → then code |
+| `cm-ux-master` | UI, UX, design, interface, usability | 48 UX Laws + 37 Design Tests + Figma/Stitch integration |
+| `cm-ui-preview` | preview, visual, mockup, render UI, wireframe | Live UI concept generation via Google Stitch or Pencil MCP |
+| `cm-dockit` | docs, documentation, knowledge base, SOP | Generate complete knowledge base from codebase |
+| `cm-project-bootstrap` | new project, init, bootstrap, setup | Full project setup: design system → staging → CI → deploy |
+| `cm-jtbd` | customer discovery, JTBD, jobs to be done, product-market fit, why users churn | JTBD canvas: Switch Interview → Outcome Metrics → Opportunity Scoring |
+
+### Growth Swarm 📈
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-content-factory` | content, blog, article, marketing | AI content engine: research → generate → audit → deploy |
+| `cm-ads-tracker` | pixel, tracking, GTM, Meta, TikTok, Google Ads | Complete conversion tracking setup across platforms |
+| `cro-methodology` | conversion, A/B test, landing page, funnel | CRO audit: funnel mapping → persuasion → objection handling |
+
+### Orchestration Swarm 🎯
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-execution` | execute, implement, plan, RARV, batch | Execute plans: batch mode, subagent-driven, parallel, or RARV |
+| `cm-continuity` | memory, context, CONTINUITY, learnings | Working memory protocol: read at start, update at end |
+| `cm-skill-mastery` | which skill, skill list, discover, help | Meta-skill: when to invoke skills, how to create new ones |
+| `cm-safe-i18n` | translate, i18n, language, localize | Safe translation with multi-pass batching and audit gates |
+| `cm-skill-chain` | chain, pipeline, workflow, multi-step, full process | Compose skills into automated multi-step pipelines |
+| `cm-deep-search` | semantic search, find docs, large codebase, qmd | Optional power-up for semantic search across large projects |
+| `cm-readit` | audio, TTS, read aloud, voice, speech, SpeechSynthesis, MP3 player | Web audio engine — TTS reader, pre-recorded MP3 player, Voice CRO triggers |
+| `cm-how-it-work` | how does X work, explain, architecture overview | Explain how a system, feature, or codebase works |
+
+### Workflow Commands 🖥️
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `cm-start` | /cm-start, start workflow, begin objective, new task | Orchestrate full cm-* workflow from objective to production code |
+| `cm-dashboard` | /cm-dashboard, kanban, task board, show tasks, status board | Render Kanban board from cm-tasks.json — visual task overview |
+| `cm-status` | /cm-status, quick status, progress, what's next, blocked | Ultra-concise progress summary: done / next / blocked |
+
+### Planned (not yet implemented) 🧪
+
+> Skills below do not have SKILL.md files yet.
+
+| Skill | Triggers | Summary |
+|-------|----------|---------|
+| `mom-test` *(planned)* | customer interview, validate idea, leading questions | Customer interviews without leading questions |
+| `release-it` *(planned)* | production, circuit breaker, timeout, chaos | Build production-ready systems with stability patterns |
+| `medical-research` *(planned)* | medical, OB/GYN, clinical, evidence-based | Evidence-based medical writing with citation standards |
+| `tailwind-mastery` *(planned)* | Tailwind, utility-first, responsive, v4 | Tailwind CSS utilities, responsive, accessibility |
+| `pandasai-analytics` *(planned)* | DataFrame, analytics, forecast, time-series | Natural language DataFrame analysis and visual reports |
+| `google-forms-sheet` *(planned)* | Google Form, sheet, App Script | Form-to-sheet integration with auto-retry |
+
+### Community Skills Registry 🌐
+
+> **59 pre-indexed community skills** from skills.sh. Install on-demand: `npx skills add {source} --skill {name} -a antigravity`
+> If tech not listed here → fall back to `npx skills find "{keyword}"`
+
+#### 🖥️ Frontend Frameworks (10)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `react-best-practices` | vercel-labs/agent-skills | react, react performance, RSC |
+| `composition-patterns` | vercel-labs/agent-skills | react composition, compound components |
+| `react-native-guidelines` | vercel-labs/agent-skills | react native, expo, mobile app |
+| `react-native-best-practices` | callstackincubator/agent-skills | react native, expo, mobile |
+| `nextjs-app-router-patterns` | wshobson/agents | next.js, app router, RSC |
+| `react:components` | google-labs-code/stitch-skills | react components, stitch |
+| `frontend-design` | anthropics/skills | frontend architecture, patterns |
+| `angular-directives` | analogjs/angular-skills | angular, directives, components |
+| `svelte-best-practices` | community | svelte, sveltekit |
+| `astro-best-practices` | community | astro, static site, islands |
+
+#### 🎨 CSS & UI Design (8)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `web-design-guidelines` | vercel-labs/agent-skills | UI review, accessibility, UX audit |
+| `tailwind-design-system` | wshobson/agents | tailwind, design tokens, utility CSS |
+| `tailwind-v4-shadcn` | jezweb/claude-skills | tailwind v4, shadcn/ui |
+| `tailwindcss-advanced-layouts` | josiahsiegel/claude-plugin-marketplace | tailwind layouts, responsive |
+| `remotion-best-practices` | remotion-dev/skills | remotion, programmatic video |
+| `shadcn-ui-patterns` | community | shadcn, radix, component library |
+| `css-architecture` | community | CSS modules, BEM, CSS-in-JS |
+| `framer-motion` | community | animation, framer motion, gestures |
+
+#### 🗄️ Databases & ORM (9)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `supabase-postgres-best-practices` | supabase/agent-skills | supabase, postgres, RLS, SQL |
+| `prisma-database-setup` | prisma/skills | prisma, schema, migration |
+| `prisma-client-api` | prisma/skills | prisma client, type-safe queries |
+| `prisma-expert` | sickn33/antigravity-awesome-skills | prisma, advanced patterns |
+| `drizzle-orm` | community | drizzle, ORM, type-safe SQL |
+| `mongodb-patterns` | community | mongodb, mongoose, NoSQL |
+| `pinecone-db` | community | pinecone, vector DB, embeddings |
+| `turso-database` | community | turso, libSQL, edge database |
+| `planetscale` | community | planetscale, MySQL, branching |
+
+#### 🔐 Authentication (6)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `clerk-nextjs-patterns` | clerk/skills | clerk, auth, nextjs auth |
+| `clerk-auth-v5` | clerk/skills | clerk v5, middleware, session |
+| `better-auth-best-practices` | community | better-auth, auth library |
+| `next-auth-v5` | the-misfits/agent-skills | nextauth, auth.js, OAuth |
+| `auth-js-v5` | the-misfits/agent-skills | auth.js, session, JWT |
+| `supabase-auth` | community | supabase auth, RLS, magic link |
+
+#### 💳 Payments & Commerce (4)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `stripe-client` | community | stripe, payment, checkout |
+| `stripe-webhook` | community | stripe webhook, event handling |
+| `stripe-checkout` | community | stripe checkout, subscription |
+| `stripe-connect` | community | stripe connect, marketplace |
+
+#### 🧪 Testing (5)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `testing-library` | community | testing library, react testing |
+| `vitest-best-practices` | the-misfits/agent-skills | vitest, unit test, coverage |
+| `playwright-e2e` | the-misfits/agent-skills | playwright, e2e, browser test |
+| `cypress-patterns` | community | cypress, e2e, component test |
+| `testing-guidelines` | anthropics/skills | test strategy, TDD, test design |
+
+#### ☁️ Cloud & Deployment (7)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `vercel-deploy-claimable` | vercel-labs/agent-skills | vercel deploy, preview URL |
+| `vercel-deployment-best-practices` | community | vercel, edge functions, ISR |
+| `azure-deployment` | microsoft/skills | azure, cloud, Microsoft |
+| `aws-deployment` | microsoft/skills | AWS, Lambda, S3 |
+| `docker-expert` | community | docker, container, Dockerfile |
+| `docker-compose-orchestration` | community | docker compose, multi-container |
+| `multi-stage-dockerfile` | community | docker build, multi-stage, CI |
+
+#### 🤖 AI & ML (5)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `vercel-ai-sdk-best-practices` | community | AI SDK, streaming, LLM |
+| `langchain-skills` | community | langchain, agents, RAG |
+| `openai-skills` | community | openai, GPT, embeddings |
+| `tavily-search` | community | tavily, web search, research |
+| `ai-sdk-patterns` | community | AI SDK, tool calling, generative UI |
+
+#### 📡 APIs & Integrations (3)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `nextjs-supabase-auth` | sickn33/antigravity-awesome-skills | next.js + supabase, full-stack |
+| `supabase-edge-functions` | nice-wolf-studio/claude-code-supabase-skills | edge functions, Deno |
+| `nextjs-seo` | laguagu/claude-code-nextjs-skills | SEO, meta tags, sitemap |
+
+#### 📱 Mobile & Cross-Platform (2)
+
+| Skill | Source | Install Keywords |
+|-------|--------|-----------------|
+| `expo-patterns` | community | expo, EAS, mobile deploy |
+| `capacitor-patterns` | community | capacitor, ionic, hybrid app |
+
+---
+
+**Discovery Protocol:**
+```
+1. Check THIS index first (59 skills above)
+   → Match found? → npx skills add {source} --skill {name} -a antigravity
+2. No match? → npx skills find "{keyword}" on skills.sh
+3. Still nothing? → Proceed without skill, note gap in .cm-skills-log.json
+
+Trigger points:
+  - cm-start Step 0.5 (before planning)
+  - cm-planning Phase A Step 4 (scope analysis)
+  - cm-execution Pre-flight (before dispatch)
+  - cm-execution RARV (after 2 failed retries)
+```
+
+## Layer 2: Skill Summary
+
+**Loaded when an agent has matched a skill from Layer 1 and needs more context.**
+
+To access Layer 2, read the first 20 lines of the corresponding SKILL.md (frontmatter + first section).
+
+```
+Example: cm-tdd Layer 2
+  - Full name: "TDD — Test Before Write"
+  - When to Use: ALWAYS before implementing any feature or bugfix
+  - Process: Red (write failing test) → Green (minimal code) → Refactor (clean up)
+  - Integration: Works with cm-execution (subagent TDD), cm-quality-gate (coverage check)
+  - Token cost: ~4200 tokens for full skill
+```
+
+## Layer 3: Full SKILL.md
+
+**Loaded ONLY when executing.** Read the complete SKILL.md file.
+
+```bash
+# Agent loads full skill only when ready to execute
+view_file /path/to/skills/cm-tdd/SKILL.md
+```
+
+## Usage Protocol
+
+```
+1. AT SESSION START:
+   - Load this skill index (Layer 1) — costs ~2500 tokens total
+   - Now you know what 34 skills do without reading any of them
+
+2. WHEN MATCHING A TASK:
+   - Scan Layer 1 triggers to find matching skill(s)
+   - If unsure, read Layer 2 (first 20 lines of SKILL.md)
+   - Choose the best skill
+
+3. WHEN EXECUTING:
+   - Load Layer 3 (full SKILL.md) for the chosen skill
+   - Follow the skill's instructions completely
+
+4. SAVINGS:
+    - Without index: 34 × 3000 = 102,000 tokens
+    - With index: 2800 + 300 + 3000 = 6,100 tokens
+    - Saved: ~95,900 tokens (~94%)
+```
+
+## Skill Domain Mapping
+
+For dynamic agent selection (Phase 3), skills map to domains:
+
+```yaml
+engineering: [cm-tdd, cm-debugging, cm-quality-gate, cm-test-gate, cm-code-review]
+operations: [cm-safe-deploy, cm-identity-guard, cm-git-worktrees, cm-terminal, cm-safe-i18n]
+security: [cm-secret-shield]
+product: [cm-brainstorm-idea, cm-planning, cm-ux-master, cm-ui-preview, cm-dockit, cm-project-bootstrap, cm-jtbd]
+growth: [cm-content-factory, cm-ads-tracker, cro-methodology]
+orchestration: [cm-execution, cm-continuity, cm-skill-mastery, cm-skill-chain, cm-deep-search, cm-readit, cm-how-it-work]
+commands: [cm-start, cm-dashboard, cm-status]
+# planned (no SKILL.md yet): mom-test, release-it, medical-research, tailwind-mastery, pandasai-analytics, google-forms-sheet
+```
+
+## The Bottom Line
+
+**Know everything. Load nothing. Execute precisely. Save 90%+ tokens.**

package/skills/cm-skill-mastery/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: cm-skill-mastery
+description: "Meta-skill for the CodyMaster kit — when to invoke skills, how to create new skills, and skill discovery. Use at conversation start to establish skill discipline."
+---
+
+# Skill Mastery — Use + Create + Discover
+
+> **The meta-skill:** How to find, use, and create cm-* skills.
+
+## Part A: Using Skills
+
+### Rule #0: Memory First (cm-continuity)
+
+Before invoking ANY skill, ensure `cm-continuity` is active:
+
+1. Has `.cm/CONTINUITY.md` been read this session? If not → **read it first**
+2. Are there relevant learnings for the module you're about to work on? → **Load them**
+3. After skill completes → **update CONTINUITY.md**
+
+> Memory is the foundation that makes all other skills smarter. Without it, you repeat every mistake.
+
+### The Rule
+
+**Invoke relevant skills BEFORE any response or action.** Even 1% chance = check the skill.
+
+### Decision Flow
+
+```
+User message received
+  → CONTINUITY.md loaded? (Rule #0)
+    → NO: Read .cm/CONTINUITY.md first
+    → YES: Continue
+  → Might any skill apply? (even 1%)
+    → YES: Read the skill → Follow it
+    → NO: Respond directly
+```
+
+### Skill Priority
+
+1. **Process skills first** (cm-planning, cm-debugging) — determine HOW to approach
+2. **Implementation skills second** (cm-tdd, cm-safe-deploy) — guide execution
+
+### Red Flags
+
+| Thought | Reality |
+|---------|---------|
+| "This is just a simple question" | Questions are tasks. Check for skills. |
+| "I need more context first" | Skill check BEFORE clarifying questions. |
+| "The skill is overkill" | Simple things become complex. Use it. |
+| "I remember this skill" | Skills evolve. Read current version. |
+| "Let me just do this one thing first" | Check BEFORE doing anything. |
+
+### Skill Types
+
+- **Rigid** (cm-tdd, cm-debugging): Follow exactly. Don't adapt away discipline.
+- **Flexible** (cm-planning): Adapt principles to context.
+
+---
+
+## Part B: Creating Skills
+
+### When to Create
+
+- Pattern repeated across 3+ projects
+- Complex process that needs documentation
+- Team convention that should be enforced
+
+### Skill Structure
+
+```markdown
+---
+name: cm-[skill-name]
+description: "One line: when to use this skill"
+---
+
+# [Skill Title]
+
+## Overview
+What and why. Core principle.
+
+## When to Use
+Specific triggers.
+
+## The Process
+Step-by-step instructions.
+
+## Red Flags
+What NOT to do.
+
+## Integration
+How it connects to other cm-* skills.
+```
+
+### Rules
+
+```
+✅ DO:
+- Keep under 400 lines (token optimization)
+- Use tables and code blocks for density
+- Include Red Flags section
+- Reference other cm-* skills by name
+- Test skill with real scenarios before deploying
+
+❌ DON'T:
+- Write prose when a table works
+- Duplicate content from other skills (reference instead)
+- Create skills for one-time tasks
+- Exceed 600 lines without good reason
+```
+
+### Token Optimization
+
+| Technique | Saves |
+|-----------|-------|
+| Tables over prose | ~40% |
+| Code blocks over explanation | ~30% |
+| Reference other skills vs duplicate | ~50% |
+| Remove obvious examples | ~20% |
+
+---
+
+## Part C: Discovering Skills
+
+### Adaptive Skills Discovery
+
+When you encounter something you don't have a skill for:
+
+```
+1. DETECT  → "I need to do X but no matching skill"
+2. SEARCH  → npx skills find "{keyword}"
+3. REVIEW  → Read the SKILL.md — safe? relevant?
+4. ASK     → "Found skill '{name}'. Install?"
+5. INSTALL → npx skills add {source} --skill {name} -a antigravity
+6. USE     → Apply the skill
+7. LOG     → Record in .cm-skills-log.json
+```
+
+### Safety Rules
+
+- Always show user what you found before installing
+- Prefer known repos (vercel-labs/agent-skills)
+- Project-level by default, global only if agreed
+- Check `npx skills list` to avoid duplicates
+- Never override existing cm-* skills with external ones
+
+---
+
+## The CodyMaster Kit (14 skills)
+
+| # | Skill | Purpose |
+|---|-------|---------|
+| 1 | `cm-project-bootstrap` | Start new projects |
+| 2 | `cm-brainstorm-idea` | Strategic analysis gate for enhancements (9 Windows + Double Diamond) |
+| 3 | `cm-planning` | Brainstorm + write plans |
+| 4 | `cm-execution` | Execute plans (batch/subagent/parallel) |
+| 5 | `cm-tdd` | Test-driven development |
+| 6 | `cm-quality-gate` | Test + verify + frontend safety |
+| 7 | `cm-code-review` | Request + receive + finish branch |
+| 8 | `cm-safe-deploy` | 6-gate deploy pipeline |
+| 9 | `cm-safe-i18n` | i18n batching + safety |
+| 10 | `cm-debugging` | Systematic root-cause debugging |
+| 11 | `cm-terminal` | Terminal command monitoring |
+| 12 | `cm-git-worktrees` | Isolated workspaces |
+| 13 | `cm-skill-mastery` | This skill (meta) |
+| 14 | `cm-identity-guard` | Git/deploy identity safety |
+
+## The Bottom Line
+
+**Skills are discipline, not overhead. Use them. Create them. Never skip them.**

package/skills/cm-start/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: cm-start
+description: Start the CM Workflow to execute your objective from idea to production code.
+---
+
+# Command: `/cm-start [your objective]`
+
+> **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`
+    - Update `CONTINUITY.md` → set Active Goal to the new objective
+
+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}"` → review → ask user → install if approved
+    - Log any discovered skills to `.cm-skills-log.json`
+
+1. **Understand Requirements (Planning & JTBD):**
+    - Read the objective provided in the `/cm-start` command.
+    - Analyze requirements, ask clarifying questions if needed (apply `cm-planning`).
+    - Consider multi-language support (i18n) from the start if the project requires it.
+
+2. **Detect Project Level:**
+    Per `_shared/helpers.md#Project-Level-Detection`
+    - Analyze the objective to determine L0/L1/L2/L3 complexity
+    - Present detected level and recommended skill chain to the user
+    - Let user confirm or override the level
+
+3. **Execute Based on Level:**
+
+    **L0 (Micro):** Code + Test only
+    - Skip planning. Apply `cm-tdd` directly → `cm-quality-gate`
+
+    **L1 (Small):** Planning lite → Code → Deploy
+    - Apply `cm-planning` (lightweight implementation plan)
+    - Apply `cm-tdd` + `cm-execution` → `cm-quality-gate`
+
+    **L2 (Medium):** Full analysis flow
+    - Apply `cm-brainstorm-idea` if problem is ambiguous
+    - Apply `cm-planning` (full implementation plan with task breakdown)
+    - Create `cm-tasks.json` → launch RARV autonomous execution
+    - Apply `cm-quality-gate` → `cm-safe-deploy`
+
+    **L3 (Large):** Full + PRD + Architecture + Sprint
+    - Apply `cm-brainstorm-idea` (mandatory)
+    - Apply `cm-planning` with FR/NFR requirement tracing
+    - Sprint planning → `cm-tasks.json` with sprints
+    - Apply `cm-execution` (Mode E: TRIZ-Parallel for speed)
+    - Apply `cm-quality-gate` → `cm-safe-deploy`
+
+3. **Track Progress:**
+    - Create or update `cm-tasks.json` by breaking the objective into specific tasks
+    - Suggest `/cm-dashboard` for visual tracking
+    - Suggest `/cm-status` for quick terminal summary
+
+4. **Complete:**
+    Per `_shared/helpers.md#Update-Continuity`
+    - Record any new learnings or decisions made during this workflow
+
+> **Note for AI:** If this is a brand new project, suggest running `cm-project-bootstrap` first. If the working environment has a risk of accidentally switching accounts/projects, remind about `cm-identity-guard` (Per `_shared/helpers.md#Identity-Check`).

package/skills/cm-status/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: cm-status
+description: View a quick progress summary of current tasks.
+---
+
+# Command: `/cm-status`
+
+When this command is called, the AI Assistant should:
+
+1. **Read progress:** Quickly read the `task.md` file or current task state.
+2. **Brief report:** Return an ultra-concise message (1-2 sentences) indicating which task was just completed, which task is next, and whether anything is blocked by errors/bugs.
+3. No need to print the full board (save that for `/cm-dashboard`).