Specifikáció és elfogadás tisztázása

Specification & Acceptance Review

Use this skill when authoring or reviewing product specifications, task briefs, and implementation plans so requirements are complete, internally consistent, and verifiable before or during coding.

Workflow

1. Verify problem clarity, scope boundaries, and user outcome (Marty Cagan & Gerald Weinberg):
   • Confirm the specification clearly states:
     • Target outcome: Which user or system actor needs this, and what concrete problem it solves.
     • In-scope vs. non-goals: Explicit boundaries so implementation neither omits required flows nor drifts into unrequested work.
     • Stakeholder impact: Who is affected when behavior changes, and what happens to existing users, data, or integrations.
2. Audit business rules for completeness and internal consistency:
   • Check every rule against edge conditions and competing rules:
     • Preconditions & eligibility: What state must hold before an action is allowed?
     • Conflict resolution: If Rule A and Rule B both apply (e.g., a discount cap vs. a minimum fee, or an admin override vs. a locked state), which rule wins?
     • Failure, cancellation & retry: What happens when a multi-step flow is interrupted, rejected, or submitted twice?
     • Empty, boundary & scale cases: Zero items, single item, maximum quota reached, expired records, or concurrent edits.
3. Ensure every acceptance criterion is falsifiable and testable:
   • Replace vague adjectives ("intuitive", "fast", "secure", "handles errors gracefully") with observable, deterministic conditions ("returns 409 Conflict when version mismatches and preserves unsaved form input").
4. Distinguish product decisions from implementation details:
   • When requirements conflict or leave a business-critical behavior undefined, formulate a concise decision question with the concrete options and their consequences rather than guessing silently.
   • Respect settled product and architectural trade-offs unless new evidence invalidates them.