skills.rest
SamJHudson01
SamJHudson01COMMUNITY
Explore all skills by this author →
GitHub

spec-writer

Generate structured software specifications with Job Stories and Gherkin acceptance criteria.

51|8|Updated Mar 10, 2026
Search Tags:#scoping#documentation#software development#specification#requirements#agile
One-click install
npx skills add https://github.com/SamJHudson01/Carmack-Council --skill spec-writer-samjhudson01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/SamJHudson01/Carmack-Council/tree/main/skills/spec-writer
Command: npx skills add https://github.com/SamJHudson01/Carmack-Council --skill spec-writer-samjhudson01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill generates concise, actionable software specifications that eliminate ambiguity for AI agents and human developers, ensuring clarity on requirements and scope before implementation begins.

Core Features & Use Cases

  • Adaptive Complexity Specs: Creates specifications tailored to the complexity of the task (Small, Feature, Product).
  • Structured Output: Generates specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries (Always, Ask First, Never).
  • Use Case: When starting a new feature development, use this Skill to produce a clear, unambiguous specification document that outlines exactly what needs to be built, what is out of scope, and how success will be measured, preventing scope creep and misinterpretation.

Quick Start

Use the spec-writer skill to generate a feature-tier specification for a new user authentication module.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I generate software specifications for agile feature development?▼

Software specifications for agile development are generated using a structured workflow defining the "what" and "why" of a task. This produces Job Stories, Gherkin acceptance criteria, and three-tier boundaries to ensure clear, agent-executable requirements without implementation details.

What is the best way to write unambiguous requirements for AI agents?▼

The best way to write unambiguous requirements for AI agents is to produce structured software specifications featuring Job Stories and Gherkin acceptance criteria. This eliminates ambiguity by clearly defining scope and success metrics before implementation begins.

How do I prevent scope creep when documenting software requirements?▼

Scope creep is prevented by documenting software requirements with three-tier boundaries: Always, Ask First, and Never. This structured specification outlines exactly what needs building and what is out of scope, preventing misinterpretation.

Can I create different complexity levels of software specifications for bug fixes and products?▼

Yes, adaptive complexity specifications can be created for Small, Feature, and Product tiers. This applies to scenarios requiring clear documentation for bug fixes or products, tailoring the requirements output to the specific task's scale.

Does software specification include implementation details like code structure?▼

No, software specification generation specifically excludes implementation details. It focuses entirely on the "what" and "why" documentation, defining requirements and scope through Job Stories and boundaries rather than technical code structure.

Related Skills

Explore More Software Engineering Skills→
nbarthelemynbarthelemy

project-interview

Conduct project specification interviews and generate a complete SPEC.md.

Community
Advanced
Adelie-SquadAdelie-Squad
17

jobs-stories

Generate Job Stories, User Stories, and Gherkin acceptance criteria from product briefs.

Official
Advanced
AgLyx3AgLyx3

agile-product-owner

Generate user stories and acceptance criteria for agile backlog management.

Community
Advanced
rezosndrezosnd

product-manager

Generate product requirement documents, user stories, and roadmaps.

Community
Intermediate