For
Use it when the work needs a boundary.
Developers, product-minded freelancers, and solo founders who need a decision-complete brief before they build.
Idea → specification
Frame the product, expose consequential unknowns, map the user flow, resolve decisions, and define acceptance before implementation begins.
Single-user license · 7-day refund window · 12 months of maintenance updates

01 / Outcome
A bounded software specification with traceable decisions, explicit non-goals, an implementation sequence, and observable acceptance tests.
When the evidence is incomplete, the workflow narrows the conclusion, marks the gap, and returns the next verification instead of inventing project facts.
02 / Workflow
A one-page product frame without false certainty
Facts, evidence, inference, and unknowns kept separate
User and system behavior aligned step by step
Material ambiguity turned into reviewable choices
One bounded implementation reference
Buildable vertical slices tied to the spec
Observable behavior for review and testing
03 / Fictional demonstration
A fictional clinic request starts with an unchosen email provider and unknown retry rules. The workflow does not fill those gaps with guesses; it separates what can be specified now from what blocks integration and release approval.
This excerpt is a fictional demonstration. It is not a customer result, production test, approval, or performance claim.
One email, 24 hours before a confirmed appointment
Provider, consent evidence, retry ceiling, approved copy
Requirements, non-goals, acceptance scenarios, next verification
04 / Included
For
Developers, product-minded freelancers, and solo founders who need a decision-complete brief before they build.
Not for
Buyers looking for automated market validation, stakeholder approval, vendor access, or guarantees that a product will succeed.
05 / Questions
No. Each workflow has a narrow trigger, required inputs, a procedure, an output contract, and rules for handling missing evidence.
The native filesystem skills are designed for Codex and Claude custom Agent Skills. Portable copy-and-paste prompts are included for other assistants. Availability depends on the model, plan, tools, and permissions you use.
No bundled workflow contains scripts or hidden network calls. A workflow may guide an assistant that already has tools, but consequential actions still require the user's authorization.
No. Results depend on the context supplied, available evidence, model capability, tool access, and human review.
Native skills, portable prompts, templates, worked examples, and a practical quick start.