skills.rest
samcdavid
samcdavidCOMMUNITY
Explore all skills by this author →
𝕏@sammy_fix_itGitHub

my-spec

Refine vague ideas into structured product specs through iterative questioning.

4|1|Updated May 31, 2015
Search Tags:#requirements#discovery#spec#product-management#stakeholders#refine#intake
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill my-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: my-spec
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-spec
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn vague ideas, bug reports, or rough requests into clear, well-scoped specifications through iterative conversations, surfacing assumptions and decision points.

Core Features & Use Cases

  • Intake and clarification: identifies what needs refinement and gathers missing context.
  • Iterative questioning and scoping: surfaces ambiguities, constraints, and acceptance criteria.
  • Spec writing: produces structured documents with problem, scope, success criteria, and risks that engineers can act on.

Quick Start

Provide a vague idea or issue description and I will refine it into a clear, well-scoped spec through structured steps.

Frequently Asked Questions about my-spec

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

FAQPage Schema
How do I refine vague product ideas into clear specs?▼

You can turn rough bug reports into structured product specs by inputting the issue description. The system identifies missing context, applies iterative scoping to surface ambiguities, and delivers a document with success criteria and open questions.

What is the best way to gather missing context during product discovery?▼

The spec writing process includes a final review loop to ensure all constraints and acceptance criteria are accurately captured. It delivers a structured spec containing the problem definition, scope, requirements, risks, and open questions for engineers.

Can I use existing issues as input for product spec writing?▼

Yes, you can use existing issues as input for product spec writing. The system accepts varied inputs including descriptions, URLs, and existing issues, refining them through structured steps into well-scoped specifications.

Does product spec generation work without predefined acceptance criteria?▼

Product spec generation works without predefined acceptance criteria by using iterative questioning to surface them during the conversation. It extracts assumptions and constraints from your initial input to build the requirements.

Related Skills

Explore More Product & Management Skills→
posit-devposit-dev
4.2k

positron-intake-rotation

Automate intake-rotation triage for Positron GitHub issues, discussions, and tickets.

Official
Basic
tech-leads-clubtech-leads-club
5.0k

tlc-spec-driven

Plan and execute software projects through four specification-driven phases.

Official
Advanced
edwardmonteiroedwardmonteiro

delivery.roadmap

Translate strategy into a sequenced delivery roadmap with risks and stakeholder communication.

Community
Basic
skerishKangskerishKang

Conversation Archiver

Archive conversation transcripts into canonical docs/conversation structures with summaries and index updates.

Community
Intermediate