wayformFAQGet early access What are shared plans?
A shared plan is an engineering plan that lives with your team instead of in one person’s chat. In Wayform, a plan is a numbered, versioned document that any teammate, or any teammate’s agent, can read, revise, build, and check work against. It starts from the decisions your team has already made, and when it ships, the decisions it produced join shared memory.
Plan mode in a coding agent writes a good plan, then the plan disappears when the session ends. Markdown plan files in a repo drift as soon as the work changes.
How it works in Wayform
- Brief before writing. Your agent calls
plan_briefwith the task. Wayform returns the decisions and constraints that bind it, plus related plans already in flight. - Save a living plan. The agent writes the plan from that brief and the repo, then saves it as plan
#N: goal, constraints, approach, checklist, and open questions. Every edit is a new version. - Move it through a lifecycle. Draft → active → building → shipped, or superseded by a newer plan. Conflicting edits are detected, not silently overwritten.
- Build and check. Build in the app or from your terminal. Before the pull request,
plan_checkgrades the diff against the plan’s checklist and inherited decisions. - Ship into memory. A linked PR merging with its checklist done ships the plan and records its decisions for the next one.
An example
Plan #12, “Team invitations”, inherits the decision to reuse GitHub identity. Chris builds it with Claude Code. The PR description carries a conformance table that shows each requirement met. When it merges, “invitations use GitHub identity because team access should extend the existing flow” becomes a decision that plan #13 starts from.
What shared plans are not
- Not a ticket tracker. Plans describe how the work will be done and why; keep your issue tracker for what and when.
- Not a guarantee of correctness. Plan check is an agent’s assessment with evidence to inspect. It doesn’t replace tests or review.
When you don’t need them
For a one-line fix, skip the plan. Shared plans earn their keep on work that spans sessions, people, or agents.
Go further
- Working with plans: lifecycle, plan check, and linked PRs.
- Agent orchestration: build plans from the app.
- Wayform vs Spec Kit and Kiro.
Questions
How is a shared plan different from plan mode?
Plan mode’s plan ends with the session. A Wayform plan is numbered and versioned, briefed by the team’s decisions, and readable by every teammate’s agent until it ships.
Which agents can use Wayform plans?
Claude Code, Cursor, and Codex can plan and build, in the app or from your terminal. Devin CLI, Antigravity, and other MCP clients can read and write plans through MCP.
When does a plan ship?
When its linked pull request merges with the plan’s checklist done. If items are still open, the plan stays in building.
Is a shared plan a ticket?
No. A plan describes how the work will be done and why. Keep your issue tracker for what gets done and when.