business-logic-checker

Reviews requirement models, design documents, and API specs for business logic gaps and risks.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/fen-zx/NovelToScript --skill business-logic-checker-fen-zx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-logic-checker
Source: https://github.com/fen-zx/NovelToScript/tree/main/.agents/skills/business-logic-checker
Command: npx skills add https://github.com/fen-zx/NovelToScript --skill business-logic-checker-fen-zx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design documents and requirement models often contain hidden flaws—missing permissions, broken state transitions, absent transaction handling, and undefined AI failure recovery—that only surface during development or production. This Skill systematically audits business designs before coding begins, producing a scored review report with prioritized risks. ## Core Features & Use Cases - Comprehensive Logic Audit: Checks business rules, permissions (CRUD/Export/Manage), state machines, data models, transactions, APIs, AI pipelines, async queues, performance, and security across 13 structured sections. - Scored Risk Report: Outputs an overall score (0-100), risk level (High/Medium/Low), a consolidated risk list, and actionable improvement suggestions. - Use Case: Before developing a novel-to-script conversion feature, feed the RequirementAnalyzer output, PAGE_SPECS.md, and API_SPECS.md into this Skill to discover that script deletion lacks a version cascade policy and the AI generation flow has no retry mechanism. ## Quick Start Review the attached design document and API specification for business logic gaps, then output a scored risk report with improvement suggestions.

Frequently Asked Questions about business-logic-checker

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

FAQPage Schema
How do I review a design document for business logic gaps before development?▼

Feed the requirement model, design document, and API specs into the checker, which systematically examines permissions, state transitions, transactions, and data consistency. It outputs a scored report listing each issue with its cause, risk level, and suggested fix.

What should a business logic review checklist include?▼

A thorough checklist covers business rules, CRUD and export permissions, entity state machines, cascade deletion policies, multi-table transactions, API completeness, AI flow retry and timeout handling, async queue jobs, indexing, and file upload security.

How do I check an AI generation workflow for failure handling?▼

Verify the LLM pipeline defines input validation, output schema checks, timeouts, retry limits, and failure recovery paths. The checker flags missing retry mechanisms and undefined task status queries as risks with severity ratings.

What inputs does the business logic checker accept?▼

It accepts RequirementAnalyzer output, DesignGenerator output, PAGE_SPECS.md, and API_SPECS.md documents. It builds a business flow model from these inputs and runs ten inspection steps before producing the final review report.

When should I run a business logic review in the development workflow?▼

Run it after requirements and design documents are drafted but before coding starts. Catching missing state transitions, undefined permissions, and absent cascade policies at this stage prevents costly rework during implementation.