Codex
Claude
GeminiWhat you do
- Supply the engagement identity and brief context, with optional agency association, guidance, and finance navigation pointer.
- Review the saved engagement record and separately decide whether to set up exact finance workflows.
Solo operators and agencies organizing lightweight client-engagement context. / agency
Client Project Setup
One read-back-verified client-project context record and, only when exactly selected, a no-launch finance setup handoff.
From request to resultA complete plan you can follow.
Visible planThe problem
Agency and standalone operators need durable engagement orientation without inventing a second project-management or finance system.
What the agent does
- Inspect current-project engagement records and resolve an existing or stable new engagement reference from supplied identity before strict run validation.
- Resolve any supplied or preserved agency association only against agency-profile resources in that same current project; stop before writing if it is unresolved.
- Merge supplied facts with permitted existing optional context, persist one engagement record, and read it back.
- Return a setup_existing finance handoff only for exact selected workflow keys; do not launch it.
When this workflow helps
A reusable method, adapted to the request.
- A client engagement needs minimal durable context in an agency or standalone workspace.
- An existing engagement context needs a reviewed update under its stable reference.
Before it starts
Ready with project context
- A currently bound StackOS project and operator-supplied engagement identity.
What proves it worked
Evidence, not a success claim.
- One queryable client-project context record
- readback evidence
- and a bounded optional finance handoff.
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Inventory Existing Engagement Context
Inspect bounded current-project project-context records and resolve one stable engagement identity.
- 02Passes to next stage
Resolve Supplied Engagement Facts
Produce the complete write payload by merging supplied facts with permitted existing optional context.
- 03Passes to next stage
Persist Client Project Context
Upsert the resolved complete engagement payload under its stable external id.
- 04Verified outcome
Read Back And Hand Off
Verify the saved engagement resource and return the optional finance setup handoff without executing it.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop after engagement context is verified. Finance setup is a separate optional handoff and is never started implicitly.
- If stable engagement identity conflicts with existing context, stop for operator direction rather than overwriting or creating a duplicate.