skills.rest
nweii
nweiiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-shaping

Shape product ideas into scoped specs and sprint plans with YAML frontmatter.

7|Updated Dec 17, 2025
Search Tags:#documentation#requirements#interview#spec#product-management#sprint-planning#living-document
One-click install
npx skills add https://github.com/nweii/agent-stuff --skill spec-shaping
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-shaping
Source: https://github.com/nweii/agent-stuff/tree/main/skills/spec-shaping
Command: npx skills add https://github.com/nweii/agent-stuff --skill spec-shaping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shape fuzzy product concepts into well-scoped specifications and organized sprint plans, enabling fast alignment and actionable work.

Core Features & Use Cases

  • Interview mode to elicit requirements and narrow scope through structured questioning.
  • Sprint breakdown mode to decompose a spec into atomic tasks with clear milestones.
  • Living-document guidance: treat specs as adaptable, versioned artifacts that evolve with feedback.
  • Use case: when a team has a rough idea, run an interview to produce a concrete spec and a plan for the next sprint.

Quick Start

Begin an interview to narrow the product problem and generate a living spec with an initial sprint plan.

Frequently Asked Questions about spec-shaping

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

FAQPage Schema
How do I turn vague product ideas into actionable specs?▼

To turn vague product ideas into actionable specs, use structured interview questioning to elicit requirements and narrow scope, generating a well-scoped living-document spec adaptable to feedback.

What is the best way to break a product spec into sprint-ready tasks?▼

Breaking a product spec into sprint-ready tasks involves decomposing the specification into atomic work items with clear milestones, delivering concrete tasks structured for immediate sprint planning execution.

How does a living-document spec help with sprint planning?▼

A living-document spec evolves with feedback during sprint planning, treating your product requirements as adaptable, versioned artifacts that keep generated work items continuously aligned with project changes.

Can I use an interview format to elicit product requirements for documentation?▼

Yes, you can use an interview format to elicit product requirements for documentation, applying structured questioning during initial product discussions to narrow the problem scope and produce concrete specifications.

Does spec shaping support YAML frontmatter metadata for product management?▼

Spec shaping supports YAML frontmatter metadata for product management, allowing you to embed structured configuration directly into your living-document specs alongside adaptive output locations.

When should I not use a structured interview for product requirement gathering?▼

You should avoid structured interviews for product requirement gathering when initial product discussions are already well-scoped, as the questioning process is designed to narrow fuzzy concepts into actionable specs.

Related Skills

Explore More Product & Management Skills→
darkroomengineeringdarkroomengineering
41

discovery

Guide structured interviews to define project scope and requirements.

Official
Intermediate
packetalienpacketalien

retrospective

Analyze sprint and milestone data to generate a structured Markdown retrospective.

Community
Advanced
igoorstraviinsky-devigoorstraviinsky-dev

speckit-constitution

Create or update the project constitution at .specify/memory/constitution.md with placeholders and versioning.

Community
Advanced
Prathmesh2000Prathmesh2000
1

task-planner

Break down high-level requirements into structured task lists with dependencies.

Community
Advanced