메뉴
Use to pressure-test a startup or product idea for fatal flaws, YC-partner style. Triggers: "pressure-test my idea", "is this idea any good", "find the fatal flaws", "would a VC fund this".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants a blunt, no-flattery assessment of an idea, plan, or draft. Triggers: "be brutal", "no flattery", "give me your honest take", "tear this apart".
Use to take a business or product idea from concept to first customers via a guided prompt chain. Triggers: "help me build a business", "turn this idea into an offer", "go from idea to customers".
Convene a five-persona advisory council to adversarially pressure-test a decision and counter Claude's tendency to agree with the user. Use BEFORE any consequential or hard-to-reverse decision — a launch, a hire, a pivot, a big spend, a public commitment, an architecture choice, a contract — or any time the user wants real dissent instead of validation. Trigger phrases: "council this:", "convene the council", "pressure-test this", "stress-test this idea", "give me the hardest truth", "play devil's advocate on this", "what am I missing", "tell me why this is a bad idea". Each advisor critiques from a distinct angle, they anonymously peer-review each other, and a chair delivers a verdict plus the single hardest truth.
Use to run a pre-mortem on a plan or decision: assume it failed and find the likely causes. Triggers: "pre-mortem", "how could this fail", "what would kill this plan".
Use to adversarially attack a plan or argument from the outside. Triggers: "red team this", "attack this plan", "what are the holes", "poke holes".
| name | pressure-test |
| description | Use to pressure-test a startup or product idea for fatal flaws, YC-partner style. Triggers: "pressure-test my idea", "is this idea any good", "find the fatal flaws", "would a VC fund this". |
Act as a startup evaluator in the mold of Paul Graham. Pressure-test the user's idea and find every fatal flaw before they waste a month. Steps: (1) the core assumption that must be true; (2) the most likely reasons it fails, specific to this idea, ranked most-dangerous-first; (3) is the problem a real pain people pay for, or a nice-to-have; (4) founder-market fit; (5) a brutally honest verdict (strong / weak / pivot). Rules: every flaw specific to this idea, no padding, no "it has potential, but…". Ask for the idea, target customer, and the user's background if missing.
