Skip to content
Merged
6 changes: 4 additions & 2 deletions docs/install/models-and-effort.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ design, a cross-cutting change, or a stub whose premise needs tracing through th
your strongest model at higher effort.

`docket-export` also runs inline at your session's model and effort; it runs one export and needs
no particular model.
no particular model. `docket-link-ticket` runs inline too, because it works with you and posts
through your session's connector.

To change the model or effort an autonomous skill runs at:

Expand Down Expand Up @@ -107,7 +108,8 @@ the two interactive brainstorm skills (`docket-new-change`, `docket-groom-next`)
`docket-finalize-change` (which keeps a real prompt — the multi-candidate batch confirmation — so a
headless drive is authorized by
[naming ids](../guide/landing-changes.md) instead) do not, and neither does `docket-export`, which
posts through your session's own tools and may ask you before a private-repository post.
posts through your session's own tools and may ask you before a private-repository post, nor
`docket-link-ticket`, which works with you and posts through your session's connector.

**The two invocation paths.** **Dispatch** — launching a named agent to do a step and waiting for it
to return — is one way to reach a pinned wrapper; a plain skill-invoke, forked, is the other. Both
Expand Down
20 changes: 15 additions & 5 deletions docs/reference/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -1757,7 +1757,7 @@ docket. It runs the `open` operation's export (`--export --print --json`) and pa
to a file or another tool, never the raw file. In a private repository it also rewrites what the
export leaves that names docket, checks the result, and shows you before → after before posting.

**Used for:** putting a spec or other artifact into a ticket, document, or message from an agent
**Used for:** putting a spec or other artifact into a document or message from an agent
session. It runs inline, because it posts with your session's own tools and may ask you first.

### docket-finalize-change
Expand Down Expand Up @@ -1789,6 +1789,15 @@ stub rather than groom it, routes to `revise`. It runs inline at the session mod
/docket-groom-next 412
```

### docket-link-ticket

The skill an agent session uses for ticket work. It links a change to an existing ticket, creates a
ticket from a change, or makes a change from a ticket, working through your session's own
connector tools for the ticket system. It records a link only after the connector confirms.

**Used for:** handing a change to a ticket system or pulling a ticket in. It runs inline, because it
needs you present and posts through your session's connector.

### docket-new-change

The interactive producer, and the entry point a human runs to propose work. It allocates the change
Expand Down Expand Up @@ -1838,8 +1847,8 @@ Only skills that never need the human mid-run are forked, because a forked subag
back to the human. The forked skills are `docket-status`, `docket-adr`, `docket-implement-next`, and
`docket-auto-groom` (`context: fork` + `agent:` frontmatter).

**Used for:** explaining why `docket-new-change`, `docket-groom-next`, `docket-export`, and
`docket-finalize-change` run inline. A headless finalize is authorized by naming ids instead.
**Used for:** explaining why `docket-new-change`, `docket-groom-next`, `docket-export`,
`docket-link-ticket`, and `docket-finalize-change` run inline. A headless finalize is authorized by naming ids instead.

### Harness

Expand All @@ -1863,8 +1872,8 @@ every harness. It is program data, not user config, and each harness block is co
abort-and-report rule: implement-next, auto-groom, finalize-change, status, adr, build-task, and
review. **Interactive** skills (`docket-new-change`, `docket-groom-next`) stay inline at the session
model, because the conversation with you is the point. They only advise a model at startup.
`docket-export` also stays inline, because it posts with your session's own tools and may ask you
first.
`docket-export` and `docket-link-ticket` also stay inline, because they post with your session's own
tools and work with you before posting.

**Used for:** knowing which skills you can dispatch and walk away from, and which need you at the
keyboard.
Expand Down Expand Up @@ -2372,6 +2381,7 @@ docket development install --source ~/dev/docket
- [docket-export](#docket-export)
- [docket-finalize-change](#docket-finalize-change)
- [docket-groom-next](#docket-groom-next)
- [docket-link-ticket](#docket-link-ticket)
- [docket-new-change](#docket-new-change)
- [docket-review](#docket-review)
- [docket-status](#docket-status)
Expand Down
3 changes: 2 additions & 1 deletion docs/reference/skills-and-agents.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,11 @@ Each line names one skill directory under `skills/` and its job.
- **docket-build** — the build role: route each plan task to a tier worker and run one full-suite gate at the end.
- **docket-build-task** — the per-task worker contract: one plan task from focused test through one commit.
- **docket-convention** — the shared contract: config, layout, manifest and ADR format, lifecycle, branch model (pure reference).
- **docket-export** — export a change, spec, plan, or results file through docket's own export, or put one into another tool; in a private repository it also rewrites docket references out and shows you before posting.
- **docket-export** — export a change, spec, plan, or results file through docket's own export, or put one into a document, message, or email; in a private repository it also rewrites docket references out and shows you before posting.
- **docket-finalize-change** — close a change out: merge if approved, verify, archive, clean up, refresh the board.
- **docket-groom-next** — groom the next needs-grooming change to build-ready through an interactive brainstorm.
- **docket-implement-next** — implement the next build-ready change end to end to an open PR with no human interaction.
- **docket-link-ticket** — link a change to a ticket in your team's ticket system, create a ticket from a change, or make a change from a ticket; always with you present.
- **docket-new-change** — capture a new unit of planned work into the backlog through up-front design.
- **docket-review** — the bounded read-only whole-branch reviewer role.
- **docket-status** — refresh the backlog, sweep merged changes to done, and run health checks.
Expand Down
Loading
Loading