requirements-grilling-and-alignment

name	requirements-grilling-and-alignment
description	Use when requirements are ambiguous, underspecified, internally inconsistent, too broad, or based on assumptions. Runs one-question-at-a-time alignment, decision-tree clarification, doc-backed grilling, scope narrowing, and APIVR evidence classification before implementation.
activation	Activate when the description trigger applies to the current task.
required_inputs	Task request, relevant repository context, constraints, and authority dependencies.
required_outputs	Skill-specific artifact, verification evidence, canonical verdict, and next action.
authority_dependencies	00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md.
evidence_requirements	Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim.

Requirements Grilling And Alignment

For a new product, feature, workflow, or behavior where the user has not yet approved a design, load skills/brainstorming/SKILL.md first. This skill then handles the requirement-specific questions and acceptance evidence.

Use this skill during APIVR Phase 1 when the request needs sharper requirements before a plan can be trusted.

Ask one decision-making question at a time. Do not ask a survey of questions unless the user explicitly requests a questionnaire.

Protocol

1. Restate the request in one sentence.
2. Identify the single most consequential unknown.
3. Ask or resolve that unknown using available docs.
4. Repeat until scope, non-goals, acceptance criteria, and evidence are clear enough for APIVR tier.
5. Convert answers into a zero-placeholder plan or mark BLOCKED.

Decision Flow

flowchart TD
  A["Ambiguous request"] --> B["Restate objective"]
  B --> C["Find highest-impact unknown"]
  C --> D{"Can docs answer it?"}
  D -- "Yes" --> E["Cite doc and classify evidence"]
  D -- "No" --> F["Ask one question"]
  E --> G{"Enough to plan?"}
  F --> G
  G -- "No" --> C
  G -- "Yes" --> H["Route to writing-plans"]

Worked Example

Scenario: "Add notifications."

• Highest-impact unknown: what event should notify whom.
• One question: "Which single event should trigger the first notification, and who must receive it?"
• Result: password reset failure alerts go to admins.
• APIVR plan now has exact event, recipient, channel, evidence, and non-goals.