planning-interview

A sprint kickoff interview captures the sprint goal, kebab-case sprint name, scope boundaries, verification steps, and known risks through a short, ordered Q&A. This produces a planning-summary file while triggering sprint initialization with the required parameters.

A Product Owner needs a recorded sprint goal, naming convention, out-of-scope items, verification pipeline, and risks before starting a new sprint. Capturing these minimum inputs during a kickoff interview provides enough clarity to write user stories without follow-up.

To reduce CI failures during project planning, define the exact build, test, lint, and typecheck workflow as verification steps. Confirming or adjusting this expected pipeline during the sprint kickoff ensures downstream execution matches the agreed verification criteria.

Yes, you can use a sprint kickoff interview to define scope boundaries without writing user stories. The interview captures the sprint goal, naming, scope, verification, and risks, then informs downstream initialization while explicitly leaving story writing and architecture proposals to other roles.

A sprint name for automated sprint initialization should be in kebab-case. Capturing this specific format during the directed kickoff interview ensures the resulting planning summary correctly triggers the downstream sprint start command with the required naming convention.

You should not use a directed interview for sprint kickoff if you need to write user stories or propose architecture. This process strictly captures minimum alignment inputs like goals, naming, scope, verification, and risks, then hands control back without generating execution-level artifacts.