Alignment Interview
Reach decision readiness before implementation starts.
Workflow
- Inspect the evidence already available in the request, repository, issue, plan, and named documents before asking the user to repeat facts.
- Maintain the current understanding as
Goal, Users, Constraints, Known evidence, Unknowns, and Success criteria; present only the material change during the interview.
- Rank unknowns by how much their answers could change scope, architecture, authority, safety, cost, or acceptance.
- Ask one material question at a time. Explain why it matters and recommend a default when current evidence supports one.
- Update the shared model after each answer and identify contradictions rather than smoothing them over.
- Stop when the remaining unknowns do not prevent a responsible next decision. Summarize the agreed model, assumptions, rejected options, unresolved questions, and next authorized action.
Boundaries
- Do not implement, edit files, publish, or create external records while interviewing unless separately authorized.
- Do not ask the user to repeat facts that can be discovered safely from the authorized workspace.
- Do not treat persistence or question count as quality. Stop when the decision is ready.
- Route broad product discovery to problem framing and concrete implementation design to implementation planning.
Output
During the interview, present the current material question and only the changed
understanding needed to answer it. Do not reopen settled decisions unless new
evidence creates a material conflict. At readiness, summarize the full agreed
understanding, evidence, decisions, assumptions, open questions, readiness, and
any next authorized action.
Read the original acceptance example when checking this behavior.
Example
Synthetic example; not an observed client result.
Input: Storage is already chosen; only retention is undecided.
Output: How long must records remain available, and what deletion obligations constrain that period?
1---2name: align-on-decisions3description: "Clarifies an underspecified request when the desired result, constraints, or success criteria are unclear; asks only material questions and does not reopen settled decisions."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/align-on-decisions7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Alignment Interview1617Reach decision readiness before implementation starts.1819## Workflow20211. Inspect the evidence already available in the request, repository, issue, plan, and named documents before asking the user to repeat facts.222. Maintain the current understanding as `Goal`, `Users`, `Constraints`, `Known evidence`, `Unknowns`, and `Success criteria`; present only the material change during the interview.233. Rank unknowns by how much their answers could change scope, architecture, authority, safety, cost, or acceptance.244. Ask one material question at a time. Explain why it matters and recommend a default when current evidence supports one.255. Update the shared model after each answer and identify contradictions rather than smoothing them over.266. Stop when the remaining unknowns do not prevent a responsible next decision. Summarize the agreed model, assumptions, rejected options, unresolved questions, and next authorized action.2728## Boundaries2930- Do not implement, edit files, publish, or create external records while interviewing unless separately authorized.31- Do not ask the user to repeat facts that can be discovered safely from the authorized workspace.32- Do not treat persistence or question count as quality. Stop when the decision is ready.33- Route broad product discovery to problem framing and concrete implementation design to implementation planning.3435## Output3637During the interview, present the current material question and only the changed38understanding needed to answer it. Do not reopen settled decisions unless new39evidence creates a material conflict. At readiness, summarize the full agreed40understanding, evidence, decisions, assumptions, open questions, readiness, and41any next authorized action.4243Read [the original acceptance example](references/continuity-example.md) when checking this behavior.4445## Example4647Synthetic example; not an observed client result.4849Input: Storage is already chosen; only retention is undecided.5051Output: How long must records remain available, and what deletion obligations constrain that period?