tryveto/veto-codex

Implement or repair a Veto capability, local setup or CI; handle Git source handoffs and authorized preview delivery. Not read-only audits, planning, production operations or payment execution.

Design or analyze a permissioned Veto user study or benefit comparison. Use for comprehension, burden, adoption and repeat-choice evidence; not synthetic customer validation.

Form and defend an evidence-based recommendation on a consequential product or engineering choice, including disagreement with the founder. Not for manufacturing objections to routine work.

Select, specify or qualify a Veto integration or WorkOS environment/authentication boundary. Use for a consequential external route or auth configuration review; not routine inbox work or a connector catalog.

Write, adopt or revise a Veto goal below 4,000 characters. Separate the accepted vision from a bounded active bet; use native action and readback for adoption, and preserve scope and pause.

Design Veto interactions, shared UI contracts/tokens, authorized structural changes or approved reference implementations. Use remove-slop for a bounded craft pass on an existing surface.

Choose Veto product priorities, first features, surfaces, or scope. Use for an unsettled product decision; not a routine approved implementation or cosmetic edit.

Define, run or assess Veto acceptance, Git candidate identity and WorkOS auth evidence; plan scoped production verification. Does not grant repair, release, access or customer-contact permission.

Critique or refine an existing Veto interface: remove decorative eyebrows, repetition, fake reassurance and broken interaction. Preserve approved structure; critique stays read-only.

Package or independently review a working prototype at an exact candidate. Use for Pro feedback or team-owned walkthroughs; not as a production release or customer-validation claim.

Make Veto sandbox tasks self-serve: safe sample inputs, scenario controls, coherent state, reset and recovery. Use for demos or rehearsals, not production operations or OS isolation.

Carry an authorized Veto outcome from context through working evidence and handoff. Select the needed procedure, coordinate contained help, and resume prior work without founder coaching.

Manage Veto feedback, queued follow-ups, steering, pause/resume and bounded goals. Use for changed priorities or ongoing-work control, not to add planning to a clear isolated edit.