business-rules

Generates a business rules document from domain model invariants and per-subdomain rules.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill business-rules-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-rules
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/business-rules
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill business-rules-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lose track of critical business constraints scattered across conversations and code. This Skill consolidates invariants, validation rules, and state transitions into a single structured Business Rules document grounded in the existing domain model. ## Core Features & Use Cases - Domain Model Integration: Reads the existing domain model, extracts invariants and subdomains, and reuses them instead of asking redundant questions. - Structured Rule Capture: Guides the user through critical rules, per-subdomain rules, validation rules, and state transitions using enforcement language (must/cannot/only when). - Frontend vs Backend Enforcement Matrix: Records which rules need client-side validation versus server-only enforcement. - Use Case: After defining a domain model for a budgeting app, run this Skill to produce docs/02_business/business_rules.md with critical invariants, field validations with error messages, and irreversible state transitions documented. ## Quick Start Ask the assistant to create the business rules document based on the existing domain model in the docs folder.

Frequently Asked Questions about business-rules

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

FAQPage Schema
How do I create a business rules document from a domain model?▼

Run this Skill after generating a domain model. It reads docs/02_business/domain_model.md, extracts existing invariants and subdomains, then asks targeted questions to expand rules per subdomain before writing business_rules.md.

What should a business rules document include for a software project?▼

It should include critical invariants, rules per subdomain phrased with enforcement language, validation rules with user-facing error messages, state transitions marking irreversible changes, and a frontend versus backend enforcement matrix.

Can I run business-rules without a domain model?▼

No. The Skill requires docs/02_business/domain_model.md as its foundation and will instruct you to run the domain-model skill first if the file is missing.

How are state transitions documented in business rules?▼

For each entity with states defined in the domain model, the Skill asks for allowed transitions and conditions, then records them explicitly, marking irreversible transitions such as ones that can never return to a prior state.

Where does the business rules output file get written?▼

The document is written to docs/02_business/business_rules.md. The Skill auto-detects the docs folder, asks when multiple candidates exist, and creates the folder if missing.