From Intent to Work Packages
An intent is broken down on its own page: a brief that says what is wrong or possible and how the team would go about it, workstreams generated against that brief, and one Work Package per deliverable scope under each workstream — each package a real record from the moment it is accepted, filled in with work items on its own page and gated by its Definition of Ready and Done.
The brief
Every breakdown starts from two short pieces of prose on the intent page: the Problem / Opportunity (what is wrong or possible, for whom, and why it matters) and the Approach (how the team would go about it, and what it would deliberately leave out). Write them yourself or click Draft with AI — the Architect fills whichever field is empty and never overwrites what you wrote. Workstreams and work packages are generated against the brief, so a thin brief produces a thin breakdown.
Pages: the intent's reference material
At the foot of the intent's page, Pages hold what the team knows about the intent — context, constraints, decisions, a glossary — as grouped markdown pages bound like a book — a tab for each group down the left, the open page on the right with page turns — the same way the Product Manual and a Work Package Plan are laid out. Write a page yourself, or type a topic and press Draft to have the Intent Architect propose one. A proposed page is not used until someone applies it (a Semi-Autonomous or Fully Autonomous studio applies them on arrival). Applied pages are given to every agent that shapes or reviews a work package under the intent, and each package lists them under From the intent. When an intent is closed its pages are kept exactly as they were.
Value and scheduling
Alongside the brief the studio owner or a reviewer sets the intent's priority, due date and value. Value is defined once for the studio on the Value Model page: the value types (by default revenue increase, cost saving, risk reduction, customer satisfaction, time saved, complexity reduction and scale of benefit), how much each counts, and what each point of the 0–5 scale means. The owner adds a type in a dialog, where the Value Analyst can draft what it measures and all six levels for them to edit. The intent is rated on those types only, each choice showing what the point means, so every intent is valued on the same terms. A value score out of 100 is the weighted average of the rated types, and the Intent Pad groups and sorts on it. These are product decisions, so the server refuses them from anyone else.
Release phases and reference numbers
An intent can be released in phases — MVP, Phase 2 and so on — and each work package is placed in one. Phases are set by the owner or a reviewer; a phase that still has packages cannot be removed. Generate release phases, in the same section, asks the Delivery Planner to propose the phases from the intent’s workstreams and the work packages in them, and puts each package that is in no phase into one. A package you have already placed stays where it is, a package is never placed before one it is implemented after, and you can move any of them afterwards. Every intent, workstream and work package also carries a reference number (INT-12, WS-31, WP-45) that the server assigns and never reuses.
The Workstream Explorer
The Explorer opens on the Work View: each workstream is a banner across the page with its work packages beneath as cards, a dashed card for the next package to define, and — when the intent has release phases — a vertical swimlane per phase. The Tree view shows the same breakdown as workstreams → work packages → work items. You accept, edit or remove every artefact — nothing proceeds unaccepted:
Related work and implementation order
A work package can name the packages that must be implemented before it — set under Implement after when you create it, on its Related work card later, or by accepting a suggested order on the Map. Packages in other intents can be named too. The server refuses an order that loops. The package page shows what it builds on and what waits on it, and draws the whole chain: every package before and after it across the studio, one lane per intent, with its intent’s own place among the other intents above; if a prerequisite is not implemented yet, a banner says so and Dispatch asks you to confirm. The order is advice for the team, not a gate: it never stops a package being approved, and changing it never invalidates a readiness review.
Reading the drawing. Steps run left to right, so everything to the left of a package comes before it. The package you are on is marked 📍 This package. Every card says in words whether it is implemented, can start or is waiting, and is a link to that package. An arrow runs from a package to each one that builds on it; arrows are routed round the cards and each meets a card at its own point, so follow a line from one card’s right edge to the next card’s left. Show this order as a numbered list gives the same order in words.
Filling a Work Package
Open a package to see its scope — the intent and workstream it sits under, its acceptance criteria and risks — and its work items. Generate them from the scope with the Composer, add one by hand, edit or remove unaccepted ones, and accept them one at a time or all at once. Accepted items are frozen until un-accepted, which asks for a reason. The package snapshots the vision statement, accepted outcomes and intent description so agents receive the full upstream story, and carries the studio's Definition of Ready and Done for its intent kind.
One page, or tabs
A work package reads top to bottom in seven numbered parts: Scope, Plan, the Definition of Ready, Coding, Iterate, the Definition of Done, then the Passport. Choose Show as tabs to see one part at a time; on a phone the page opens that way. Each tab says where its part stands — complete, in progress, needs attention or failed — with an icon and a word, and the page opens on the part the package is at. Your choice is remembered in this browser for every package; Show as one page puts it back.
Reviewing and approving
Review every acceptance criterion — AI may omit edge cases that require domain knowledge. The package must pass its readiness gate and be approved by a named human (recorded with notes and timestamp) before it can be dispatched. Changing the scope or the work items after the gate has been reviewed invalidates the evidence gathered against the old version — see Work Packages & the Readiness Gate.
Auto Pilot
In a Semi-Autonomous studio, Take it from here on the intent page runs the whole flow — brief, workstreams, one package per scope, the implementation order and phases, then work items on each package — without moving you off the page you are on: the panel says where it is working and links you there. It asks the Delivery Sequencer for the implementation order of the packages it created, and adds those links only to its own packages. The run ends there, with every package left as a draft: which of them go for review, and on to the readiness gate, is yours to decide on each package. Auto Pilot this workstream and Auto Pilot this package do one part. Nothing is dispatched. The run goes on the server, so it carries on with the tab closed and several intents can run at once; Auto Pilot & Accept All says what it may cost and how a run is stopped or resumed.