skills

Bootstrap a new immutable SDD repo by copying a starter from the plugin into the current directory. Detects empty vs existing repo, helps select mode (spec / app / single) + team language + profile handling, copies the matching starter, and emits next-step git commands. Use when starting a new immutable SDD project or adding immutable configuration to an existing project. Triggers - "/immutable:init", "immutable 시작", "SDD 부트스트랩", "새 spec 레포".

Lightweight pre-implementation skill for the immutable SDD flow. After a pitch is authored (in spec or single repo) or the user explicitly opts into a no-pitch refactor/internal-work path, this skill confirms which pitch is being implemented (or acknowledges the no-pitch path), captures app-side context the pitch lacks, and writes a transient context note for the plan-review skills. Does NOT generate a design artifact — the pitch is the design artifact in immutable-prd mode. Triggers - "/immutable:design", "디자인 단계", "pitch 확인", "구현 준비".

Adversarial CEO-style review of the implementation plan. Inputs - pitch (required unless the user explicitly opts into refactor mode, in which case the skill proceeds pitch-less) AND design handoff note at `.claude/immutable/design/{slug}.md` written by `/immutable:design` (expected, warn-on-absence — NOT hard-refused; absence triggers an explicit AskUserQuestion 3-way pause+run-design / proceed-degraded / abort so the user owns the choice consciously rather than the skill silent-skipping app-side context). Pre-existing linked ADRs are referenced if present but are NOT a prerequisite — ADR-authoring triggers are surfaced as an OUTPUT of this review (Phase 3.2), not consumed as input. Walks Phase 0 nuclear scope challenge (premise / existing-code leverage / dream-state / mandatory alternatives / mode selection) and 11 review sections. Surfaces pitch-supersede and ADR-authoring triggers. Triggers - "/immutable:plan-review-ceo", "CEO 리뷰", "스코프 검토", "plan review scope".

Minimum-viable PR creation skill for the immutable SDD flow. Runs pre-ship checklist, verifies commit hygiene, runs build/test, composes a PR body that auto-includes pitch and linked ADR paths, then creates the PR via `gh pr create`. Refuses if the eng review did not APPROVE. Stops short of cross-session learnings capture and harness-policy gating — teams that want those layers should wrap this skill rather than fork it. Triggers - "/immutable:ship", "PR 만들어", "배포 준비", "ship it".

Guided authoring for append-only Architecture Decision Records (ADRs) in an immutable SDD repo. Conducts a focused interview (context, decision, consequences, alternatives), runs multi-persona adversarial review, and writes the ADR only when a 90% completeness gate passes. Use when a team makes a load-bearing technical direction that future engineers must understand. In the orchestrated SDD flow, ADRs are authored reactively — only after /immutable:plan-review-eng Phase 3 surfaces an ADR-authoring trigger, never upfront right after the pitch; the skill is also callable standalone to record an out-of-flow decision. Triggers - "/immutable:adr", "ADR 작성", "아키텍처 결정 기록", "architectural decision".

Engineering-perspective review of the implementation plan. Walks 4 sections (Architecture, Code Quality, Test Coverage, Performance) with a worktree-parallelization analysis and surfaces ADR-authoring triggers. Runs in two modes - "ceo-grounded" (when /immutable:plan-review-ceo APPROVED first; uses the CEO scope envelope) and "standalone" (no CEO note; reviews pitch directly with a built-in lightweight scope check). The design handoff note at `.claude/immutable/design/{slug}.md` written by `/immutable:design` is an expected input in BOTH modes (warn-on-absence, NOT hard-refused) — absence triggers an explicit AskUserQuestion 3-way (pause+run-design / proceed-degraded / abort) so the user owns the choice consciously. In ceo-grounded mode plan-review-ceo prompts the same warn upstream; the eng re-prompt lets the user revisit option B before eng locks in. Triggers - "/immutable:plan-review-eng", "ENG 리뷰", "엔지니어 리뷰", "engineering review".

Guided authoring for immutable, append-only PRD/pitch files. Conducts a grill-me style interview with context intake, domain-language check, multi-persona adversarial review, and a 90% completeness gate before writing any file. Use when a team needs to produce new spec/PRD content or version-update existing ones in an append-only SDD repo. Triggers - "/immutable:prd", "pitch 작성", "스펙 작성", "PRD 추가", "피치 만들어".

Migrate .immutable-prd/config.yml from config schema v2 to v3 AND migrate team profile.yml field schema (v1 to v2 in v0.5.7+). Bumps versions, copies the bundled default profile when missing, uncomments the profile pointer, and merges new schema fields into existing team profiles preserving overrides. Idempotent and zero-data-loss. Use when graduating a v0.4 repo to the v0.5 profile system or when picking up a plugin update that bumped profile_schema. Triggers - "/immutable:migrate", "v3 업그레이드", "profile 전환", "config migrate", "profile schema migration".

Heavy context-gather skill for ambiguous SDD requests. Forces premise challenge plus 3 implementation alternatives before writing anything. Output is a transient design-doc note intended as Stage 1.5 Context Intake input for `/immutable:prd`. Use when the user is exploring a new feature, the problem is fuzzy, or you sense they are about to pick option 1 without considering options 2 or 3. Triggers - "/immutable:office-hours", "오피스 아워", "premise challenge", "explore options".