spec-kit

To convert feature ideas into Gherkin stories, draft a complete story file in docs/stories/ that captures the feature's acceptance criteria. The story serves as the sole specification, requiring no intermediate artifacts before implementation begins.

Maintain a single approved specification by using a Gherkin story file with frontmatter-driven status tracking. This enforces story validation steps, ensuring drafts are approved and ready for implementation within your development workflow.

No, you do not need separate specification or task artifacts. The Gherkin story file itself is the minimum spec, treating the story as the sole specification document and eliminating the need for intermediate problem or plan files.

Frontmatter validation for feature story approval works by enforcing a story template and applying status checks. This ensures stories are properly drafted, approved, and tracked through the development lifecycle before implementation.

Yes, you can track feature epic status automatically using Gherkin story files. The story template supports integration with feature epics and applies automatic status tracking via frontmatter metadata within the docs/stories/ directory.

You should avoid using a single Gherkin story as the sole specification when your feature development workflow requires multiple intermediate artifacts like detailed plans or task breakdowns rather than one approved story per feature.