validate

Validates product ideas through six forcing questions and saves a design document.

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill validate-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/no-session/pstack/tree/main/validate
Command: npx skills add https://github.com/no-session/pstack --skill validate-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders and builders often start coding before confirming anyone actually wants the product. This Skill runs a structured office-hours session that stress-tests demand, target users, and the narrowest paid wedge before any code is written, producing a design document as the only output. ## Core Features & Use Cases - Startup Mode Diagnostic: Six forcing questions covering demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit, with smart routing based on product stage (pre-product, has users, has paying customers). - Builder Mode Brainstorming: Design-thinking collaboration for hackathons, side projects, learning, and open source ideas. - GO / KILL / PIVOT Decision: Ends with a concrete verdict and one actionable assignment, saved as a design doc for the project. - Use Case: A solo founder with a new SaaS idea runs the session before writing code, gets pushed to name a specific paying customer and a one-week wedge, and walks away with a validated (or killed) concept and a design doc. ## Quick Start Ask the assistant to run the validate skill to pressure-test your new product idea before building anything.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate a startup idea before building it?

Run a structured diagnostic that asks six forcing questions about demand evidence, current workarounds, the specific user, and the smallest paid wedge. The session ends with a GO, KILL, or PIVOT decision and a concrete next action.

What questions should I ask to test demand for a product idea?

Ask what evidence shows someone would be upset if the product disappeared, what users do today to solve the problem, who the specific person is that needs it most, and what the smallest version someone would pay for this week looks like.

Can I use idea validation for hackathon or side projects?

Yes. Builder mode handles hackathons, open source, learning, and fun projects with design-thinking brainstorming instead of the hard startup diagnostic. The mode is chosen based on your stated goal at the start of the session.

Does the validation skill write code or scaffold a project?

No. It has a hard gate against implementation: no code, no scaffolding, no implementation skills. Its only output is a design document capturing the validated idea and decision.

When should I run idea validation in my workflow?

Run it before any planning or engineering review, as soon as you have a new product idea. It is designed to precede plan-ceo-review and plan-eng-review so bad ideas get killed before they consume build time.