paw-spec

Convert issues or briefs into structured feature specifications with prioritized user stories.

39|6|Updated Oct 8, 2025

Search Tags:#research #specification #requirements #clarification #traceability #user-stories

Ready to run

npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: paw-spec
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-spec
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a vague issue or feature brief into a precise, testable specification with prioritized user stories, requirements, and success criteria, enabling clear alignment before design and development.

Core Features & Use Cases

Interactive clarification to resolve high-impact gaps before drafting
Generate prioritized user stories with acceptance criteria and traceability IDs (FR-001, SC-001)
Integrate research findings into the specification and revise based on downstream feedback
Ensure requirements are testable and map cleanly to stories

Quick Start

To start a new spec from an issue, instruct the PAW session to create a specification from your issue description and run the clarification phase as needed.

Frequently Asked Questions about paw-spec

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

FAQPage Schema

How do I convert a vague issue brief into a structured feature specification?▼

To convert a vague issue brief into a feature specification, provide the issue description to initiate an interactive clarification phase that resolves gaps before drafting prioritized user stories with acceptance criteria.

What is the best way to ensure user stories are independently testable and well-scoped?▼

Ensuring user stories are independently testable requires generating structured specifications with traceability IDs, mapping requirements cleanly to stories, and defining clear success criteria for each feature.

Can I integrate research findings into my requirements specification and revise it later?▼

Yes, you can integrate research findings directly into the specification and apply revisions based on downstream feedback, ensuring the requirements document stays aligned throughout the workflow.

How does interactive clarification improve the quality of feature requirements?▼

Interactive clarification improves feature requirements by identifying and resolving high-impact gaps in the initial brief before drafting begins, ensuring alignment and preventing scope creep during development.

Do I need traceability IDs for managing feature specifications and user stories?▼

Traceability IDs like FR-001 and SC-001 are enforced within the specification to map requirements and success criteria directly to user stories, ensuring every feature maintains strict backward traceability.

What should I do if my user stories lack clear acceptance criteria and success metrics?▼

If user stories lack clear acceptance criteria, transform the brief into a precise specification that generates prioritized stories with defined success metrics and testable requirements to establish alignment.