What problem does it solve? Teams often jump from a vague idea straight to implementation, converging on the first solution proposed without examining the problem, the evidence, or cheaper alternatives. This Skill runs a structured discovery interview that turns an unshaped idea into a confirmed verdict and a design document with literal decisions. ## Core Features & Use Cases - Structured Discovery Interview: Walks through Situation, Problem, Evidence, Journey, and Verdict phases, asking only answerable questions with recommended answers. - Two-Shape Decision Framework: Compares a lighter and a heavier technical shape against the actual repository, with explicit conditions for when each wins. - Design Document Output: Produces a .design/<name>.md file with Decisions, Roadmap, RFC/spike/design handoffs, and Sources that feeds directly into pbs-plan. - Use Case: When a stakeholder says "we should add caching" or "should we build this feature", run this Skill to recover the underlying problem, measure its cost, reach a build/not-build verdict, and record concrete decisions before any planning begins. ## Quick Start Ask the agent to run pbs-discover on your idea, for example: "Use pbs-discover to research whether we should build a notification system for this project."
