ProductPlan & share
Planning
Plan where the code lives. Status moves itself.
Issues, cycles, initiatives and proposals in the same hub as the code. An issue links to its branch, change request and build target, verified against the repository, so the board shows what the repository shows.
Work
Cycle 14
ActiveSep 15 – Sep 28How you use it
Planning, step by step.
01Planning
An idea arrives as a proposal
Anyone files a proposal; the discussion happens on it; when it is ready it converts into issues that remember where they came from. The link picker checks branch and change request names against the live repository instead of letting anyone type one.
02Planning
Plan a cycle, and watch it burn up
Boards live inside cycles, because a board without a time box is a pile. The burn-up is drawn from the issue event log, so it reports the day work started and finished, not the day a title was edited. Pending work rolls over; the next cycle can generate itself.
03Planning
The agent’s loop: pick up, branch, link, close
An agent picks an issue up the way a person does and shows on the board as itself. Its branch links, its change request links, and when the change merges the issue completes. The task board the agent keeps for its own sub-steps is the same board.
04Planning
Roll up across projects
Initiatives live at the organization level and span projects, with updates, a timeline and the issues that feed them. They never answer anonymously, even on a public project. Press c to create an issue anywhere in Work, and Esc to close any sheet.
Coming soon: roadmaps and estimates · a command palette in Work
The full reference lives in the docs.
Works with
Open a branch and try it.
Boots in seconds. Your team joins with a link.