vibe-requirements-spec

Draft a Markdown requirements specification from vague coding goals.

Updated Mar 1, 2026

Search Tags:#planning #ideation #requirements #exploration #spec #alignment #drafting

Ready to run

npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-requirements-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-requirements-spec
Source: https://github.com/adhi-jp/agent-skills/tree/main/skills/vibe-requirements-spec
Command: npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-requirements-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn vague coding goals into a structured Markdown requirements specification artifact that clarifies intent and scope without authoring implementation details.

Core Features & Use Cases

Draft, revise, save, and manage a single active requirements spec artifact to guide planning and alignment.
Separate confirmed requirements from ideas, defaults, and open questions, while tracking decisions and risks.
Enforce a disciplined drafting workflow that prevents premature planning and requires explicit approval before downstream work.

Quick Start

Draft a first version of the requirements spec for your vague goal and iterate with a concise summary of decisions.

Frequently Asked Questions about vibe-requirements-spec

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

FAQPage Schema

How do I turn vague ideas into a structured requirements spec?▼

To turn vague ideas into a requirements spec, draft a concise Markdown artifact that clarifies intent and scope. This process separates confirmed requirements from open options and prevents premature implementation planning.

What is the best way to draft requirements for early project exploration?▼

The best way to draft requirements for early exploration is to enforce a disciplined workflow that tracks decisions, risks, and ideas separately. This ensures alignment before any downstream planning begins.

Can I use this requirements drafting process for non-technical goals?▼

Yes, you can use this requirements drafting process for non-technical goals. It applies broadly to brainstorming, alignment, and early creative exploration by clarifying intent without authoring implementation details.

How do you manage a single active requirements spec during brainstorming?▼

You manage a single active requirements spec by drafting, revising, and saving the artifact iteratively. This maintains a clean alignment summary by isolating confirmed requirements from defaults and open questions.

Why does requirements drafting require explicit approval before implementation planning?▼

Requirements drafting requires explicit approval before implementation planning to prevent premature commitments. This disciplined workflow ensures scope and intent are fully aligned before any downstream technical work starts.

thepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community

Advanced

bwgz

design-documentation

Translates approved requirements into comprehensive technical designs with architecture diagrams, component interfaces, data models, and decision logs.

Community

Intermediate