Skip to main content
Use this guide when a feature is big enough that you want to agree on what to build before any code changes. Agents write the brief, the user flows, the technical plan, and the tickets as artifacts in the Task. You review and comment on them, the agents revise them, and the approved tickets drive the build. For a small, obvious change, skip the planning and prompt an agent directly.

​
Before You Start

  • A Task with your repository added as a workspace folder, so agents can read the code. See Quickstart.
  • A coding agent that can run skills, such as Claude Code or Codex.
  • If someone shared the Task with you, the Editor or Owner role is required to edit artifacts. Anyone with access can comment.

​
Plan the Feature

1

Frame the feature

In the composer, type $ or /, pick traycer-epic-brief, and describe the feature. The agent asks about anything unclear and writes a short brief once you agree on the framing.
2

Map the flows and the technical plan

Run $traycer-core-flows to settle what users do and see, then $traycer-tech-plan to work through the architecture. Answer the agent’s questions as they come; see Agent questions. Before it drafts the tech plan, the agent tells you what is still open and waits for you to confirm.
3

Read the artifacts

Open each one from the Artifacts panel. A bar beside a row marks an artifact that changed since you last opened it. You can edit the text directly; edits save as you type. See Editing artifacts.
4

Comment where you disagree

Select a passage, click Comment (⌘⌥M / Ctrl+Alt+M), write your note, and press ⌘Enter / Ctrl+Enter. The threads collect in the Comments panel. See Comments.
5

Have the agent address your comments

Ask for it in the chat:
The agent updates the artifact and resolves the threads it handled. The Open tab of the Comments panel shows what is left.
6

Pressure-test the plan (optional)

Run $traycer-artifact-critique on the plan. It writes a review artifact with gaps, contradictions, and risks. Comment on it, or ask the agent to fold the findings into the plan.
7

Break the plan into tickets

Run $traycer-ticket-breakdown. The agent writes one ticket per piece of work, with its dependencies, under a tickets folder, and revises the set until you approve it.
8

Build from the tickets

Run $traycer-execute. It orders the tickets into batches by dependency and starts a child agent for each ticket; the children appear under it in the Agents panel. It reviews each batch against the plan, marks the tickets that pass Done, and stops to ask you when the work drifts from the product plan. To follow progress, open Filter artifacts in the Artifacts panel and set Type to Ticket.
If an edit to an artifact goes wrong, click Version history (the clock button) in the artifact’s tile, select an earlier version, and click Restore this version. See Version history and recovery.