CKS — Claude Code Starter Kit
Version 4.4.0 | Built 2026-04-05 | 519f7ee
A Claude Code plugin providing a 5-phase feature lifecycle — from idea to production. Discover, design, sprint, review, and release with structured workflows, AI agents, and quality gates.
Install
claude /plugin add cardinalconseils/claude-starter
After install, all commands are available with the /cks: prefix.
CKS detects your project automatically on first session:
🆕 CKS — First time in this project
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
/cks:adopt → Mid-development? Adopt CKS into your current work
/cks:bootstrap → Fresh start with CKS lifecycle for this project
/cks:kickstart → Got an idea? Go from idea to scaffolded project
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Getting Started
New Project (From Scratch)
/cks:kickstart → idea → research → monetize → brand → design (ERD, schema.sql, PRD, API, architecture) → scaffold
/cks:bootstrap → scaffold → .claude/ → CLAUDE.md → .prd/ → .context/
/cks:new → start first feature → enters Phase 1
Existing Codebase (Mid-Development)
/cks:adopt → scan codebase → generate CLAUDE.md → detect secrets → create feature at sprint phase
/cks:sprint → pick up where you are → plan → build → review → QA → merge
/cks:adopt is for when you already have code and want CKS to help you ship what you're working on. It skips discovery and design, scans your git history and .env files, and drops you straight into sprint.
Commands at a Glance
Project Setup
/cks:kickstart → idea → research → monetize → brand → design (ERD, schema.sql, PRD, API, architecture) → scaffold
/cks:bootstrap → scaffold → .claude/ → CLAUDE.md → .prd/ → .context/
/cks:adopt → existing codebase → CLAUDE.md → .prd/ → feature at sprint phase
5-Phase Feature Lifecycle
Each feature goes through 5 phases. Start with /cks:new, advance with /cks:next:
/cks:new "feature" → creates feature entry → enters Phase 1
Phase 1: /cks:discover → Discovery (11 Elements)
Phase 2: /cks:design → Design (Stitch MCP screens + component specs)
Phase 3: /cks:sprint → Sprint Execution (plan → build → review → QA → UAT → merge)
Phase 4: /cks:review → Review & Retro (feedback → iteration decision)
Phase 5: /cks:release → Release Management (Dev → Staging → RC → Production)
| Command | Phase | What It Does |
|---|
/cks:discover [phase] | 1 | Gather 11 Elements: problem, stories, scope, API surface, criteria, constraints, test plan, UAT, DoD, KPIs, cross-project deps |
/cks:design [phase] | 2 | UX flows, API contract, screen generation (Stitch MCP), component specs, design review |
/cks:sprint [phase] | 3 | Sprint planning, TDD, implementation, code review, QA validation, UAT, merge |
/cks:review [phase] | 4 | Sprint review, retrospective, backlog refinement, iteration decision |
/cks:release [phase|all] | 5 | Environment promotion with quality gates: Dev → Staging → RC → Production |
Phase 4 Iteration Loop:
/cks:review → feedback →
├── "UX issues" → back to Phase 2 (Design)
├── "Logic bugs" → back to Phase 3 (Sprint)
├── "Scope changed" → back to Phase 1 (Discovery)
└── "Ready" → Phase 5 (Release)
Quick Actions — Daily Development
/cks:go build → commit → push → PR (the daily driver)
/cks:go commit stage + smart commit message
/cks:go pr commit + push + open PR
/cks:go dev auto-detect and start dev server
/cks:go build auto-detect and run build
Automation
| Command | What It Does |
|---|
/cks:next | Auto-advance to the next phase (respects iteration loop) |
/cks:autonomous | Run all 5 phases without stopping |
/cks:progress | Show 5-phase dashboard + suggest next action |
Session Management
| Command | What It Does |
|---|
/cks:sprint-start | Begin work session — load full context (CLAUDE.md, rules, PRD state, git) |
/cks:sprint-close | End work session — adherence check, capture learnings |
/cks:eod | End of day — summarize work into dated DEVLOG entry |
/cks:standup | Morning standup — recap last DEVLOG, suggest next action |
Standalone Tools
cardinalconseils