Hapimatic
Menu

Paid add-on · hosted service

Issue Workflow

Your GitHub issues become the work queue.

Every issue moves through formatted, researched, implemented, tested, and closed, with the evidence attached, and anyone with access to the repo can see what is being worked and in what state. The Issue Workflow can seed into an existing repo with issues already in progress; no preparation necessary.

Contact us about hosted pilotsIn pilot — contact us
✅ checkpoint: ✨ created ✅ checkpoint: ✨ created issue-creatora sentence becomes an issue ✅ checkpoint: 📊 formatted ✅ checkpoint: 📊 formatted issue-formatterrequirements, criteria, risk ✅ checkpoint: 📝 researched ✅ checkpoint: 📝 researched issue-researcherthe plan and its confidence ✅ checkpoint: 🧠 expert-reviewed ✅ checkpoint: 🧠 expert-reviewed issue-expert-revieweroptional: an expert checks it ✅ checkpoint: 🔨 worked ✅ checkpoint: 🔨 worked issue-workerimplemented in its own worktree ✅ checkpoint: 🧪 tested ✅ checkpoint: 🧪 tested issue-testerverified as a user would use it ✅ checkpoint: 👁️ refactor-reflected ✅ checkpoint: 👁️ refactor-reflected issue-refactor-reflectorfresh eyes, then your approval ✅ checkpoint: ☑️ closed ✅ checkpoint: ☑️ closed issue-closerreviewed, merged, summarised OpenOpen Closed Session list forgets expandedprojects on reload #128 📋 Overview✅ Requirements · 🎯 Acceptance🧪 Research plan · 94%🧠 Expert review: plan refined3 commits · PR #131 openedProof: 214 tests · 2 screenshotsApproved by youMerged · 📋 Closing Summary labels on the issue
fig. 1 — an issue moves through the workflow's labels

Why it matters

  • The issue is the unit of work

    Its state, its plan, and its evidence live on the GitHub issue, not in one agent's context. Close the session and nothing is lost.

  • You approve. Agents do the rest.

    Work stops at the gates you choose. Between them, agents format, research, implement, and test without being asked twice.

  • Everyone sees the same queue

    Anyone with access to the repo can see what is being worked and in what state.

How it works

  1. FormattedA rough request becomes a structured issue: requirements, acceptance criteria, risk, and size.
  2. ResearchedAn agent reads the code, writes the implementation plan, and states its confidence before anything changes.
A GitHub issue after the Issue Workflow has formatted and researched it: the template body (overview, requirements, acceptance criteria, risk, and status), the researcher's handoff with its confidence, the state labels with their emoji, the milestone, and the parent epic.
On GitHub: the formatted issue, its research handoff, and the labels that carry its state
  1. ImplementedA session works the plan in its own worktree and commits against the issue.
  2. TestedThe change is verified the way a user would use it, and the proof is attached to the issue.
  3. ClosedAfter your approval: review, pull request, merge, and a closing summary on the issue.
The same issue closed: the timeline on GitHub shows each checkpoint label as it was added, the commits, your approval, the merged pull request, and the closing summary with its evidence.
On GitHub: every step of the workflow, recorded on the issue
The Hapimatic session header with a linked issue: the issue's current workflow label is shown in the session itself and updates as the issue moves.
In Hapimatic: the session header carries the issue's state
A GitHub Projects v2 table: every open item with its status, wave, tier, lane, labels, and sub-issue progress.
On GitHub: the program board, table view
The same project as a board: Todo, In Progress, and Done columns with the issue cards and their labels.
On GitHub: the program board, board view

What it can do

  • Start from a sentence: create an issue, research it, work on it
  • One session per issue, each in its own worktree; multiple sessions working in parallel
  • Evidence on the issue: plans, test results, and screenshots
  • Approval gates before anything merges
  • Epics: a parent issue that tracks and orders its sub-issues
  • Milestones that show how much of a release is done
  • The Issue Workflow can seed into an existing repo with issues already in progress; no preparation necessary

In use

In a session
  1. create an issue: the session list forgets expanded projects on reload
  2. research issue 128
  3. work on issue 128
  4. approve issue 128
A finished, well-formatted issue on GitHub as an iPhone shows it: the state labels with their emoji, the template body with every box ticked, and the closing summary.
On GitHub, on a phone: a finished issue

In pilot — contact us

A paid add-on of the hosted service. It is not part of the open-source core.

Contact us about hosted pilots

Paid add-ons for the hosted service

These are paid add-ons of the hosted service. They are not part of the open-source core.

  • Paid add-on

    Issue Workflow

    Your GitHub issues become the work queue.

    • Every issue moves through formatted, researched, implemented, tested, and closed, with the evidence attached
    • Anyone with access to the repo can see what is being worked and in what state
    • The Issue Workflow can seed into an existing repo with issues already in progress; no preparation necessary
    Explore the Issue Workflow →
  • Paid add-on

    Project Manager

    An agent that runs the fleet for you

    • The Project Manager spawns peer sessions and hands each one an issue from your plan
    • It monitors every session on a schedule and unblocks what it can, so work continues with nobody watching
    • It reports back to you in its own session and brings you only the decisions that are yours to make
    Explore the Project Manager →
  • Paid add-on

    Hardware Bench

    Extend your agent's reach into the physical world with sensors, actuators, lab instruments, PCB design software, and more.

    • A bench camera lets your agent see the board, the indicator LEDs, and the instrument screens
    • Your agent drives the lab instruments: it loads a rail, profiles the current, and captures an oscilloscope waveform
    • It reads the schematic and edits the BOM and the PCB layout in KiCad to carry the fix through
    Explore the Hardware Bench →