check-requirement-delta

Detect conflicts between new requirements and existing GraphQL schemas, Prisma models, and authorization rules.

3|2|Updated Jun 25, 2024
One-click install
npx skills add https://github.com/Hopin-inc/civicship-api --skill check-requirement-delta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-requirement-delta
Source: https://github.com/Hopin-inc/civicship-api/tree/main/.claude/skills/check-requirement-delta
Command: npx skills add https://github.com/Hopin-inc/civicship-api --skill check-requirement-delta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects conflicts between new requirements and existing system specifications (APIs, data models, and business rules) to prevent unsafe changes and surface actionable mitigations.

Core Features & Use Cases

  • Comprehensive conflict detection across GraphQL schemas, Prisma models, and RLS/authorization rules.
  • Outputs a structured risk report detailing affected domains, data model impact, API changes, and recommended migration steps.
  • Supports phased migration planning and traceability for governance and compliance.

Quick Start

Identify conflicts between a given set of requirements and the current system's schemas and rules to guide safe integration.

Frequently Asked Questions about check-requirement-delta

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

FAQPage Schema
How do I detect requirement conflicts in a GraphQL schema?

Conflict detection for GraphQL schemas analyzes new requirements against existing APIs, data models, and authorization rules. It surfaces actionable remediation steps to ensure safe integration and API compatibility.

What is requirement conflict detection for system migrations?

Requirement conflict detection identifies clashes between new requirements and existing system specifications like Prisma models or authorization rules. It outputs a structured risk report detailing data model impact and recommended migration steps for safe integration.

How do I check new requirements against existing Prisma models and authorization rules?

Checking new requirements against Prisma models and authorization rules requires comprehensive conflict detection. This identifies data model mismatches and business rule violations, outputting a structured risk report that supports phased migration planning and traceability.

Does conflict detection work with Prisma models and RLS authorization rules?

Yes, conflict detection supports Prisma models and RLS authorization rules. It identifies potential conflicts between new requirements and existing specifications, delivering structured findings that support data integrity, API compatibility, and risk mitigation.

What is the best way to plan safe API migrations when adding new requirements?

The best way to plan safe API migrations is using conflict detection to surface actionable mitigations before applying changes. It delivers a structured risk report detailing affected domains, supporting phased migration planning and traceability for governance and compliance.