skills.rest
slgoodrich
slgoodrichCOMMUNITY
Explore all skills by this author →
GitHub

specification-techniques

Transform vague product ideas into precise, testable specifications.

121|19|Updated Oct 17, 2025
Search Tags:#product management#use cases#PRD#user stories#requirements engineering#agile documentation#product specification
One-click install
npx skills add https://github.com/slgoodrich/agents --skill specification-techniques
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification-techniques
Source: https://github.com/slgoodrich/agents/tree/main/plugins/product-management/skills/specification-techniques
Command: npx skills add https://github.com/slgoodrich/agents --skill specification-techniques

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the problem of ambiguous or incomplete product specifications by providing a comprehensive suite of techniques and templates. It ensures clear communication of requirements, reducing rework and aligning development with user needs, ultimately delivering the right product efficiently.

Core Features & Use Cases

  • User Stories & Job Stories: Define features from the user's perspective, focusing on outcomes.
  • PRD & Use Case Templates: Structure detailed Product Requirements Documents and user interaction flows.
  • Non-Functional Requirements: Specify critical aspects like performance, security, and scalability.
  • Edge Case Checklist: Ensure comprehensive coverage of all scenarios, preventing unexpected issues.
  • Use Case: Document the requirements for a new user onboarding flow, including user stories, non-functional requirements, and a checklist for edge cases to ensure a robust and complete specification.

Quick Start

Generate a comprehensive PRD structure for a new mobile banking app, including sections for user stories and non-functional requirements.

Frequently Asked Questions about specification-techniques

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

FAQPage Schema
How do I write user stories and acceptance criteria that prevent miscommunication with developers?▼

User stories and acceptance criteria transform vague ideas into testable specifications by framing features from the user's perspective, defining outcomes, and listing concrete scenarios developers must satisfy. This format reduces rework by ensuring alignment before development starts.

What should a PRD include to cover all requirements—functional, performance, and edge cases?▼

A comprehensive PRD structures user stories, non-functional requirements (performance, security, scalability), use case flows, and edge-case checklists. This layered approach ensures developers have complete context for building robust features and prevents unexpected issues in production.

Why do product specifications fail, and how do I avoid costly rework?▼

Ambiguous specifications lead to misaligned development and rework. Clear specifications using structured templates, traceability across requirements, and testable acceptance criteria ensure the team builds the right product efficiently and catches gaps before implementation.

How do I document API specifications, Jobs-to-be-Done, and cross-functional alignment in one framework?▼

Apply specification techniques across multiple formats—API specs, Jobs-to-be-Done statements, and acceptance criteria using Gherkin or 3Cs—to unify how teams define, validate, and communicate requirements across product, engineering, and design.

What's the difference between user stories, use cases, and PRDs, and when do I use each?▼

User stories capture single user outcomes in conversational format; use cases document detailed interaction flows; PRDs structure the full product vision with all requirement types. Combine them to satisfy different audiences and levels of detail.

How do I ensure my specifications catch edge cases and anti-patterns before development?▼

Use edge-case checklists and anti-pattern guidance embedded in your specification templates to systematically identify gaps, boundary conditions, and common pitfalls. This prevents surprises and ensures comprehensive coverage across scenarios.

Related Skills

Explore More Product & Management Skills→
Open-PawsOpen-Paws
4

requirements-interview

Coordinates stakeholder interviews and synthesizes findings into a formal specification document.

Official
Intermediate
camilooscargbaptistacamilooscargbaptista
7

sprint-planning

Convert backlog items into prioritized user stories with acceptance criteria and sprint backlog.

Community
Advanced
viethahongviethahong

prd-writing

Generate PRDs with goals, user flows, requirements, acceptance criteria, and edge cases.

Community
Advanced
GainInsightDevGainInsightDev

af-write-scenario-specs

Generate BDD Markdown scenario specifications with preconditions, steps, and expected outcomes.

Official
Basic