Invocation shapes

How direct requests, handoffs, goals, and casual-build prompts become a bounded work record (audit object).

Any entry shape must become a bounded work record.

A direct task, findings file, handoff, broad goal, or casual build request can start a run.
Before mutation, the agent still has to bind:

scope
owner and source of truth
route
evidence
completion criteria.

The four common shapes

Direct governance

A concrete task, finding list, review, handoff, or bounded plan is already the work target.

Direct governancedirect

/implementaudit fix the failing release test

Embedded governance

A host goal, task, or plan already exists; IMPLEMENTAUDIT governs that target and does not print a second goal.

Embedded governanceinside goal

/goal using /implementaudit, close the findings in AUDIT.md

Goal synthesis

A broad goal becomes a bounded work record before execution or handoff.

Goal synthesissynthesize

/implementaudit audit this repo and give me the next best goal

Governed casual-build intake

A normal build request is accepted only after it becomes scoped repo work with rollback and evidence.

Casual-build intakegoverned

/implementaudit add a login page to this app

The shape changes where the work record comes from; it does not remove the gates.

What to paste

For a first try, paste one concrete request in Claude Code or Codex from the repo you want changed.

Concrete taskstart

/implementaudit add tests for the login timeout bug

If you already have findings, paste that as a separate request instead.

Findings fileaudit

/implementaudit close the findings in AUDIT.md

What gets written

Bound work record (audit object), always.
Run folder under .IMPLEMENTAUDIT/runs/<task-slug>-<id>/ for phased or larger work.
STATE.md, roadmap, and phase checklists when a run folder is used.
Before/after evidence and final audit references for all runs.
Recorded checks before claiming progress.

Source surfaces

README.md invocation modes, skills/implementaudit/references/planning-depth.md, skills/implementaudit/references/goal-format.md, and skills/implementaudit/references/routing.md.

Shape comparison

Direct governance

Work record source: Concrete task, audit file, finding list, handoff, review, or bounded plan.
Goal emitted?: No.
Mutation allowed when: The request is bound to scope, owner/source, route, evidence, and completion criteria.
If blocked: Stop or hand off with the missing boundary named.

Embedded governance

Work record source: The host goal/task/plan already owns the work.
Goal emitted?: No nested goal.
Mutation allowed when: The existing work target is governed in place and the run can prove its gates.
If blocked: Return an honest handoff inside the outer goal.

Goal synthesis

Work record source: A broad idea, gap, or incomplete audit target.
Goal emitted?: Ready-to-paste only; the user must paste it unless already embedded.
Mutation allowed when: Only after the synthesized goal is accepted as a bounded work record.
If blocked: Emit a ready-to-paste handoff or ask only necessary intake questions.

Governed casual-build intake

Work record source: Normal repo-build intent from the user.
Goal emitted?: No by default.
Mutation allowed when: The request has been normalized into scoped repo work with rollback/defer and evidence plan.
If blocked: Refuse unsafe/non-repo input or hand off impossible scope.

A printed /goal line is handoff text, not automatic dispatch.
Slash commands fire only when the user submits them.

Boundary that does not change

Every shape still needs:

owner and source of truth
evidence planning
before/after checks
visible failure handling
final audit closure or handoff.