Add test-first-governance to the community preset catalog

[ka-zo]

Preset Submission

Preset ID

test-first-governance

Preset Name

Test-First Governance

Version

1.3.0

Description

Governs TDD with coverage-complete BDD/ATDD Gherkin scenarios, explicit suite ownership, professional test reports, traceability, and risk-based quality gates.

Author

Zoltán Katona, PhD

Repository URL

https://github.com/ka-zo/spec-kit-preset-test-first-governance

Download URL

https://github.com/ka-zo/spec-kit-preset-test-first-governance/archive/refs/tags/1.3.0.zip

Documentation URL

https://github.com/ka-zo/spec-kit-preset-test-first-governance/blob/main/README.md

License

MIT

Required Spec Kit Version

>=0.12.11

Required Extensions

None.

Templates Provided

• constitution-template — appends test-first governance principles for TDD, BDD, ATDD, and quality gates
• spec-template — appends evidence ownership, Gherkin, traceability, edge-case, and acceptance-coverage sections
• plan-template — appends test architecture, tooling, gate applicability, threshold, and evidence-retention planning
• tasks-template — appends test-first task ordering, suite tags, Red-Green-Refactor checkpoints, and validation gates
• checklist-template — appends reusable TDD, BDD, ATDD, and quality-gate criteria
• test-traceability-template — provides normalized requirement-to-test traceability and a scenario coverage matrix
• defect-log-template — provides feature-level defect, triage, risk-acceptance, and verification-closure reporting
• test-summary-template — provides feature-level test-summary and release-evidence reporting
• overall-test-summary-template — provides aggregate project or release-level test-summary reporting
• gherkin-feature-template — provides a standalone Gherkin feature template for BDD and ATDD scenarios

Commands Provided

• speckit.constitution — adds mandatory test-first principles to constitution generation
• speckit.specify — adds evidence ownership and Gherkin scenario requirements to specification
• speckit.plan — adds test architecture, suite directories, tooling, traceability artifacts, and quality gates to planning
• speckit.tasks — makes applicable TDD, BDD, and ATDD work mandatory and orders it before implementation
• speckit.checklist — adds test-first quality criteria to checklist generation
• speckit.analyze — validates traceability, Gherkin mirroring, scenario coverage, and gate completeness
• speckit.implement — governs implementation through Red-Green-Refactor cycles and mandatory validation gates
• speckit.converge — creates an aggregate project or release-level test summary

Number of Scripts

None.

Tags

tdd, bdd, atdd, quality-gates, traceability

Key Features

• Governs incremental Red-Green-Refactor development for production logic
• Requires coverage-complete, non-duplicative BDD and ATDD scenarios where applicable
• Establishes explicit suite ownership while allowing evidence to satisfy multiple roles without duplication
• Maintains requirement-to-test traceability and a scenario coverage matrix
• Produces feature-level defect logs, traceability reports, and test summaries
• Produces an aggregate rolling or release-specific test summary
• Applies risk-based coverage, linting, formatting, static-analysis, security, and runtime quality gates
• Supports governed N/A decisions with rationale and alternative evidence
• Wraps the Spec Kit workflow from constitution through implementation, analysis, and convergence
• Is designed to compose with other presets while taking high priority for test-first governance

Testing Checklist

• Preset installs successfully from the release archive using specify preset add --from
• Template resolution works correctly after installation
• Documentation is complete and includes valid specify preset add ... commands
• Tested on at least one real project
• Command overrides register correctly in supported agent directories
• Command overrides and their corresponding template sections have been checked for coherence

Submission Requirements

• Valid preset.yml manifest included
• All 10 referenced template files and 8 referenced command files exist
• Documentation URL points to the preset README
• README includes valid catalog, archive, and local-development installation forms
• LICENSE file included
• Public GitHub release 1.3.0 created
• Preset ID follows the lowercase-with-hyphens naming convention
• Version follows semantic versioning
• Description is under 200 characters
• Added to presets/catalog.community.json in alphabetical order by preset ID
• Added to the Community Presets table in docs/community/presets.md in alphabetical order by preset name

[mnriem]

Please use the preset submission issue template for new/update presets

[ka-zo]

@mnriem Can you please give me directions, with some help? I was using the Presets Publishing Guide and I was also using the Preset Submission Issue Template.

[mnriem]

I was looking for the [Preset] prefix as that is what the title prefills ;) And it should be coming in as an issue. Not as a PR. I will file the issue, but next time please create an issue where it will show you the templates you can use

[ka-zo]

I was looking for the [Preset] prefix as that is what the title prefills ;) And it should be coming in as an issue. Not as a PR. I will file the issue, but next time please create an issue where it will show you the templates you can use

Thank you for your help, I appreciate it.

[mnriem]

Closing in favor of #3502

[mnriem]

It has been merged. Thank you!