challenge

Identify and categorize hidden assumptions in designs, implementations, or requirements.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill challenge-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: challenge
Source: https://github.com/sQVe/cape/tree/main/skills/challenge
Command: npx skills add https://github.com/sQVe/cape --skill challenge-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface hidden assumptions in designs, implementations, and requirements before they become expensive mistakes.

Core Features & Use Cases

  • Interactive, turn-based assumption discovery and categorization
  • Risk scoring and constraint documentation to guide decision-making
  • Supports design reviews and audits for scope creep

Quick Start

Initiate a challenge session and surface assumptions one by one.

Frequently Asked Questions about challenge

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

FAQPage Schema
How do I identify hidden assumptions in a design review?

To identify hidden assumptions during a design review, use an interactive, turn-based methodology that surfaces assumptions one by one. Each assumption is then categorized, risk-assessed, and resolved before work proceeds.

What is the best way to audit requirements for scope creep?

Auditing requirements for scope creep involves systematically surfacing and categorizing hidden assumptions within the project scope. This process applies risk scoring to each assumption to prevent costly mistakes and guide decision-making.

How does interactive risk assessment for project requirements work?

Interactive risk assessment works by challenging requirements one turn at a time. It uncovers uncertain assumptions, scores their risk, and documents constraints to ensure every assumption is resolved before implementation proceeds.

Can I run a requirements audit during brainstorming sessions?

Yes, you can apply this assumption challenge methodology during brainstorming sessions when assumptions are uncertain. It interactively surfaces and categorizes assumptions to prevent expensive mistakes early in the process.

When should I use turn-based assumption discovery?

Use turn-based assumption discovery before work proceeds on designs, implementations, or requirements. It is essential when uncertain assumptions exist, ensuring every item is risk-assessed and resolved to avoid costly implementation mistakes.