business-rules

Generate a business rules catalog documenting logic, constraints, and decision criteria for requirements.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill business-rules-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-rules
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/requirements/business-rules
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill business-rules-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business logic often lives in stakeholder heads or scattered notes, causing AI development agents to invent rules during implementation. This Skill produces a signed, traceable business rules catalog that pins down every constraint, calculation, and decision criterion before construction begins. ## Core Features & Use Cases - Structured Rule Catalog: Generates a business-rules.md document with per-domain rule sections, each rule carrying an ID, category, condition, testable logic, examples, and exceptions. - Required Coverage Checks: Ensures validation, authorization, calculation, lifecycle, temporal, and compliance rule categories are populated or explicitly marked N/A. - Traceability & Gating: Every rule must trace to a functional requirement (FR-XXX), and the document is blocked from signature until nine validation rules pass, with BSA as approval authority. - Use Case: After signing a functional spec for a lending platform, run this Skill to produce eligibility, interest calculation, and compliance rule sections that downstream traceability and development agents consume. ## Quick Start Ask the agent to generate the business rules catalog for your project based on the signed functional specification.

Frequently Asked Questions about business-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document business rules for a software project?▼

Run this Skill after your functional specification is signed. It gathers project context and stakeholder input, then generates a business-rules.md catalog with one section per functional domain, each rule carrying an ID, condition, testable logic, examples, and exceptions.

What categories of business rules should a requirements document cover?▼

The catalog requires coverage of validation, authorization, calculation, lifecycle/state, temporal, and compliance categories. Each must be populated with rules or explicitly marked N/A with a reason, and every rule must trace to at least one functional requirement.

What must be completed before generating a business rules catalog?▼

The functional-spec document from the Define phase must exist and be signed. The Skill blocks execution until this prerequisite is satisfied, since rule domains and traceability links derive from the approved functional requirements.

Who approves a business rules document in an SDLC workflow?▼

The Business Systems Analyst (BSA) holds final approval authority over the Business Rules Catalog. The Business Owner validates rules and the Technical Lead reviews implementability, but only the BSA signature gates progression to the traceability skill.

Why does business rules generation fail validation?▼

Validation fails if prerequisites are unsigned, the document is not at its canonical path, placeholders remain, sections are empty, the author or document ID is malformed, cross-references are broken, or the document is not in English.