plan-pressure-test

Evaluate product ideas with six forcing questions and scope mode recommendations.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/QuestionPilot/authored-skills --skill plan-pressure-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-pressure-test
Source: https://github.com/QuestionPilot/authored-skills/tree/main/skills/plan-pressure-test
Command: npx skills add https://github.com/QuestionPilot/authored-skills --skill plan-pressure-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you pressure-test product ideas, features, or plans before investing in build effort, ensuring you're making informed decisions.

Core Features & Use Cases

  • Forcing Questions: Run through a structured set of six forcing questions to evaluate the viability of an idea.
  • Scope Modes: Recommend one of four scope modes based on the answers to the questions.
  • Taste-Decision Gate: Separate mechanical/determinate answers from genuine taste decisions requiring operator input.
  • Output: Provide a concise decision guide with findings and recommendations.

Quick Start

Use the plan-pressure-test skill to evaluate a new feature idea for your project.

Frequently Asked Questions about plan-pressure-test

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

FAQPage Schema
How do I evaluate product ideas before committing to development?

Product idea evaluation involves running a proposed plan through structured interrogation using six forcing questions to test viability and determine scope. This process separates mechanical answers from taste decisions, yielding a concise decision guide with actionable recommendations.

What is the best way to determine the scope of a new product feature?

Determining feature scope involves answering a structured set of six forcing questions that evaluate the idea's viability. Based on your responses, the process recommends one of four scope modes to guide your product planning and build effort.

How do I pressure-test a project plan to avoid building the wrong features?

Pressure-testing a project plan requires applying structured interrogation to challenge the feature's viability before investing build effort. A taste-decision gate separates objective answers from subjective choices requiring your operator input, preventing unnecessary development.

Can I use structured interrogation for project scoping without prior planning experience?

Structured interrogation for project scoping is accessible without prior experience because the process provides a fixed set of six forcing questions. However, you must provide operator input at the taste-decision gate to resolve genuine subjective choices.

When should I not use structured interrogation for feature evaluation?

Structured interrogation for feature evaluation should be avoided when a project requires immediate execution without a viability check, or if you cannot provide the necessary operator input for taste decisions required by the decision guide output.