spec-shaper

Transform ambiguous ideas into structured software specifications with acceptance criteria.

1|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill spec-shaper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-shaper
Source: https://github.com/pascallammers/mylo-travel-concierge-v2/tree/main/.claude/skills/spec-shaper
Command: npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill spec-shaper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users transform vague ideas and incomplete requirements into clear, structured, and actionable specifications, bridging the gap between concept and implementation.

Core Features & Use Cases

  • Requirement Gathering: Guides users through a structured questioning process to uncover functional and non-functional needs.
  • Spec Type Identification: Helps determine if a Feature, Epic, Refactor, or Integration spec is most appropriate.
  • Use Case: A product manager has a high-level idea for a new user dashboard but isn't sure about the specifics. They use the spec-shaper Skill to ask clarifying questions, define user stories, acceptance criteria, and break down the implementation into manageable tasks.

Quick Start

Use the spec-shaper skill to help me define the requirements for a new user profile page.

Frequently Asked Questions about spec-shaper

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

FAQPage Schema
How do I turn vague product ideas into clear software specifications?

To turn vague ideas into clear software specifications, you need structured requirement gathering that identifies functional and non-functional needs. This process guides you through targeted questions to uncover missing details and shape actionable feature definitions.

What is the best way to define user stories and acceptance criteria for a new feature?

Defining user stories and acceptance criteria requires breaking down high-level concepts into well-defined specifications. By identifying the specific spec type and structuring conversations around constraints, you elicit the exact functional details needed for implementation.

How do I know if my requirements need a feature, epic, or refactor specification?

Determining whether requirements need a feature, epic, or refactor specification depends on the scope and nature of the change. Spec type identification evaluates your initial idea against implementation tasks to categorize it accurately for development.

How do I break down incomplete requirements into manageable implementation tasks?

Breaking down incomplete requirements into manageable implementation tasks involves a structured questioning process. This approach uncovers necessary constraints and non-functional details, transforming ambiguous concepts into a comprehensive and actionable task list.

Can I use structured scoping for an integration specification?

Yes, you can use structured scoping for an integration specification. The requirement gathering process supports identifying various spec types, including integrations, and helps define the specific acceptance criteria needed for those technical connections.