Bosca / Work Ops

Bosca Work Ops

Plan and track work,
built into the platform.

Portfolios, specs, tasks, sprints, boards, and releases — all with your own workflows, in the same platform as your content and code. Your team plans and tracks here, and so do the AI agents working alongside them.

How it works

How it works

Organize, plan, track.

01

Organize

Group work into portfolios, programs, and projects, so a single task and the whole roadmap sit in the same structure.

02

Plan

Write a spec, break it into requirements, and turn each into a task — or add tasks straight to a board or a sprint.

03

Track

Move tasks through the workflows you define, on boards and in sprints, with your own statuses, priorities, and labels.

What makes it powerful

A full tracker, shaped to your team

The hierarchy, the work items, the boards, and the rules — with the statuses, workflows, and types set the way your team already works.

Four levels of structure

Portfolios hold programs, programs hold projects, projects hold tasks — organize a single team or a whole org.

Specs and requirements

Write a spec as a rich document, break it into requirements, and track each one as its own task.

Releases and milestones

Versions collect what ships in a release; milestones set dated targets that roll up across a program.

People and agents

Your team works in the editor — and through the Bosca CLI's MCP server, Claude and other agents write specs and track tasks here too.

Tasks on your terms

Task types, statuses, priorities, resolutions, and labels are yours to define and compose into your project workflows.

Workflows you define

Give each task type its own set of statuses and the moves allowed between them.

Boards and sprints

Run the work on kanban or scrum boards, in sprints with a start, an end, and a goal.

Automation

When a task is created, transitioned, or an SLA is at risk, run a rule that edits, transitions, comments, or opens a task.

How work gets done

Your agents plan and track right here

The Bosca CLI runs an MCP server, so Claude and other AI agents work in the same Work Ops your team does. An agent writes the spec, breaks it into requirements, opens the tasks, and moves them along as it goes — the plan it makes and the work it does, in one shared place.

  • The Bosca CLI exposes Work Ops to AI agents as MCP tools.
  • An agent writes a spec, its requirements, and the tasks that carry it out.
  • It keeps its own statuses current on the same board your team watches.
  • What an agent plans and does sits right beside your team's work.
agent · bosca mcp
workops_speccreate · "Live sessions dashboard"
workops_requirementcreate · 4 requirements
workops_taskcreate · BOS-142 … BOS-145
workops_tasktransition · BOS-142 → Done
spec, requirements, and tasks — tracked on your board

Part of the platform

Linked to your content and your code

Because Work Ops is part of Bosca, a task isn't off in a separate tool. It links to the document it's about, the spec it came from, and the commits that reference it — all in one place.

  • A task can link to the content document it concerns.
  • A spec can point at the repository and path where its work lives.
  • Commits and pull requests that name a task's key link back to it.
  • Tasks link to each other — blocks, duplicates, relates to, and more.
BOS-142 · links
document · Live map design
spec · DASH-2
commit · a1b0c7 references BOS-142
blocks · BOS-149

The plan and the work, in one place

Portfolios down to subtasks, specs down to sprints, all with your own workflows — next to the content and code your team is actually shipping.