specify

Name: specify
Availability: InStock
Author: lionbenjamin

Draft product specifications with problem, goals, user stories, and acceptance criteria.

15|6|Updated Jan 5, 2026

Search Tags:#planning #scoping #specification #requirements #product-management #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/lionbenjamin/agent-templates --skill specify-lionbenjamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/lionbenjamin/agent-templates/tree/main/skills/specify
Command: npx skills add https://github.com/lionbenjamin/agent-templates --skill specify-lionbenjamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define clear, testable product specifications that articulate what to build and why, without prescribing how.

Core Features & Use Cases

Structured specification template with sections for problem, goals, user stories, acceptance criteria, scope, and success metrics.
Guidance for writing user stories and measurable acceptance criteria to align stakeholders and reduce ambiguity.
Real-world example: define a feature and its success criteria to prevent scope creep.

Quick Start

Draft a feature specification for a new login flow including user stories and acceptance criteria.

Frequently Asked Questions about specify

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

FAQPage Schema

How do I write a product specification with clear acceptance criteria and user stories?▼

To write a product specification, use a structured template that includes problem, goals, user stories, acceptance criteria, scope, and success metrics. This format articulates what to build and why while ensuring testable requirements that align stakeholders.

What is the best way to define feature scope and prevent scope creep during planning?▼

The best way to prevent scope creep is defining feature scope using a structured specification with explicit boundaries and success metrics. Clearly documenting the problem and goals ensures stakeholders understand exactly what is excluded from the current build.

How do I structure measurable acceptance criteria for software features?▼

You structure measurable acceptance criteria within a dedicated specification section, pairing them directly with user stories. This approach reduces ambiguity and provides measurable conditions to verify feature outcomes before development begins.

Can I use a product specification template for early feature ideation and requirements refinement?▼

Yes, you can use a product specification template during early feature ideation and requirements refinement. It guides drafting by enforcing sections for problem definition, goals, and user stories to solidify outcomes across software features.

Why define success metrics when scoping a new product feature?▼

You define success metrics when scoping a feature to articulate what to build and why, ensuring testable outcomes. Including these metrics in the specification aligns stakeholders on expected results and prevents unmeasurable scope expansion.