Skip to main content

/cto-review

Open a CTO-review ticket for a feature. Thin entry point over the cto-review skill.

Usage​

  • /cto-review — use the current feature/branch's PRD (docs/prds/<slug>-<cu-id>.md).
  • /cto-review <prd-path | cu-id> — a specific PRD.
  • /cto-review on an ad-hoc task (no PRD) — describe the task; the skill gathers what exists and marks missing handoff fields explicitly.

What happens​

Run the cto-review skill: it resolves the "CTO Review" ClickUp list by name, builds the title [Feature name] informative title, assembles the handoff package (problem/outcome, scope, UI composition from COMPONENTS.md — or Storybook + src/components until design-system PR #326 merges — acceptance criteria, design reference, links), creates the task tagged cto review, links it to the PRD's clickup_parent, and returns the ticket URL.

When it fires automatically​

At the end of the PRD-level handoff: once /handoff flips a PRD to ready-for-rd, it invokes this so the CTO-review ticket opens without a manual step. Use /cto-review directly only for tasks that did not come through /handoff.

Boundaries​

  • Opens the ticket; does not approve, move, or close it.
  • Never fabricates handoff fields or hardcodes the list ID (see the skill's boundaries).