Results for “business-rules”

Analyzes requirements and produces four artifact files: requirements.md, user-stories.md, acceptance-criteria.md, and business-rules.md, with optional loading from SRS workflow artifacts.

Design or revise a company's commercial policy governing discounts, approver thresholds, exception flows, and deal frameworks using data-backed matrices and linting tools.

Define company values and culture for a minimalist business, drawing on principles from The Minimalist Entrepreneur.

Diagnoses business models using dontbesilent's ontological framework, offering consultation mode to dissolve problems and checkup mode to analyze business structures.

Translate design decisions into business value by reading financials, mapping competitive landscapes, and defending design work in ROI terms.

Provides evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflows for sales snapshots, pricing comparisons, duplicate-charge diagnosis, or code-backed billing reality.

Personal working rules, decision frameworks, and preferences for ejarbe. Invoke with /rules to surface these during any session. AUTO-TRIGGER when working with MCP servers, MCP transport, SSE, streamable HTTP, server migration, .well-known metadata, or MCP server discovery/registration.

Applies the BIZBOK enterprise architecture framework to structure analysis, problem solving, and decision documentation.

Drafts monthly investor updates, quarterly board decks, and high-signal stakeholder communications that surface wins, misses, risks, and asks clearly.

Breaks down a company's business model, revenue signals, positioning, pricing, moat, and weak points into a fixed, comparable template with fact-versus-inference labeling.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.