dev-spec

Convert vague feature requests into structured design documents.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Jason-chen-coder/dev-skills --skill dev-spec-jason-chen-coder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-spec
Source: https://github.com/Jason-chen-coder/dev-skills/tree/main/skills/dev-spec
Command: npx skills add https://github.com/Jason-chen-coder/dev-skills --skill dev-spec-jason-chen-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables users to convert vague or under-specified requests into clear, structured design documents for development planning and implementation. It addresses the challenge of ambiguity by surfacing uncertainties and clarifying scope before coding begins.

Core Features & Use Cases

  • Ambiguity Surfacing: Interactively identify unclear aspects of a request through multiple interview waves.
  • Scoping & Clarification: Collaboratively define in-scope and out-of-scope items, ensuring aligned expectations.
  • Spec Generation: Produce minimal, verifiable solutions and detailed acceptance criteria to guide development.
  • Use Case: A product manager requests a new feature; this Skill helps clarify requirements, resolve ambiguities, and produce a ready-to-implement spec.

Quick Start

Provide a vague feature request and let the Skill lead you through clarification questions, then generate a structured design document ready for review.

Frequently Asked Questions about dev-spec

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

FAQPage Schema
How do I turn a vague feature request into a structured design document?

To turn a vague feature request into a structured design document, this Skill interactively surfaces ambiguities and clarifies scope through multiple interview waves to produce verifiable specifications.

What is the best way to scope requirements for a new user onboarding feature?

Scoping requirements for user onboarding involves collaboratively defining in-scope and out-of-scope items, resolving ambiguities upfront to ensure aligned expectations before development begins.

How do I resolve ambiguity in product specifications before engineering starts?

Resolving ambiguity in product specifications requires identifying unclear aspects of a request through interactive clarification, then generating minimal, verifiable solutions and acceptance criteria.

Can I generate verifiable acceptance criteria from under-specified product requests?

Yes, you can generate verifiable acceptance criteria from under-specified requests by collaboratively surfacing uncertainties and defining clear boundaries to guide implementation.

When should I use an interactive scoping process for feature design?

Use an interactive scoping process for feature design when a product manager provides a fuzzy request and you need to clarify requirements and produce a ready-to-implement spec.