skills.rest
blaknite
blakniteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

specifying-behaviour

Generate structured natural language behaviour specifications with acceptance criteria and constraint statements.

Updated Aug 23, 2026
Search Tags:#documentation#specification#requirements#acceptance criteria#behaviour
One-click install
npx skills add https://github.com/blaknite/agent-skills --skill specifying-behaviour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specifying-behaviour
Source: https://github.com/blaknite/agent-skills/tree/main/specifying-behaviour
Command: npx skills add https://github.com/blaknite/agent-skills --skill specifying-behaviour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in creating unambiguous, structured natural language specifications for features or changes, bridging the gap between vague user stories and overly technical documentation.

Core Features & Use Cases

  • Structured Specification Writing: Guides users to write clear, concise behaviour specifications.
  • Defining Acceptance Criteria: Useful for clearly outlining what constitutes successful implementation.
  • Use Case: When defining a new feature, use this skill to articulate exactly how it should behave under various conditions, ensuring all stakeholders have a shared understanding.

Quick Start

Use the specifying-behaviour skill to write a specification for a user login feature.

Frequently Asked Questions about specifying-behaviour

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

FAQPage Schema
How do I write behaviour specifications for software features?▼

To write behaviour specifications, use a strict format starting with a lead declarative sentence, followed by 'when' clauses for edge cases, and concluding with constraint statements to define expected system interactions clearly.

What is the best way to define acceptance criteria for a new feature?▼

The best way to define acceptance criteria is to generate structured natural language specifications that articulate exactly how a feature should behave under various conditions, ensuring all stakeholders share a common understanding.

How do I structure edge cases in a software requirement specification?▼

Structure edge cases in a requirement specification by adding 'when' clauses after the primary declarative sentence, followed by constraint statements to capture conditional system interactions and boundaries.

Can I use natural language specifications instead of formal requirements documentation?▼

Yes, you can use natural language specifications to bridge the gap between vague user stories and overly technical documentation, providing unambiguous, structured requirements that are accessible to non-technical stakeholders.

What format should feature behaviour documentation follow?▼

Feature behaviour documentation should follow a strict format: a lead declarative sentence stating the expected behaviour, followed by 'when' clauses for edge cases, and concluding with constraint statements for system boundaries.

Related Skills

Explore More Software Engineering Skills→
fanguyunfanguyun

feature-forge

Facilitate structured workshops to produce feature specifications, user stories, and acceptance criteria.

Community
Advanced
javierhbrjavierhbr

atdd

Generate failing executable tests from natural language acceptance criteria.

Community
Intermediate
1479089714790897
7

kwp-product-management-write-spec

Generate structured product requirement documents from unstructured problem statements.

Community
Intermediate
IntegralistIntegralist
2

behaviour-spec

Generate Gherkin specifications from feature descriptions for BDD testing.

Community
Intermediate