Confirm the baseline
Identify the applicable SOW, proposal, or other agreed scope document.
Compare a new client request with the agreed scope, cite the evidence, and prepare review-ready internal and client-facing drafts.
For small web, design, marketing, and software agencies.
Launch price
$29
One time for the first 20 qualifying customer orders. Planned standard price: $49.
Checkout activates after Stripe and policy review.
The problem
A rushed request may add a deliverable, channel, format, platform, revision, or technical assumption. Someone must reread the SOW, find the evidence, separate the work, and respond carefully—often while the client is waiting.
Three-step workflow
Identify the applicable SOW, proposal, or other agreed scope document.
Use an email, document, ticket, chat message, or pasted text the host can read.
Receive classifications, evidence, missing information, warnings, and safe drafts.
Fictional before and after
The example below uses fictional data and a tested clear-out-of-scope fixture. It is not a fake Codex or Claude interface.
Before
A client asks for LinkedIn advertising creative, an immediate price, and a March 28 delivery promise inside a website project.
After
The request is separated, classified out of scope with high confidence, cited to the SOW, and converted into neutral drafts with human placeholders.




Five possible outcomes
Direct evidence includes the requested work within the applicable limits.
Direct evidence identifies a new, excluded, or limit-exceeding request.
The supplied language supports more than one reasonable interpretation.
Material project documents disagree and authority cannot be selected safely.
A usable baseline, request, attachment, status, or readable source is missing.
The product includes a complete operating procedure, evidence rules, uncertainty controls, stop conditions, a structured schema, editable configuration, five fictional fixtures, expected outputs, deterministic validation, installation instructions, and troubleshooting.
Use local files, PDF, DOCX, email, SharePoint, Google Drive, project systems, or pasted text when your Codex, Claude, or compatible host is already authorized to access them. The kit does not create those connections or bypass access controls.
Clear commercial boundary
The workflow prepares operational analysis without pretending to approve legal, commercial, or delivery decisions.
Buyer ZIP, upload-ready skill ZIP, unpacked skill folder, documentation, configuration, fictional examples, tests, validator, renderer, license draft, and changelog.
Launch offer
$29
One-time purchase. First 20 completed, non-refunded customer orders; then $49.
No payment is being accepted until Stripe, delivery, and reviewed policies are connected.
Product FAQ
No. It includes a reusable skill, five rule sets, a structured output contract, configuration, fictional fixtures, expected outputs, validation tools, tests, installation instructions, and buyer documentation.
At minimum, a readable baseline scope document and an intelligible client request. Project status, amendments, briefs, rate cards, and agency policies can improve the result when relevant.
No. The workflow can use PDF, DOCX, email, SharePoint, Google Drive, project systems, local files, and pasted text when your host is already authorized and able to read them reliably.
No for normal analysis. Python 3 and PyYAML are optional and used only for deterministic validation, Markdown rendering, and local tests.
No. The product runs in your own compatible AI host and uses only the sources you choose to provide there. Do not send client contracts or confidential project files to the planned support address.
No. It is an administrative productivity aid, not legal advice. It does not decide breach, waiver, enforceability, rights, remedies, or legal document authority.
No. Price and delivery impact remain human-entered placeholders. The skill may prepare neutral wording for review, but it never sends it or marks approval complete.
The original purchaser receives fixes, documentation updates, and minor improvements released within version 1.x. Future major versions, integrations, and bundles are not promised.
The planned 14-day practical-use policy covers duplicate charges, inaccessible delivery that cannot be replaced, material differences from the product description, and documented installation failure on an advertised compatible host that support cannot resolve. Final reviewed terms will be published before checkout.
Checkout will open after final setup