Skip to main content

/handoff

Execute the Product β†’ R&D handoff for a PRD β€” stage 3 of the Product ↔ R&D Handoff pipeline. The guiding invariant: for the downstream agent, the contract is code and tokens β€” not pixels. This command exists so the handoff is perfect at the PRD level β€” a PRD that a downstream AI can turn into a Design Doc with zero ambiguity and zero screenshots.

Steps​

  1. Resolve the PRD. Default to the PRD for the current feature/branch (docs/prds/<slug>-<cu-id>.md); accept an explicit path or CU-id otherwise.
  2. Run gatekeeper Mode A β€” the independent Definition-of-Ready check against the PRD template. It blocks on any P0 gap.
  3. AI-consumability check (the perfection bar β€” verify each, name any miss):
    • Β§7.2 UI Composition names components from COMPONENTS.md (catalog ships with design-system PR #326; until then Storybook), never invented ones. A needed-but-missing component is flagged as a separate /add-component request, not hand-rolled.
    • Color/spacing intent references tokens (e.g. semantic.success), never raw hex.
    • Β§7.4 Copy is provided as text, not baked into an image.
    • A design reference is linked and is code, not pixels: a Figma frame reachable via Dev Mode MCP + Code Connect (Path A), or a Claude Design code branch (Path B). It must also be machine-readable by the AI β€” a client-rendered link the AI can't fully read (e.g. a claude.ai/public/artifacts/… page WebFetch truncates) is present but not consumable; ask for a readable form (pasted text / committed markdown / Dev-Mode Figma) before flipping. A human may override after confirming a readable copy exists.
    • Acceptance Criteria are testable; the boundary holds (WHAT/WHY only β€” no HOW leaking into the PRD).
  4. Flip status draft β†’ ready-for-rd only when steps 2–3 pass. Update the PRD frontmatter and confirm the clickup_parent linkage.
  5. Open the CTO-review ticket β€” invoke /cto-review: open a ticket in the dedicated ClickUp "CTO Review" list, titled [Feature name] informative title, tagged cto review, carrying the full handoff package (problem/outcome, UI composition, design reference, acceptance criteria, links). This is the end-of-product-flow checkpoint so the CTO sees every feature before R&D commits.
  6. Hand to R&D β€” offer to run /plan-feature to draft the Design Doc from the now-ready PRD. The UI-design half of the handoff is then validated by /design-review.

Boundaries​

  • Blocks, does not paper over. If the design reference is a screenshot, or Β§7.2 invents a component, the handoff is not ready β€” say so and route back to Product/Designer. Never flip to ready-for-rd with a placeholder.
  • This is the PRD-level half of the handoff. The UI-design-level half is /design-review.