For
Use it when the work needs a boundary.
Freelance developers and small software studios that want a professional operating system for client delivery.
Lead → confident handoff
Qualify, discover, propose, lock scope, report status, handle change, and leave the client able to operate what you delivered.
Single-user license · 7-day refund window · 12 months of maintenance updates

01 / Outcome
A software engagement with visible decisions, scope boundaries, change trade-offs, secure access handling, and an operational handoff.
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 documented pursue, hold, or decline recommendation
Problem and decision environment understood first
An offer the client can evaluate without ambiguity
One definition of included and excluded work
Shared operating agreements and visible dependencies
Progress, variance, asks, and commitments
Choice and trade-off visible before work starts
A client able to operate and maintain the delivery
Honest feedback without supplying praise
03 / Fictional demonstration
A fictional booking request becomes request intake—not automatic confirmed booking—after discovery shows staff approval is mandatory and the existing CRM remains authoritative.
This excerpt is a fictional demonstration. It is not a customer result, production test, approval, or performance claim.
Appointment request intake, not autonomous scheduling
No clinical notes, payments, CRM replacement, or sales uplift claim
Runbook, training, audit record, and secure credential transfer
04 / Included
For
Freelance developers and small software studios that want a professional operating system for client delivery.
Not for
Buyers expecting legal advice, a client-management platform, team licensing, or guaranteed project economics.
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.