What problem does it solve? Teams often start non-trivial features without checking whether the work fits the project's stated vision, goals, and scope, leading to scope drift and wasted effort. This Skill reads the repo's PROJECT.md and issues an evidence-backed verdict — ALIGNED, NEEDS_CLARIFICATION, or OUT_OF_SCOPE — before any planning or implementation begins. ## Core Features & Use Cases - Three-axis comparison: Evaluates the proposed change against goal alignment, explicit out-of-scope items, and constraints, citing specific lines from PROJECT.md. - Deterministic verdict mapping: Maps comparison results to one of three verdicts using a fixed decision table, preventing soft or ambiguous judgments. - Structured options on conflict: When a change is OUT_OF_SCOPE, it presents three concrete options — update PROJECT.md, adjust the feature, or cancel and discuss scope — and waits for the user's decision. - Use Case: Before planning a new integration feature, run the alignment check to confirm it advances a stated goal and does not violate the documented out-of-scope list, then carry the verdict into the plan. ## Quick Start Ask the agent to check whether your proposed feature aligns with PROJECT.md before starting planning.
