What problem does it solve? Plans, specs, and designs often contain hidden assumptions, unresolved tradeoffs, and unexamined branches that only surface during implementation. This Skill stress-tests an existing plan by relentlessly interviewing the user about every aspect of it, walking down each branch of the decision tree until shared understanding is reached. ## Core Features & Use Cases - Relentless decision-tree interrogation: Walks each branch of the design tree one question at a time, resolving dependencies between decisions and providing a recommended answer for every question. - Codebase-grounded answers: When a question can be answered by exploring the codebase, it explores the code instead of asking the user, keeping the interview evidence-based. - Workflow signal integration: Emits best-effort beislid workflow-signal events (working, waiting, blocked, done) so external tools can observe interrogation state; the command no-ops safely when unconfigured. - Optional visual decision-tree surfaces: When repo-level beislid:visual_surfaces config is active, it can render decision trees, tradeoff matrices, and risk maps as supplemental Lavish-backed HTML surfaces with typed feedback gates, while Markdown/chat remains canonical. - Use Case: After drafting an implementation plan for a database migration, say "poke holes in this plan" and the Skill will grill you on rollback strategy, data consistency, downtime windows, and dependency ordering until every branch is resolved. ## Quick Start Say "poke holes in this plan" or "stress-test this design" while pointing at an existing plan, spec, or design document.
