spec-writing

To write Gherkin specs before implementation, you create or update feature files in the pandahrms-spec repository, establishing a hard gate that prevents any code changes from proceeding without agreed-upon specifications.

A spec-first workflow requires Gherkin specifications to be written or updated in pandahrms-spec before any work proceeds, enforcing a hard gate that blocks code changes until specs are established and agreed upon.

For non-Pandahrms projects, Gherkin specs are guided to be stored directly in the project's own repository rather than pandahrms-spec, provided the workspace constraints are met.

You must set up the pandahrms-spec repository as a sibling directory within your workspace environment so the spec-writing process can correctly locate and update the Gherkin feature files.

Your workflow requires specs before implementation to ensure alignment between design, requirements, and tests, creating a hard gate that prevents untracked code changes from proceeding without agreed-upon Gherkin specifications.

You can update existing Gherkin specifications in the pandahrms-spec repository before proceeding with new implementation, ensuring the feature files reflect current requirements and maintaining the hard-gate rule.