Clarify scope first

Asks a person to fill in what the ticket leaves out before any code is written. For tickets that are deliberately high-level.

Template	scope-clarification
Works on	A git repository, cloned into an isolated Docker sandbox
Where a person acts	Clarify implementation requirements — a person fills in a form, waiting up to 30m

The workflow

Drawn from the template spec at build time. Bookkeeping nodes that only record status are left out; amber nodes are where a person acts.

flowchart TD
  n_clarify>"Clarify implementation requirements<br/><small>person: input</small>"]
  n_validate["Validate"]
  n_implement["Implement"]
  n_review["Review"]
  n_checkApproval{"Check approval?"}
  n_openPR["Open PR"]
  n_checkReviewLimit{"Check review limit?"}
  n_done(["Done"])
  n_terminateReviewFailed(["Failed<br/><small>review failed</small>"])
  n_reviewFix["Review fix"]
  n_clarify -->|"submitted"| n_validate
  n_clarify -->|"timed out"| n_validate
  n_validate --> n_implement
  n_implement --> n_review
  n_review --> n_checkApproval
  n_checkApproval -->|"yes"| n_openPR
  n_checkApproval -->|"no"| n_checkReviewLimit
  n_openPR --> n_done
  n_checkReviewLimit -->|"yes"| n_terminateReviewFailed
  n_checkReviewLimit -->|"no"| n_reviewFix
  n_reviewFix --> n_review
  class n_clarify gate

Maturity: built from the flagship steps

Ships as a built-in template and reuses the engineering steps the flagship flow runs. This particular arrangement of them is not separately exercised end to end against a real repository. See product overview §8.

Use it

Every built-in template is seeded into the workflow library and can be cloned, edited on the visual canvas, and versioned — see architecture for the node types. The spec lives in packages/shared/src/workflow/templates/scopeClarification.ts.