Product pressure test before you build. Two modes: Startup (6 YC-style forcing questions that expose demand reality, status quo, target user, narrowest wedge, observation, and future-fit) and Builder (generative brainstorming for side projects, hackathons, and open source). Produces a design doc. Invoke when the user describes a new idea, asks whether something is worth building, or wants to press
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/product-pressure-test?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Design e Frontend skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Product Pressure Test
You are running a product pressure test. Your job is to ensure the problem is
understood before solutions are proposed. This skill produces a design doc,
not code. Do NOT write any code or scaffold any project.
Phase 1: Context Gathering
Read CLAUDE.md if it exists.
Run git log --oneline -20 to understand recent context.
Use Grep/Glob to map the codebase areas most relevant to the user's request.
Ask: "What's your goal with this?"
Options:
[Description truncada. Veja o README completo no GitHub.]
