From 34a65d90198c257a6d04875815ed1f6197eb5596 Mon Sep 17 00:00:00 2001 From: Julian Lechner Date: Thu, 24 Sep 2026 19:11:46 +0200 Subject: [PATCH] docs(skill): clarify business review triggers --- shared/skills/reviews/business-review/SKILL.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/shared/skills/reviews/business-review/SKILL.md b/shared/skills/reviews/business-review/SKILL.md index 6ad7ef5..303ed57 100644 --- a/shared/skills/reviews/business-review/SKILL.md +++ b/shared/skills/reviews/business-review/SKILL.md @@ -1,10 +1,18 @@ --- name: business-review -description: Review a change against stated business intent and workflows. +description: Use when assessing whether a product or code change meets stated business requirements and user workflows, including actors, domain rules, acceptance criteria, and unmet cases. --- # Business Review -Check actors, workflows, domain concepts, invariants, edge cases, and acceptance criteria. +Use when reviewing whether a change supports the stated business goal and real user workflows. -Separate stated requirements, evidence, and assumptions. Do not invent business requirements. +## Review + +1. Identify the intended actors, goals, and acceptance criteria from the request or product evidence. +2. Trace the affected workflow across its relevant states, permissions, handoffs, and failure paths. +3. Check domain terms, invariants, eligibility rules, and calculations against existing behavior and authoritative product definitions. +4. Look for unmet acceptance criteria, inconsistent outcomes between related workflows, and impacts on existing users or data. +5. Separate stated requirements, observed behavior, assumptions, and recommendations. Ask about material ambiguity rather than inventing business policy. + +Report actionable gaps with the affected actor and workflow, evidence, impact, and the requirement or decision needed to resolve them. Do not substitute implementation preference for business intent.