Skip to main content
Spec Led should be easy to start and able to grow with the project. That means the method should use progressive disclosure. Start with the smallest useful loop. Add more structure only when the project needs it.

​
Level 1: Starter

Use this for small TypeScript projects. You need:
  • one specs/ folder
  • one or more *.spec.md files
  • one check command
  • one CI check
This is enough for many teams.

​
Level 2: Verified

Use this when the project starts to grow. Add:
  • stable IDs
  • clearer verification targets
  • better reports
  • stronger CI output
Some teams may also add an optional pre-commit hook here. That can help catch issues earlier, but it is not the main shared gate.

​
Level 3: Governed

Use this when many parts of the system need to move together. Add:
  • acceptance criteria
  • traceability mappings
  • proposal records
  • decision records
  • diff-aware CI rules
This is where a richer governance model starts to matter.

​
Level 4: Conformance

Use this for larger or more sensitive systems. Add:
  • conformance scenarios
  • release gates
  • stronger operational checks
  • richer drift and evidence reports
This is the deeper end of the method.

​
The key rule

Do not force Level 4 complexity onto a Level 1 team. That is how good methods become too hard to use. The system should let teams start small and grow without switching to a new model later.