Workflow extensions · 0.4.1 preview
Make your process part of the project.
Give your coding agent a repeatable path from request to reviewed delivery. Adapt the reviews and checks to your team, and keep the decisions available for the next change—all in Git.
Start with a process you already use
- Deliver a product change
- Prepare a proposal, review the scope, implement it, verify the result and leave a local release handoff.
- Review an incident
- Gather the timeline, separate facts from hypotheses and retain a review. Create follow-up work when you ask for it.
- Share your team's approach
- Package your own workflow, templates and guidance. Choose the reviewer and project checks instead of repeating them in each session.
One change helps the next
In the Beacon example, a request to export bookmarks becomes a reviewed proposal and a verified download feature. The workflow leaves an export-contract decision. A fresh session uses that decision to plan import, including which new choices still need review.
- Request
- Reviewed proposal
- Verified feature
- Retained decision
- Next plan
Read the actual records and next-session response →
Your process, in your repository
An extension is a versioned package of Markdown workflows, templates, guidance and tool recipes. GitDocket installs it under docket/extensions/ by default and records project choices alongside it. Commit those files so another checkout has the same process.
Invoke a workflow by name, such as product-delivery:deliver. Your agent reads its current instructions and configuration, follows the work you authorized, and reports results or an unresolved requirement. You review the proposal and decide the next step. GitDocket manages package validation, task state and update conflicts; the agent follows the review instructions and runs checks.
Proposals, decisions and completed work live elsewhere in your project's linked Markdown. They stay readable when the package is updated or retired. Project choices remain distinct from package defaults; simultaneous local and upstream edits are reported for review.
Use the tools your agent already has
A workflow can read an issue, inspect checks or prepare a handoff using tools exposed by your agent host, including MCP tools. You bind those available tools to the workflow's recipes. Posting a prepared handoff needs your authorization for its content and destination. The extension does not set up connections or credentials.