spec-driven-development

PROACTIVELY use when documenting architectural decisions. Creates Architecture Decision Records (ADRs) from specification context using MADR format. Extracts technical decisions, alternatives considered, rationale, and consequences from specifications.

PROACTIVELY use. Interactive authoring assistant for specifications. Pass mode as argument (ears, gherkin, userstory). Use when creating new requirements using EARS syntax, Gherkin scenarios, or user stories with step-by-step guidance.

PROACTIVELY use. Converts specifications between formats. Pass mode as argument (ears, gherkin, kiro). Use for format transformations, feature file generation, or Kiro synchronization.

PROACTIVELY use. Generates or refines specifications. Pass mode as argument (generate, refine). Use for creating new specs from requirements or improving existing spec quality.

PROACTIVELY use. Audits or validates specifications (read-only). Pass mode as argument (audit, validate). Use for quality audits with scoring or quick format validation.

Create Architecture Decision Record from specification context.

Author and validate AsyncAPI 3.0 specifications for event-driven API design, message brokers, and async communication patterns

Audit specification quality and generate compliance report.

Canonical specification format reference. Use when understanding the canonical spec schema, field requirements, provider-agnostic specification structure, or validating specifications against the schema.

Create or update the project constitution file (.constitution.md) for Spec Kit workflow.