What's inside
Four surfaces. One workflow.
Every surface earns its place, either by saving your team time or by giving the agents the context they need to ship the next one.
Surface 01 · Inbox
The things waiting on you
The PM's landing page. Every item the agents are blocked on: a Plan waiting for approval, a QA failure that needs a call, a release ready to ship. Items disappear when actioned. Inbox zero is real.
- Urgency filter chips: All · Urgent · Plan reviews · Blockers
- One-click action CTAs per row: Review draft, Approve handoff, Ship it
- Real-time updates as agents move work between stages
Surface 02 · Cards
Every card carries its whole story
Open any card and the full dossier is there: the approved plan, the subtasks, a chat with the agents working it, the timeline of every handoff and check, and the docs pages it changed. The board tells you where work stands; the card tells you everything else.
- Detail, Subtasks, Timeline, Docs, and Chat tabs on every card
- The Timeline is the execution record: stage changes, QA runs, demo videos, and PR links in order
- Edit the plan inline and the agents pick up the change
- Cards mirror issues on your Jira, Linear, or GitHub Projects board; both stay in sync
Surface 03 · WIP Tasks
Every task in flight, side by side
The live view of everything the agents are working on right now. Multiple cards progress in parallel, and selecting one shows its whole story: your conversation with the agents interleaved with timeline events, so context never leaves the card.
- All in-flight conversations in one list, with stage and progress at a glance
- Chat and timeline interleaved: plan approvals, subtasks generated, stage changes
- Jump into any task and redirect the agent mid-flight
- Anyone on the team can open a task and pick up the thread
Surface 04 · Docs
Your project's living memory
Specs, architecture notes, and decisions. Written and updated by the agents as cards ship. Each page knows which cards produced it and which cards reference it. And when an agent makes a change, the reasoning is captured here too, not just the result.
- Bidirectional links between cards and docs
- Reasoning capture: the why behind each change, written back to the record
- Inline edit and save; commits go to your vault repo
- Annotate-to-kick-card: turn a doc highlight into a new card in one step
Bring your own agents
The cockpit is ours. The intelligence is yours.
AI StackWorks doesn't ship its own model. Connect the agents you already run on Hermes and OpenClaw, and we'll drive them through the workflow.
Lives on your existing board
Your board stays your board.
AI StackWorks doesn't replace Jira, Linear, or GitHub Projects. It mirrors them. Cards on our board ↔ issues on yours. Status changes round-trip. Your PM's bookmark doesn't change.
- Two-way sync with Jira, Linear, GitHub Projects
- Slack notifications and approvals in the channels you already use
- Vault commits push to your git repo
Who this is for
AI StackWorks fits teams already moving fast with AI, not teams looking for their first chatbot. The sweet spot is a team that already runs a board, ships through GitHub, and uses at least one coding agent.
Best fit
- Startup CTOs and technical founders
- Eng managers who own delivery
- Agencies and fractional CTOs
- Teams already running a coding agent
Less fit
- Teams without an established workflow
- Anyone wanting a simple chatbot
- Teams with no board yet