AI Planner

The AI Planner turns a feature description and repository context into an editable specification that can be exported or converted into a ticket.

When to use the Planner

Use the Planner when work needs clarification, trade-off decisions, and acceptance criteria before implementation.

It is appropriate for cross-cutting features, incomplete stakeholder requests, and work supported by screenshots or existing specifications. Use a ticket directly when the requirements are already complete and approved.

Planning steps

The six steps move from configuration to an approved document.

Step	Operator action	Result
Configuration	Select the workspace, model, starting branch per repository, description, and attachments.	The plan receives repository and request context.
Understanding	Review the restated request.	Scope misunderstandings can be corrected early.
Clarifications	Answer open questions.	Requirements and boundaries become explicit.
Recommendations	Select or revise proposed directions.	Trade-off decisions are recorded.
Specifications	Review the generated structured document.	Requirements, user flows, technical constraints, acceptance criteria, failure cases, out-of-scope items, and page wireframes are assembled.
Review	Edit, compare versions, undo or redo changes, and request assisted edits.	The final plan is ready for export or ticket creation.

Do not treat generated content as approved by default. Confirm repository assumptions, security requirements, deployment impact, and acceptance criteria before creating a ticket.

Auto-Answer modes

Auto-Answer can complete clarification and recommendation choices when an operator does not need to approve each answer.

Mode	Behavior
None	Requires operator answers.
MVP	Prefers the smallest viable scope.
Balanced	Balances scope and implementation cost.
Features-Rich	Prefers broader functionality.
Custom	Applies the supplied decision policy.

Use None for security-sensitive, contractual, migration, or production-operability decisions. Review all automatically selected decisions before finalizing the plan.

Plan lifecycle

The lifecycle shows whether a plan is editable or closed. A temporary session-host disconnect during initial repository setup is recovered automatically; the plan remains active unless setup reaches its final failure deadline.

Status	Meaning
Draft	Planning is in progress.
Completed	The specification is finalized.
Canceled	Planning was stopped.

Draft plans appear in My Work with progress. Updates appear automatically for connected viewers. Only one mutation can be processed for a plan at a time; wait for the current action to finish before retrying.

Repository isolation

Each plan uses an isolated working copy so repository inspection does not alter active development sessions.

Select the correct starting branch for every repository before starting. If the repository or branch is unavailable, correct workspace Git access and retry the plan action.

Attachments

Attachments provide source material for the plan.

Add screenshots, diagrams, specifications, and other relevant files during configuration. Remove secrets and unrelated customer data before upload, and verify that generated requirements accurately reflect the attachment.

Export and ticket creation

The Review step produces an operator-controlled handoff.

• Copy places the current specification on the clipboard.
• Download saves the current specification as Markdown.
• Create Ticket from Plan opens a pre-filled ticket linked to the plan.

Before creating the ticket, confirm the title, target workspace, branches, implementation workflow, assignees, and approval requirements. See Ticket configuration.

Permissions

Permissions control plan creation and access to other users' plans.

Permission	Capability
planner.create	Start a plan.
planner.view_all	View plans created by other users.
planner.manage	Manage plans beyond normal ownership limits.

Workspace membership and repository access still apply.

Troubleshooting

These checks address common planning failures.

Symptom	Check
Plan cannot start	Confirm workspace membership, model availability, host availability, repository credentials, and selected branches.
Step appears stuck	Wait for the active action, refresh once, and review the visible failure message before retrying.
Answers are not reflected	Return to the affected step, confirm the answer, and regenerate the specification.
Assisted edit is unsuitable	Undo to the previous version, narrow the instruction, and review the resulting comparison.
Ticket creation is unavailable	Complete the plan and confirm ticket permissions in the target workspace.
Attachment context is wrong	Remove the attachment, upload the intended file, and regenerate the affected content.