Skip to main content

User Guide

Purpose: The standing reference the team consults during and after onboarding — how to journey work through Swifter, how to deliver well, and how to operate the interface.

The Cookbook is the part of this blueprint that an engagement team keeps open on a second monitor while they are actually running a project. Setup gets the workspace standing; the Cookbook is what carries delivery week after week. It is divided into three guides because three different questions come up during real work, and conflating them is one of the consistent ways teams get stuck. What is the canonical path for this kind of work? — Journeys. How should I compose a work item, sequence agents, and decide when to split? — Delivery. Where do I click, what do those tabs mean, what is Preview actually showing me? — Interface.

The three guides interlock by reference, not by repetition. The Journeys Guide is the entry point — it shows the canonical happy paths end-to-end and the recovery moves when those paths derail. It is deliberately narrative, because the most common onboarding question is "what should I do, in order, to ship a screen?" and a checklist answers that better than a method essay. When a journey calls for deeper context — why is integration a separate work item?, what makes a good page WI?, what does the autonomous-triage agent actually route to? — it cross-references the Delivery Guide. When a journey calls for a specific UI move — how to open Preview, what the Dev tab shows, how to read a session header — it cross-references the Interface Guide.

The Delivery Guide is the method reference. It documents the five universal principles for AI-agent work items, the work-item templates by type, the canonical run sequences per type, the agent catalogue, and the project-level patterns that determine whether a backlog converts cleanly or churns. New BAs read it cover-to-cover during onboarding; experienced ones return to specific sections when authoring a new kind of WI for the first time on the engagement. The Interface Guide is the operating manual — projects, work items, sessions, chat, App/Dev/Test tabs, Preview, pull-request actions — covered with enough screenshots and field-by-field detail that a new joiner can navigate the tool unaided by their second day.

Pages in this section​

  • Journeys Guide — end-to-end happy paths for frontend, integration, and a troubleshooting catalogue.
  • Delivery Guide — the agentic SDLC, guidelines, design system, work-item composition and run sequences.
  • Interface Guide — operating Swifter as a tool: projects, work items, agents, previews, pull requests.

How to read the Cookbook​

If you have just finished Setup, start with the Journeys Guide — run a real Frontend Screen Happy Path on a small WI before reading anything else. Once a screen is on main, read the Delivery Guide end-to-end; it will retroactively explain why the journey worked. Keep the Interface Guide bookmarked for ad-hoc lookups. For team leads, the recommended onboarding loop is: one engineer ships a journey, the lead reviews against the Delivery Guide's WI quality rubric, and the team revisits any troubleshooting pattern that came up.