spec-writing

Name: spec-writing
Availability: InStock
Author: Pandaworks

Write or update Gherkin specifications in pandahrms-spec before implementation.

Updated Mar 1, 2026

Search Tags:#workflow #bdd #gherkin #specs #spec-writing #pandahrms

Ready to run

npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill spec-writing-pandaworks-software-plt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-writing
Source: https://github.com/pandaworks-software-plt/pandahrms-skills/tree/main/skills/spec-writing
Command: npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill spec-writing-pandaworks-software-plt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gherkin specifications must be written or updated in the pandahrms-spec repository before any Pandahrms work proceeds. This creates a hard gate that prevents implementation from starting without agreed-upon specs.

Core Features & Use Cases

Writes or updates Gherkin specs for Pandahrms projects before implementation.
Guides teams to ensure alignment between design, requirements, and tests.
Supports non-Pandahrms projects by guiding specs to be stored in the project's own repository if Pandahrms workspace constraints apply.

Quick Start

Write or update the Gherkin specs in pandahrms-spec before starting implementation.

Frequently Asked Questions about spec-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write Gherkin specs before starting code implementation?▼

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.

What is a spec-first workflow and how does it enforce a hard gate for development?▼

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.

Does the spec-writing workflow work for non-Pandahrms projects?▼

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.

How do I set up the workspace directory for writing Gherkin specifications?▼

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.

Why does my development workflow require specs before implementation?▼

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.

Can I update existing Gherkin specifications instead of writing new ones?▼

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.