pm-business-rules-library

Create structured business rule libraries and decision tables for product management workflows.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-business-rules-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-business-rules-library
Source: https://github.com/ljucask/pureinn-product-development/tree/main/skills/pm-business-rules-library
Command: npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-business-rules-library

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of scattered business rules and undocumented decision logic by creating structured, maintainable registers that keep product constraints consistent across development.

Core Features & Use Cases

  • Business Rules Library Creation: Builds a centralized catalog of business rules with unique BR identifiers, priorities, statuses, entity mappings, and lifecycle tracking.
  • Decision Model Management: Creates decision tables with TBL identifiers to define complex conditions, outcomes, and edge cases for product logic.
  • Use Case: A product team launching a marketplace can use this Skill to replace a monolithic BRD with continuously updated business rules and decision models referenced by feature specifications.

Quick Start

Ask the AI to create or update the business rules library and decision models for my product using the available PRD and domain context.

Frequently Asked Questions about pm-business-rules-library

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

FAQPage Schema
How do I centralize business rules and decision logic for product management?

To centralize business rules, you create a structured library with unique identifiers, priorities, statuses, and entity mappings to replace fragmented logic documentation and maintain consistency across development workflows.

How do I build decision models for complex product features and edge cases?

Building decision models involves generating decision tables with specific identifiers to define complex conditions, outcomes, and edge cases for product logic, ensuring comprehensive coverage of business decisions.

What is the best way to replace a monolithic BRD with maintainable product constraints?

The best way to replace a monolithic BRD is creating continuously updated business rules and decision models with lifecycle tracking, referenced directly by feature specifications and development artifacts.

Can I map domain entities and track lifecycle statuses for feature planning?

Yes, you can map domain entities and track lifecycle statuses by creating structured rule registers that apply to feature definition, domain modeling, and compliance constraints within product management workflows.

Does creating a business rules library require existing PRD and domain context?

Creating a business rules library requires existing PRD and domain context to accurately identify rules, map entities, generate decision tables, and integrate constraints with feature development artifacts.