Archive notice: This page documents historical Spec Kitty behavior and is not the current 3.2 workflow. Start with Spec Kitty 3.2 for current docs.
1.x Branch and Workspace Model
Feature-Centric Branching
- Each feature is tracked as a branch-scoped workspace.
- Work packages are executed in isolated working directories.
- Merge operations close the feature workflow by integrating approved work.
Execution Discipline
- Work packages should move through lane states in order.
- Planning artifacts are the contract for implementation and review.
- Charter principles are applied before final acceptance.
Typical 1.x Paths
- Feature artifacts:
kitty-specs/<feature>/... - Runtime/project state:
.kittify/... - Command templates and mission defaults from packaged mission/template roots (
src/specify_cli/missions/**,src/specify_cli/templates/**) and project overrides.