validate-idea

Validates ideas via a five-question interview and emits a GREEN/YELLOW/RED verdict document.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill validate-idea-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-idea
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/validate-idea
Command: npx skills add https://github.com/me2resh/apexyard --skill validate-idea-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents wasted effort by turning a vague idea into a clear go/no-go decision before you write a full spec.

Core Features & Use Cases

  • Five-question pre-spec gate: Runs a structured one-question-at-a-time interview to surface target user, current alternative, smallest valuable test, kill criteria, and build/buy/rent posture.
  • Backlog-aware validation outputs: Reads idea or project context from the portfolio layout and writes a validation document into the correct per-project validation path.
  • Verdict with guided next action: Produces a GREEN/YELLOW/RED outcome for proceeding, parking, or archiving with appropriate side effects.

Quick Start

Run /validate-idea IDEA-042 to validate a backlog entry by ID and generate a one-page validation verdict ready for the next step.

Frequently Asked Questions about validate-idea

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

FAQPage Schema
How do I validate a product idea before writing a full spec?

Validating a product idea before a spec involves running a five-question interview to assess target user, current alternative, smallest test, kill criteria, and build/buy/rent posture, producing a go/no-go verdict.

What is a pre-spec gate in product management?

A pre-spec gate is a structured validation step that turns a vague backlog idea into a clear go/no-go decision by resolving portfolio paths and generating a single-page validation document before PRD readiness.

How do I decide whether to build, buy, or rent a feature?

To decide whether to build, buy, or rent a feature, a structured validation interview assesses posture alongside kill criteria and smallest valuable tests, yielding a GREEN, YELLOW, or RED verdict.

What kill criteria should I set for my backlog idea?

Kill criteria for a backlog idea are established during pre-spec validation by defining the smallest valuable test and current alternatives, ensuring quick archival of non-viable pitches before PRD writing.

Can I use this for free-form pitch validation or only backlog IDs?

Free-form pitch validation is supported alongside structured backlog entry validation by ID, applying the same five-question interview to generate a one-page validation document with controlled side effects.

What does a GREEN, YELLOW, or RED validation verdict mean for project handover?

A GREEN, YELLOW, or RED validation verdict guides the next action for project handover by indicating whether to proceed with speccing, park the idea, or archive it with appropriate side effects.