GitDocket
Workflow extensions
Make your process part of the project.
Give your coding agent your team’s steps for planning, building, and reviewing a change. Save the templates and checks in your repository so you can reuse them next time.
Start with a process you already use
- Deliver a product change
- Write a proposal, review the scope, build the feature, and check the result.
- Review an incident
- Gather the timeline, investigate what happened, and record what to do next.
- Bring a list into planning
- Read an external list through an agent connection, cite its items, and review proposed project work.
- Share your team’s approach
- Save your workflow and templates so each session starts with the same instructions.
Bring an external list into a project plan
Notion is an illustrative source. If your agent already has an authorized Notion connector or MCP tool, an extension can guide it to read a selected list, keep links to the source items, and draft a planning proposal in your repository. Create Docket tasks from that proposal only when you explicitly ask.
Example request: “Read the launch list in my connected Notion workspace. Cite each item and draft a project plan in this repository. Ask me before creating tasks.”
- Connect the source to your agent and authorize the needed read access.
- Configure a list-reading workflow with the source and a binding to the tool your agent already exposes.
- Ask the agent to follow the workflow, then review the sourced proposal before recording any requested work items.
The extension supplies reusable instructions, configuration and tool bindings. It does not install a connector, manage credentials or provide background synchronization. No ready-made Notion extension or live Notion validation ships here. The Beacon walkthrough shows retained project records; its verification and provenance include a real local MCP fixture with synthetic inputs, not a live third-party provider.
One change helps the next
In the Beacon example, an agent adds bookmark export and records the file format it chose. A fresh session finds that decision and uses it to plan import.
- Request
- Reviewed proposal
- Checked change
- Recorded decision
- Next change
Read the proposal, decision, and next-session response →
Keep the workflow with the project
An extension is a package of Markdown workflows, templates, guidance, and tool instructions. GitDocket installs it under docket/extensions/. Commit those files and your project choices so another checkout has the same process.
Ask your agent to use a named workflow, such as product-delivery:deliver. It reads the instructions, prepares the work, and brings the result back for review. You can choose the reviewer, change the checks, and adapt the templates.
Your proposals, decisions, and completed work stay in the project when you update or remove an extension. GitDocket manages package updates and flags conflicts with your edits.
Use the tools your agent already has
A workflow can use connected tools to read an issue, inspect checks, or prepare a handoff. It uses your agent’s existing connections and permissions. You decide when to send a handoff or publish a result.
The agent follows the workflow’s instructions and runs the checks. Review steps depend on those instructions being followed; installing an extension does not set up external services or enforce approvals automatically.