What problem does it solve? Teams often start building client deliverables without confirming requirements, leading to costly rework when assumptions about the client's domain, scope, or priorities turn out wrong. This Skill enforces a mandatory alignment phase that interrogates the user before any implementation begins. ## Core Features & Use Cases - Paradigm Identification: Classifies the client's core need into CMS-driven, SaaS-functional, or process-orchestration paradigms to avoid forcing the wrong solution architecture. - Historical Context Lookup: Searches past task runs and architecture decision records (ADRs) via a combined_search MCP tool so prior lessons and decisions are applied instead of repeated mistakes. - Relentless One-at-a-Time Questioning: Walks through scope, constraints, success criteria, hidden assumptions, and edge cases one question at a time, then writes an alignment summary requiring explicit user approval before work starts. - Use Case: Before writing the first commit of a new client project, run this Skill to read the client requirements document, confirm the contingency profile, grill the stakeholder on scope and acceptance criteria, and produce a signed-off alignment summary. ## Quick Start Ask the AI to grill you on the requirements for the new client project before writing any code.
