Planner
Planner adds tickets to Prompt Studio. Plan work on a board, hand tickets to coding agents, and review what they deliver.
Install
Planner is not installed by default. Open Settings → Project → Extensions, find Project Planner under Available, and select Install. You can also run this inside a project folder:
pst extensions add pstdio-planner
Agents publish implementation and independent review outcomes to the ticket’s core Activity feed. New managed attempts do not require Reports. Keep the Reports compatibility extension only while reading or migrating historical evidence.
Ticket navigation groups linked resources by their owning resource type, including Workspaces, Sessions, Pull requests, Notes, and Reports. Type groups keep their contents visible while additional links load in bounded pages. Attached ticket files show their content without ticket Activity or Needs attention controls; returning to the ticket restores those controls.
What Planner adds
- A Project Timeline for milestones, tracks, dependencies, and review gates. See Timeline.
- Auto Build to let a supervisor assign valid project tickets using your prompt and eligibility filters. See Auto Build.
- A Tickets board in the project sidebar, and a page for each ticket. See Dashboard.
- Statuses and tags for each project. See Tags and statuses.
- Managed attempts: an agent works on a ticket in its own Git worktree, keeps the ticket status current, and reuses that workspace for corrections. An extra review is optional. See Attempts.
- Needs attention: the place for ticket actions that need a person. It currently contains review requests for tasks and decisions. See Needs attention.
- The
pst pstdio.planner,pst pstdio.planner ticket-status, andpst pstdio.planner ticket-tagcommands. See CLI. - Skills that teach agents to work with tickets:
create-ticket,create-proposal,create-sub-tickets,refine-ticket, andimplement-ticket. - Cleanup board in the Tickets breadcrumb dropdown starts an agent session to reconcile stale statuses and blocked reasons across unfinished tickets. Its editable
cleanup-boardprompt requires evidence for changes and leaves tickets with ongoing or unverifiable sessions untouched. It reviews the whole project, regardless of view filters. - Ticket, prompt, and document templates. Edit them in Settings → Project → Templates.
Use Open tickets in the dashboard command palette to open the current project’s Tickets board.
Ticket numbers
Core assigns ticket numbers. Planner reads the current number from core instead of storing its own copy. After devices reconnect, core repairs duplicate numbers and keeps old numbers as aliases. An old number that matches one ticket still opens that ticket. A shared alias shows every matching ticket in search and opens every match from a file link; pst pstdio.planner get-ticket --id <number> returns all matches. Use the stable ticket ID when changing a ticket through a shared alias.
Local ticket folders follow the current number. Planner preserves unsaved text and attached files when it moves an owned checkout after a renumber. Workspace links use ticket IDs, so an old branch number does not attach the workspace to a different ticket.
Refinement options
Open Settings → Project Planner → Workflow & automation. Update canvas designs for UI changes is enabled by default. It applies to tickets that add or change UI, including changes to existing features.
The ticket skills read the project option with pst pstdio.planner refinement-policy. The result contains updateCanvasDesign. When enabled, the agent follows the project’s canvas skill and updates the live design before completing the ticket or changing production UI. The ticket links the canvas page, exact preview names, source paths, and a short walkthrough. This replaces the artifact prototype requirement. If the option is off, the agent records why it skipped the design step. If Canvas is unavailable, the agent uses the project’s existing design workflow and records why no canvas was linked. Tickets without UI changes do not require one.
Install the optional Artifacts extension from Extensions to use prototypes. Its package name is artifacts. Refinement does not install it automatically. Shared ticket workflow options belong to Planner alongside its refinement and implementation skills.
Implementation options
Open Settings → Project Planner → Workflow & automation, to configure the implement-ticket workflow:
- Adversarial review runs a review automatically before the final commit and handoff.
- Open PR opens a draft pull request after validation and links it to the ticket.
- Default target branch selects a remote branch from the project’s Git folder. Clear the selection to use the repository’s default branch.
- Maximum in-progress tickets limits how many tickets run an implementation at once. Run attempt does not start another ticket at this limit, whether automation or a person runs it.
Choose Auto Build in Project Timeline to open its modal. Enter a prompt, choose the supervisor harness, model and run options, set Eligible tickets, and confirm with Auto Build. All options stay in the same modal. The information icon next to the title explains how it works. A supervisor uses your prompt to assign valid, unassigned tickets as dependencies and capacity allow. Completed tickets are excluded using your workflow settings. Each implementation uses the default agent and target branch.
The supervisor ends its turn between checks and resumes when more work can run. The mode keeps running when the timeline is closed and resumes its checks after restarting Prompt Studio. Click the active Auto Build button to open its activity popover. Review requests appear above sessions, and the footer stays visible while the activity list scrolls. Pause suspends new dispatches and wake-ups while current agents continue. Resume continues the same supervisor and scope. While paused, Stop Auto Build cancels all linked sessions, including queued follow-ups. The selected view, filters, and search only affect the display. A supervisor wake-up failure pauses the run and shows the error. Resolve it before resuming.
Auto build leaves gates, blocked work, open review requests, and existing attempts for review. Agents that get stuck use Planner’s Request review action so the timeline shows Needs attention.
The options apply only to the current project. Adversarial review and Open PR are on by default. Projects without a local Git folder can still set the review and pull request options. Turning off Adversarial review does not change the optional managed reviews described in Attempts.
The skill reads these options with pst pstdio.planner implementation-policy and follows them without asking. Instructions you give for a specific task take precedence.
Ticket tags have their own panel in Settings → Project.
From a terminal, list the branch choices with pst pstdio.planner implementation-targets. Set one with pst pstdio.planner set-implementation-target --branch origin/main. Leave out --branch to clear it.
Manual ticket order
Planner uses public core order positions for moves and new tickets. Offline moves merge into the same order on each device, with each stable ticket once. Filtered rows retain their global place; archived tickets do not enter active board moves.
Storage migration 4 imports numeric order by rank and stable ticket ID with
migration.position, preserving IDs and content. It keeps old ranks until every
position is saved, then removes them. An interrupted import can resume. New moves
use storage.positions.between; Planner no longer computes numeric midpoints or
rebalances neighbours.
A legacy card can arrive from an offline device after the shared migration has finished. Planner inserts such arrivals after the current order using core positions, without resetting existing manual moves. Ordinary content edits keep the freshly stored position; only explicit order actions replace it.
Metadata updates use the public observed-read and conditional-update API from PS-1073. If a remote edit wins, Planner reads the new value and recomputes only the intended metadata. A matching published host and SDK are required; a development SDK link does not satisfy the production delivery gate.
Offline tag edits
Ticket commands keep flat tagIds. The data layer projects single choices and
multi-select lists from private per-tag selections. Each multi-select option has
its own stored membership value, so adding a flag offline preserves another
device’s different addition. Clearing a list removes observed choices while
retaining additions made concurrently. Ordinary storage arrays remain whole values.
Existing tags values remain migration input when selections are first edited.
A single/multi conversion preserves a concurrent choice as an editable list;
a later explicit selection resolves it. Storage also fences each observed record
lifetime, so an offline edit cannot change a deleted-and-recreated ticket.
Updated at: 2026-11-07