spec

Transform vague feature discussions into structured SDD-compatible specification files.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/npow/claude-skills --skill spec-npow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/npow/claude-skills/tree/main/spec
Command: npx skills add https://github.com/npow/claude-skills --skill spec-npow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague ideas, conversations, and feature requests into structured, reviewable specifications that clarify the problem, scope, requirements, and measurable outcomes.

Core Features & Use Cases

  • Structured Specification: Produces SDD-compatible spec.md files with user stories, functional requirements, success criteria, assumptions, and edge cases.
  • Design Clarification: Extracts the core system, asks up to three high-value questions, and records explicit assumptions when details are uncertain.
  • Downstream Readiness: Creates specifications that can feed planning, task generation, implementation, and quality validation workflows.
  • Use Case: Give the Skill a rough feature discussion and receive a focused specification that development teams can review and use for subsequent planning.

Quick Start

Ask the spec skill to turn your feature idea or conversation into an SDD-compatible specification.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn vague feature ideas into structured software specifications?

To turn vague ideas into structured software specifications, provide your feature discussions to the tool to generate reviewable spec.md files containing user stories, functional requirements, success criteria, and documented edge cases.

What is the best way to write an SDD-compatible specification from rough product requirements?

Writing an SDD-compatible specification from rough product requirements involves extracting the core system, asking clarifying questions, and documenting explicit assumptions to produce measurable requirements and prioritized user scenarios.

Can I use this to create API proposals and technical designs from unstructured conversations?

Yes, you can create API proposals and technical designs from unstructured conversations by processing the text to produce downstream-ready specification artifacts with clear scope and testable outcomes.

Does this approach handle assumptions and edge cases when mapping user stories?

Handling assumptions and edge cases when mapping user stories is supported by recording explicit assumptions when details are uncertain and producing measurable requirements that account for boundary conditions.

What downstream workflows can consume the generated specification artifacts?

Downstream workflows that can consume the generated specification artifacts include development planning, task generation, software implementation, and quality validation processes.

When do I need a formal specification document for my technical design?

You need a formal specification document for your technical design when clarifying the problem, scope, and requirements is necessary to produce measurable outcomes and reviewable deliverables for your development team.