Made for Engineers
Turn the Vague Problem Into Something You Can Solve
Also useful for: Product Owners, Software Engineers, people in Software Engineering, people in Software Engineers
Clarify requests, expose assumptions, set constraints, investigate unknowns, document decisions, and break risky changes into safer delivery steps.
About this collection
Your progress
Sign in to track completion across this collection.
Handle feature requests, bug reports, estimates, technical plans, and partner conversations that start with missing details or unclear tradeoffs.
What you'll walk away with
✓Testable requirements for vague feature requests
✓Hidden assumptions and unknowns surfaced
✓A ranked plan for technical investigation
✓Clear constraints and tradeoffs for solution design
✓Ambiguous bugs and build tickets properly triaged
✓Technical decisions documented in a concise format
Economic outcome
Avoid Professional Risk
Outcomes are illustrative and not guaranteed.
Your Turn the Vague Problem Into Something You Can Solve path
Complete in order for the strongest progression- Prompt
- Guided
- Workflow
- Checklist
- Template
- Playbook
- Sequence
Prompt
Organize Information
Turn a Vague Feature Request Into Testable Requirements
Turn a loose ticket or message into a structured requirement draft that separates confirmed needs from assumptions and unknowns.
Prompt
Make a Decision
Find the Assumptions Hiding in a Technical Plan
Turn a proposed implementation into a ranked assumption register with fast validation checks for the biggest risks.
Guided
Make a Decision
Choose What to Investigate First in an Unfamiliar System
Prioritize the fastest, most useful checks before changing code or committing to a solution.
Guided
Make a Decision
Set Practical Constraints Before Designing the Solution
Define the boundaries a proposed solution must respect before spending time comparing designs.
Workflow
Make a Decision
Triage an Ambiguous Bug Report
Convert a thin bug report into a focused investigation plan without making random code changes.
Checklist
Create a Checklist
Ready-to-Build Ticket Check
Run a fast ticket audit before committing code, estimates, or implementation time.
Checklist
Create a Checklist
Before You Commit to an Estimate
Check whether a work request is clear enough to estimate, then choose a range, a conditional estimate, or a short investigation first.
Template
Compare Options
One-Page Technical Decision Note
Document a technical decision in one page without losing the constraints, unknowns, or tradeoffs that shaped it.
Playbook
Compare Options
Break a Risky Change Into Safe Delivery Slices
Turn one large production change into an ordered delivery plan of small, independently verifiable slices.
Sequence
Have a Conversation
Clarify a Request With a Product Partner
Run a structured product clarification conversation before technical planning begins.