feature-spec

Write feature specifications with acceptance criteria and out-of-scope boundaries.

Updated Jul 18, 2025

Search Tags:#requirements #scope creep #acceptance criteria #github issues #feature specification #technical notes

Ready to run

npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill feature-spec-dougborg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/dougborg/stocktrim-openapi-client/tree/main/.claude/skills/feature-spec
Command: npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill feature-spec-dougborg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid building the wrong thing by forcing clear, testable requirements before implementation, reducing rework and misalignment.

Core Features & Use Cases

Structured alignment template: Capture a feature’s problem, user story, acceptance criteria, out-of-scope items, and technical notes in a consistent format.
Testable acceptance criteria: Ensure every requirement can be verified with concrete, measurable checks.
Scope control via Out of Scope: Reduce iteration churn by explicitly documenting what is not included.
Implementation clarity via Technical Notes: List affected files/tables/roles and dependencies to avoid surprise changes mid-flight.
Issue linking workflow: Close and depend on related GitHub issues from the spec for better traceability.

Quick Start

Write a feature specification for the change you plan to ship, including testable acceptance criteria, an out-of-scope section, and a technical notes list of affected files or components.

Frequently Asked Questions about feature-spec

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

FAQPage Schema

How do I write feature specifications that prevent scope creep?▼

Feature specifications prevent scope creep by enforcing testable acceptance criteria, explicit out-of-scope boundaries, and technical notes listing all affected files, tables, and roles before implementation begins.

When do I need to use a feature specification template?▼

A feature specification template is needed for significant product changes involving multiple files, roles, or user-facing impact where requirements are not yet fully clear and require team alignment before implementation.

How do I define testable acceptance criteria for product requirements?▼

Testable acceptance criteria are defined by ensuring every requirement can be verified with concrete, measurable checks, capturing the feature's problem, user story, and explicit out-of-scope items in a structured alignment format.

Can I link GitHub issues to my feature specification?▼

Yes, you can close and depend on related GitHub issues directly from the feature specification, establishing better traceability between your requirements and the corresponding implementation tasks.

What's the best way to document technical notes for a feature change?▼

Technical notes are documented by listing all affected files, tables, roles, and dependencies within the feature specification, ensuring implementation clarity and avoiding surprise changes mid-flight during development.