spec

Generate Given/When/Then specifications with acceptance criteria for features.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/LeviLeckenby/agentic-ways-of-working --skill spec-levileckenby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/LeviLeckenby/agentic-ways-of-working/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/LeviLeckenby/agentic-ways-of-working --skill spec-levileckenby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to create precise Given/When/Then specifications before implementing features, reducing drift between requirements and delivery.

Core Features & Use Cases

  • Generates a formal Given/When/Then spec covering happy paths, edge cases, and error conditions.
  • Defines acceptance criteria and constraints to guide development, testing, and QA.
  • Useful for product managers coordinating cross-functional teams and for engineers clarifying scope in complex projects.

Quick Start

Draft a complete Given/When/Then specification for a feature description and save it as specs/{feature-name}.md.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I write Given/When/Then specifications for feature requirements?

Acceptance criteria are explicitly mapped to the generated Given/When/Then scenarios, providing clear constraints to guide development, testing, and QA. This ensures formal alignment between requirement definitions and delivery expectations.

How do I create a Given/When/Then spec for a feature description?

The specification covers formal Given/When/Then scenarios, including happy paths, edge cases, and error conditions, while enforcing a structured frontmatter-driven description and explicit acceptance criteria mapping to guide development and QA.

What's the best way to align product management and engineering on feature scope?

By generating formal Given/When/Then scenarios with explicit acceptance criteria mapping, this skill enables product managers and engineers to align on complex project scope, reducing drift between initial requirements and final delivery.

Does generating Given/When/Then specs work for edge cases and error conditions?

Yes, the skill generates formal Given/When/Then specifications that explicitly cover happy paths, edge cases, and error conditions. This ensures comprehensive acceptance criteria derivation for development, testing, and QA workflows.