skills.rest
Pixel-Process-UG
Pixel-Process-UGOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec-writing

Generate implementation-free software specifications with JTBD and Given/When/Then criteria.

1|Updated Mar 15, 2026
Search Tags:#documentation#specification#requirements#product management#acceptance criteria#JTBD
One-click install
npx skills add https://github.com/Pixel-Process-UG/superkit-agents --skill spec-writing-pixel-process-ug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writing
Source: https://github.com/Pixel-Process-UG/superkit-agents/tree/main/templates/skills/spec-writing
Command: npx skills add https://github.com/Pixel-Process-UG/superkit-agents --skill spec-writing-pixel-process-ug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that software specifications are clear, testable, and free from implementation details, leading to more flexible and maintainable code.

Core Features & Use Cases

  • Jobs to Be Done (JTBD): Structures requirements around user needs and motivations.
  • Implementation-Free Specs: Enforces a strict rule against including code, technology choices, or architectural patterns in specifications.
  • Acceptance Criteria: Defines clear, testable conditions using the Given/When/Then format.
  • Use Case: A product manager needs to define a new feature. They use this skill to create a specification document that clearly outlines what the feature should do from a user's perspective, without dictating how the developers should build it.

Quick Start

Use the spec-writing skill to create a new specification file for the user authentication feature.

Frequently Asked Questions about spec-writing

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

FAQPage Schema
How do I write implementation-free software specifications?▼

Implementation-free software specifications are generated using the Jobs to Be Done methodology, enforcing a strict cardinal rule against including code, technology names, or architectural patterns to ensure flexible, maintainable outcomes.

What is the Jobs to Be Done methodology for product requirements?▼

Jobs to Be Done structures product requirements around user needs and motivations rather than technical solutions, defining what a feature should accomplish without dictating how developers should build it.

How do I format acceptance criteria for software specifications?▼

Acceptance criteria are formatted using Given/When/Then statements to define clear, testable conditions for software specifications, ensuring each requirement has verifiable success metrics.

How do I organize specifications into a story map for release planning?▼

Specifications are organized into a story map for release planning using SLC criteria, which stands for Simple, Lovable, Complete, to prioritize and structure feature delivery effectively.

Why do my software specifications include too many implementation details?▼

Software specifications often contain implementation details because technical constraints bleed into requirements; enforcing a strict cardinal rule strips out code, technology names, and architectural patterns.

Does product management documentation work without specifying architecture?▼

Product management documentation works effectively without specifying architecture by focusing strictly on user perspectives and jobs to be done, yielding clear and testable specification documents.

Related Skills

Explore More Product & Management Skills→
Kushal9889Kushal9889

create-jtbd

Create Jobs-to-Be-Done documents for product features from user needs.

Community
Intermediate
OmexITOmexIT
13

ticket-breakdown

Convert PRD or design docs into epics, tickets, and acceptance criteria.

Community
Intermediate
ZateZate
9

requirements-patterns

Generate user stories and acceptance criteria using Given-When-Then templates.

Community
Basic
mohamedgshoaibmohamedgshoaib
5

react-useeffect

Identify React useEffect anti-patterns and recommend architectural alternatives.

Community
Intermediate