Plans, specs and issues, ready before anyone writes code.
Turn goals into plans with dependencies and owners, write specs from your architecture docs, and file approved work in Linear. Your engineers stay on the code.
A goal becomes a map of work, with owners.
The planner lays out what depends on what. You approve the issues before they reach Linear.
3 roles, ready to adjust.
Ask Chat for the team and it proposes these roles, each with a job description, instructions, skills and a model. Rename them, change who reports to whom, or add people.
Breaks goals into plans, assigns owners and reviews every spec before it reaches you.
Writes specs, RFCs and docs, and answers questions from your architecture docs with sources.
Maps dependencies, estimates and order of work, and keeps Linear in sync after approval.
The work, and what’s ready today.
Everything below is available now.
Goals turned into plans with dependencies and owners
Describe the goal. The team proposes the steps, what blocks what, who owns each part and what it will cost to plan.
Specs and technical docs, with sources
Specs and RFCs drafted from your architecture docs. Ask a question and get an answer with the exact source.
Approved work filed as Linear issues
After you approve the exact list, issues are created in Linear with owners, estimates and links to the spec. If the list changes, it waits for you again.
Weekly status reports on a schedule
Every Friday: what shipped, what slipped and what’s next, from Linear and your team’s work.
Same office rules as every other team.
Issues are created only after you approve that list. Change it and it waits again.
Each employee reads only the docs and Linear teams you give it access to.
A spec counts as done when its checks pass and the manager accepts it.
Add an engineering team to your office.
Start on the free plan, no card. Same approvals and budgets as every other team.