Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/install/models-and-effort.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ 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. `docket-link-ticket` runs inline too, because it works with you and posts
through your session's connector.
through your session's connector. `docket-update-ticket` runs inline as well, for the same reason.

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

Expand Down Expand Up @@ -109,7 +109,8 @@ the two interactive brainstorm skills (`docket-new-change`, `docket-groom-next`)
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, nor
`docket-link-ticket`, which works with you and posts through your session's connector.
`docket-link-ticket`, which works with you and posts through your session's connector, nor
`docket-update-ticket`, which posts through it too.

**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
2 changes: 1 addition & 1 deletion docs/reference/cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Each line is a pointer: the command, what its verbs govern, and where to read th
repository-independent). Verbs: `docket capabilities --help`.
- **`docket change`** — create and transition changes in the backlog. Verbs: `docket change --help`
(`docket schema` lists the request keys, including `hold`).
- **`docket context`** — assemble read-only context bundles for the implementation workflow. Verbs: `docket context --help`.
- **`docket context`** — assemble read-only context bundles for docket workflows (implementation, finalize, ticket updates). Verbs: `docket context --help`.
- **`docket development`** — contributor operations against a docket checkout: install from a
checkout and run the complete test suite. Verbs: `docket development --help`.
- **`docket diagnostic`** — read-only diagnostics, including the resolved configuration
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/config-keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,9 +57,9 @@ Each key has one scope:
| `board.section_order` | `[in-progress, built, blocked, groomed, proposed, deferred]` | any layer | the order of the board's sections |
| `board.sorting.<section>.by` / `.direction` | `updated` / `desc` | any layer | how each board section is sorted |
| `change_types` | `[chore, docs, feat, fix, refactor, perf]` | any layer | the types a change can be classified as |
| `tickets.provider` | `""` (unset) | repo-only | the ticket system this repository's changes link to (jira, linear, …); no effect yet |
| `tickets.site` | `""` (unset) | repo-only | where that ticket system lives; no effect yet |
| `tickets.project` | `""` (unset) | repo-only | where new tickets go (a project, team, repository, or board, by tool); no effect yet |
| `tickets.provider` | `""` (unset) | repo-only | the ticket system this repository's changes link to (jira, linear, …); used when linking or creating a ticket |
| `tickets.site` | `""` (unset) | repo-only | where that ticket system lives; used when linking a ticket by URL or id |
| `tickets.project` | `""` (unset) | repo-only | where new tickets go (a project, team, repository, or board, by tool); used when creating a ticket |
| `tickets.auto.change_created` | `false` | repo-only | a switch for when a change is created; no effect yet |
| `tickets.auto.spec_written` | `false` | repo-only | a switch for when a change's spec is written; no effect yet |
| `tickets.auto.pr_opened` | `false` | repo-only | a switch for when a change's pull request opens; no effect yet |
Expand Down
28 changes: 25 additions & 3 deletions docs/reference/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -849,6 +849,16 @@ and recorded branch.
docket context implementation --id 412 --json
```

### Ticket context

The read-only bundle `docket-update-ticket` reads before posting: the change's ticket link, the
repository's visibility, whether the event has happened, the facts behind it, and spec and results
links pinned to the metadata commit the read took.

```sh
docket context ticket --id 412 --event pr_opened --json
```

### Implement-next / the drainer

`docket-implement-next` — the autonomous workflow that picks the next build-ready change (or the
Expand Down Expand Up @@ -1836,6 +1846,16 @@ inline.
@docket-status # agent-dispatch: same pinned run, drillable live
```

### docket-update-ticket

The skill an agent session uses to post an update to a change's linked ticket when you ask. It posts
one short comment through your session's own connector, with spec and results links pinned to the
commit that holds them, and reports the update as posted only when the connector confirms. In a
private repository it posts nothing yet.

**Used for:** telling people in the ticket system that something happened. It runs inline, because
it posts through your session's connector.

### Fork / forked skill

On harnesses that support it, a skill can run as a fork of the current context rather than a fresh
Expand All @@ -1848,7 +1868,7 @@ back to the human. The forked skills are `docket-status`, `docket-adr`, `docket-
`docket-auto-groom` (`context: fork` + `agent:` frontmatter).

**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.
`docket-link-ticket`, `docket-update-ticket`, and `docket-finalize-change` run inline. A headless finalize is authorized by naming ids instead.

### Harness

Expand All @@ -1872,8 +1892,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` and `docket-link-ticket` also stay inline, because they post with your session's own
tools and work with you before posting.
`docket-export`, `docket-link-ticket`, and `docket-update-ticket` also stay inline, because they
post with your session's own tools.

**Used for:** knowing which skills you can dispatch and walk away from, and which need you at the
keyboard.
Expand Down Expand Up @@ -2385,6 +2405,7 @@ docket development install --source ~/dev/docket
- [docket-new-change](#docket-new-change)
- [docket-review](#docket-review)
- [docket-status](#docket-status)
- [docket-update-ticket](#docket-update-ticket)
- [Drive disposition: WAITING / PASSED / FAILED / HALTED](#drive-disposition-waiting--passed--failed--halted)
- [Effects](#effects)
- [Escalation (NEEDS_ESCALATION)](#build-tier--escalation) — see Build tier / escalation
Expand Down Expand Up @@ -2496,6 +2517,7 @@ docket development install --source ~/dev/docket
- [Suite gate](#suite-gate)
- [Sweep](#sweep)
- [Sync integration](#sync-integration)
- [Ticket context](#ticket-context)
- [Tri-state verdict / halt exit code](#tri-state-verdict--halt-exit-code)
- [Two invocation paths: skill-invoke vs agent-dispatch](#two-invocation-paths-skill-invoke-vs-agent-dispatch)
- [Uninstall](#uninstall)
Expand Down
1 change: 1 addition & 0 deletions docs/reference/skills-and-agents.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ Each line names one skill directory under `skills/` and its job.
- **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.
- **docket-update-ticket** — post a short update to a change's linked ticket when you ask (spec written, PR opened, PR merged, results completed, or a revision, blocker, or kill), with links pinned to the commit that holds them; shared repositories only for now.

## Default workflow roles

Expand Down
Loading
Loading