kodus-business-rules-validation

# Kodus Business Rules Validation ## Goal Run Kodus business-rules validation from the current repository diff only. ## Required Inputs - One local diff scope: - default working tree diff - or `--staged` - or `--branch <name>` - or `--commit <sha>` - or `[files...]` - Optional task reference: - `--task-url <url>` or `--task-id <id>` - Do not pass both. ## When to Use - The user asks for business-validation, business validation, business rules validation, or acceptance-criteria validation - The user wants to check local implementation vs task requirements - The user mentions local business validation or `kodus pr business-validation` Do not use this skill as a substitute for `kodus review`. Local review and business-rules validation are different flows. ## Workflow 1. Choose the local scope. - Default working tree diff when no scope flag is provided. - Use only one of `--staged`, `--branch`, `--commit`, or `[files...]`. 2. Build and run the command. Examples: ```bash kodus pr business-validation kodus pr business-validation --staged --task-id KC-1441 kodus pr business-validation --branch main --task-id KC-1441 kodus pr business-validation --commit HEAD~1 --task-id KC-1441 kodus pr business-validation src/service.ts src/use-case.ts --task-id KC-1441 ``` 3. Interpret the result. - `Mode: local diff` means validation over the provided local diff scope. - If output says missing MCP/task context, report that directly and request integration/context setup. ## Notes - `kodus review` does not trigger this flow. - Prefer `--task-id` or `--task-url` when the task is not obvious from local context. - `KC-1441`-style keys are valid.