Specs & Requirements
A spec is where the thinking happens — a real document your team writes together. Break it into requirements, turn each into a task, and the plan and the work stay tied together from the first line.
A real document
A spec is a full rich document, not a text box. Several people edit it at once and the changes merge as they type. Nest a spec under a parent to break a big piece of work into smaller specs, each with its own status — and the parent rolls up how many of its children are done.
From plan to work
Break a spec into requirements — each its own document — and turn each one into a task that carries it out. A spec can generate those tasks for you and remember which ones it made, so you can trace a shipped change back to the requirement that asked for it.
People or agents
Specs and tasks aren't only for people. The Bosca CLI runs an MCP server, so Claude and other AI agents write specs, break them into requirements, and track their tasks in the same Work Ops your team uses — the plan and the progress in one shared place.
Keep exploring