docs-business

Name: docs-business
Availability: InStock
Author: evengul

Document business rules, domain workflows, and operational logic for MC-ORG.

Updated Jun 26, 2022

Search Tags:#project management #access control #business rules #workflows #domain logic #mc-org

Ready to run

npx skills add https://github.com/evengul/mc-org --skill docs-business

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-business
Source: https://github.com/evengul/mc-org/tree/main/.claude/skills/docs-business
Command: npx skills add https://github.com/evengul/mc-org --skill docs-business

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive reference for the business rules, domain workflows, and operational logic that govern the MC-ORG application, ensuring consistent and correct implementation of its features.

Core Features & Use Cases

Business Logic: Understand domain rules, project lifecycle stages, and task management constraints.
Access Control: Reference role hierarchies and user permission levels.
Workflow Definitions: Clarify invitation processes, dependency rules, and notification triggers.
Use Case: When developing a new feature that modifies project stages, consult this Skill to ensure the implementation adheres to the defined lifecycle and auditing requirements.

Quick Start

Explain the role hierarchy and the capabilities of each role within MC-ORG.

Frequently Asked Questions about docs-business

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

FAQPage Schema

How do I document business rules and domain workflows for project management?▼

Documenting business rules and domain workflows involves defining project lifecycle stages, task management constraints, and operational logic to ensure consistent feature implementation and correct application behavior.

How does role-based access control work for application user permissions?▼

Role-based access control works by defining a role hierarchy where specific permissions are assigned to each role, restricting user capabilities and clarifying invitation workflows based on their assigned level.

What are the constraints for preventing circular project dependencies?▼

Preventing circular project dependencies requires enforcing constraints within the domain logic that restrict how projects link to one another, ensuring no recursive loops exist in the project hierarchy.

When do I need to reference domain logic for modifying project lifecycle stages?▼

You need to reference domain logic when developing new features that modify project stages, ensuring the implementation adheres to defined lifecycle rules and auditing requirements for operational consistency.

Does this business rules reference cover invitation workflows and notification triggers?▼

Yes, this business rules reference covers invitation workflows, dependency rules, and notification triggers, providing clear definitions for how these processes operate within the application's domain logic.

What is the best way to explain the role hierarchy and capabilities within MC-ORG?▼

The best way to explain the role hierarchy is to reference the documented access control rules, which outline each role's specific capabilities and permission levels within the MC-ORG application.