Analyze Business Requirements

Use this skill when business needs, bug behavior, or process expectations must be turned into clear, testable, implementation-ready requirements.

When to Use

• a feature, workflow, or policy change needs structured requirements
• making actors, business rules, and state transitions explicit
• defining testable behavioral acceptance criteria (BDD / Gherkin)
• capturing preserved behavior versus changed behavior
• specifying probabilistic acceptance criteria and HITL escalation triggers for AI/LLM features
• defining autonomy boundaries, MCP tool permissions, and kill-switches for agentic systems
• preparing structured machine handoffs via contracts/schemas/feature-ticket.json

Core Rules