skills.rest
nsheaps
nsheapsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Spec Writing

Produce iterative product specifications and prioritized user stories from seed inputs.

3|1|Updated Dec 3, 2025
Search Tags:#requirements#iterative#product-management#user-stories#acceptance-criteria#spec-writing#product-spec
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill spec-writing-nsheaps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Spec Writing
Source: https://github.com/nsheaps/ai-mktpl/tree/main/plugins/product-development-and-sdlc/skills/spec-writing
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill spec-writing-nsheaps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product specifications are often created in a single pass and miss assumptions, edge cases, and testable acceptance criteria; this skill guides a repeatable, research-driven process to turn a seed idea into an actionable spec and prioritized user stories.

Core Features & Use Cases

  • Iterative cycle: Seed, Draft, Research, Review, and Refine to grow fidelity over multiple passes rather than one-shot writing.
  • Template-driven drafting: Start with a skeleton using a provided spec template that separates Problem & Requirements from Technical Design.
  • Research and validation: Encourage prior-art review, technical feasibility checks, and focused user questions to fill unknowns.
  • User stories & acceptance criteria: Decompose validated requirements into prioritized, testable stories ready for implementation.
  • Use case: Convert a one-paragraph problem statement into a skeleton spec, research relevant constraints, refine requirements, and produce a set of prioritized user stories with acceptance tests.

Quick Start

Write a one-paragraph seed describing the problem, target user, and urgency, then ask the assistant to draft a skeleton spec from the template and mark unknowns as [TBD].

Frequently Asked Questions about Spec Writing

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

FAQPage Schema
How do I write product specs from a short problem statement?▼

To write product specs from a short problem statement, provide a one-paragraph seed describing the problem, target user, and urgency. The skill drafts a skeleton spec from a template and iteratively expands it through research, review, and refinement cycles.

How do I generate testable acceptance criteria for user stories?▼

You generate testable acceptance criteria by decomposing validated product requirements into prioritized user stories. The iterative refinement cycle ensures each story includes specific acceptance tests ready for implementation planning.

What is the best way to structure a product spec for technical design?▼

The best way to structure a product spec for technical design is using a combined template that explicitly separates Problem & Requirements from Technical Design. This ensures validated user needs align with technical feasibility checks.

How does iterative spec writing improve product discovery and planning?▼

Iterative spec writing improves product discovery by growing fidelity over multiple passes—Seed, Draft, Research, Review, and Refine—rather than one-shot writing. This research-driven process catches assumptions, edge cases, and missing constraints early.

Can I use this approach to validate technical feasibility and prior art?▼

Yes, you can validate technical feasibility and review prior art during the research phase. The workflow encourages targeted user questions and technical checks to fill unknowns marked as [TBD] before finalizing requirements.

What do I need to start drafting a product spec?▼

To start drafting a product spec, you only need a brief seed describing the target user, the core problem, and the urgency. The process generates a skeleton spec and prioritized user stories without requiring pre-existing detailed documentation.

Related Skills

Explore More Product & Management Skills→
cvillamarp-lgtmcvillamarp-lgtm

working-backwards

Draft a PR/FAQ document with problem, solution, quotes, and plan.

Community
Intermediate
sicktasticsicktastic

user-story

Create Mike Cohn user stories with Gherkin acceptance criteria.

Community
Intermediate
npownpow
4

deep-idea

Generate and validate non-obvious ideas with adversarial prior-art checks.

Community
Advanced
andreyvitandreyvit
5

zoo-zero

Execute end-to-end tasks with iterative code-review and fix loops.

Community
Advanced