spec-author

Generate feature specifications with user stories, acceptance tests, and architecture for TDD.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/wtsi-hgi/llm-knowledge-base --skill spec-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-author
Source: https://github.com/wtsi-hgi/llm-knowledge-base/tree/main/.github/skills/spec-author
Command: npx skills add https://github.com/wtsi-hgi/llm-knowledge-base --skill spec-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, self-contained feature specifications, ensuring clarity and enabling Test-Driven Development (TDD) for other agents.

Core Features & Use Cases

  • Specification Generation: Writes comprehensive feature specs including user stories, acceptance tests, architecture diagrams, and implementation plans.
  • TDD Enablement: Produces specs that can be implemented purely through TDD by another agent.
  • Use Case: A product manager needs a new user authentication feature. This Skill generates a spec document detailing the user stories, API contracts, and acceptance tests, which an 'implementor' agent can then use to build the feature.

Quick Start

Use the spec-author skill to write a specification for a new user login feature.

Frequently Asked Questions about spec-author

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

FAQPage Schema
How do I write feature specifications for test-driven development?

Generate feature specifications for test-driven development by defining user stories, acceptance tests, and architecture. This produces self-contained documents that enable automated TDD implementation and ensure software clarity.

What is the best way to structure user stories and acceptance tests for software development?

Structure user stories and acceptance tests using strict formatting rules for machine readability. Detailed specification generation includes defining the implementation order and architecture to facilitate clear test-driven development.

Can I use generated feature specifications to automate test-driven development with another agent?

Yes, generated feature specifications are designed to enable test-driven development by another agent. The self-contained documents provide API contracts and acceptance tests necessary for an implementor agent to build the feature.

How do I define implementation order and architecture in a feature specification?

Define implementation order and architecture within the feature specification by generating comprehensive plans. The specification adheres to strict formatting rules, ensuring the architecture diagrams and implementation steps are highly machine readable.

Does feature specification generation work without external dependencies?

Yes, feature specification generation works without external dependencies. The process relies on internal formatting rules and references to produce self-contained documents detailing user stories and acceptance tests for software development.