system-spec-kit

Spec-folder automation standardizes documentation across file modifications by enforcing progressive levels (1-3) and applying templates. Use the create-spec-folder script or /spec_kit commands to auto-generate named folders, preserve context, and trigger gated workflows whenever you change code, docs, or configuration.

Spec folders support three progressive documentation levels: Level 1 baseline captures essential change intent, Level 2 verification documents validation steps and decisions, and Level 3 full provides complete context including memory checkpoints and vector search indexing for cross-session resumption.

Yes. The Skill provides 12 templates, 7 automation scripts, and 8 governance gates that standardize specs and enforce documentation compliance. Gate-enforced workflows block file modifications until spec requirements are satisfied, reducing revision toil and ensuring context preservation.

Spec folders integrate with memory tooling and vector-search indexing to checkpoint context during file modifications. Memory preservation enables fast resumption in future sessions by storing change rationale, decisions, and indexed documentation that the memory MCP server and vector-index tools can retrieve.

Create a spec folder whenever your conversation modifies files—code, documentation, or configuration. The mandatory spec-folder model applies universally to enable template enforcement, memory checkpointing, and gated modification rules, minimizing context loss and accelerating onboarding across all file-change scenarios.