gxpm-specifier

Capture domain behavior specifications in Gherkin-style scenarios during the specify phase.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-specifier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gxpm-specifier
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-specifier
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-specifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gxpm-specifier helps teams formalize domain-level behavior in a structured, non-implementation format, ensuring stakeholders agree on intended behavior before coding.

Core Features & Use Cases

  • Governs behavior-spec drafting in Gherkin-style scenarios during the specify phase.
  • Enforces constitution-compliant governance with CANON.md references and explicit [NEEDS CLARIFICATION] guards.
  • Provides a gate-checked workflow that prevents implementation steps until user confirmation and non-placeholder data are present.

Quick Start

Begin by running gxpm specify init to start drafting behavior specifications.

Frequently Asked Questions about gxpm-specifier

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

FAQPage Schema
How do I write behavior specifications in Gherkin before starting implementation?▼

BDD behavior specifications are captured in Gherkin-style scenarios during the specify phase, enforcing non-implementation rules and constitution-gate compliance to ensure stakeholders agree on intended behavior before any coding begins.

What is the specify phase in behavior-driven development?▼

The BDD specify phase is a governance stage where domain-level behavior is formalized in Gherkin scenarios, preventing implementation steps until user confirmation and non-placeholder data validate the intended behavior.

How do I prevent premature implementation in a BDD specification workflow?▼

You prevent premature implementation in BDD workflows by applying gate-checked governance rules that block coding steps until specifications contain no placeholders and receive explicit user confirmation.

Why does my BDD specification workflow require a constitution gate check?▼

A constitution gate check is required in BDD specification workflows to enforce governance compliance via explicit references, ensuring domain behavior is validated and non-implementation rules are met before proceeding.

How do I handle missing domain knowledge when drafting Gherkin scenarios?▼

When missing domain knowledge occurs while drafting Gherkin scenarios, use explicit NEEDS CLARIFICATION guards to flag incomplete behavior, preventing the specification from passing governance checks until resolved.

Can I use Gherkin scenarios for governance without writing implementation code?▼

Yes, you can use Gherkin scenarios for governance without implementation code by operating within a dedicated specify phase that enforces non-implementation rules and validates behavior through constitution checks.