Command
Crystallize interview results into an IMMUTABLE seed spec (YAML). Run ONLY after /interview reaches ambiguity ≤ 0.2. Extracts ontology, AC, constraints. Once created, seeds cannot be modified — only versioned.
Command
Generate layer-aware technical design document from seed spec. USE AFTER /seed and BEFORE /decompose. Maps features to 3-tier architecture, surfaces discussion points before final design.
Command
USE WHEN stuck on a bug, architecture decision, or recurring failure. Applies 5 perspectives sequentially (Researcher → Architect → Contrarian → Simplifier → Hacker) to break deadlock.
Command
Command "bdd-feature" from studioKjm/ai-harness-template, covering /bdd-feature — bdd feature management, usage and feature 작성 템플릿.
Command
A command for writing and tracking BDD scenarios using Given, When, and Then steps. BDD, or behaviour-driven development, describes expected user behaviour in examples that can be checked during implementation.
Command
Switch the active reasoning persona (analyst | ux-designer | pm-strict). Provided by the BMAD-lite methodology.
Command
Decompose a feature into BMAD-style user stories with acceptance criteria. Provided by the BMAD-lite methodology.
Command
Um comando para manter um glossário compartilhado de termos do domínio, alinhando os nomes usados pela equipe, pelo código e pelas APIs.
Command
Domain-Driven Design 핵심 산출물(Bounded Context, Aggregate, Domain Event, Glossary)을 관리합니다.
Command
Capture learnings from a closed spike and optionally promote them to ADR or seed evolution. Provided by the Exploration methodology.
Command
Create or manage time-boxed spikes (research investigations) with sandbox exempt from spec/boundary gates. Provided by the Exploration methodology.
Command
Add or resolve action items on an incident. Provided by the Incident Review methodology.
Command
Analyze recurring root causes and contributing factors across incidents. Provided by the Incident Review methodology.
Command
Manage incident records — blameless postmortem capture with state machine. Provided by the Incident Review methodology.
Command
Methodology: lean-mvp Purpose: Build→Measure→Learn cycle. One metric. Pivot or persist.
Command
Semantic diff between two seed versions (entities, AC, actions, constraints, architecture). Provided by the Living Spec methodology. Use after /seed creates seed-vN+1 to understand what changed since seed-vN.
Command
Classify existing decompose tasks against a new seed version. Outputs task-migration-plan.yaml with categories (unchanged/modified/deprecated/added). Provided by the Living Spec methodology.
Command
Methodology: mikado-method Purpose: Tree-based incremental refactoring. Try → fail → revert → discover prerequisites → solve leaves first.
Command
Manage Service Level Objectives (SLO) — define, activate, retire, track violations. Provided by the Observability First methodology.
Command
Define observability spec (metrics/logs/traces) for a target before implementation. Provided by the Observability First methodology.
Command
Advance a parallel-change plan from migrate to contract phase, verifying zero callers reference the old signature. Provided by the Parallel Change methodology.
Command
Verify the expand phase of a parallel-change plan — both old and new signatures must coexist in the codebase. Provided by the Parallel Change methodology.
Command
Advance a parallel-change plan from expand to migrate phase. Verifies both old and new exist before transition. Provided by the Parallel Change methodology.
Command
Manage parallel-change plans (Expand → Migrate → Contract). Provided by the Parallel Change methodology. Use this for backward-incompatible changes (DB schema, API signatures, breaking type changes) that require zero-downtime migration.