formulate-data-model

Challenge and revise existing BDD-annotated RDB logical data models against business knowledge.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/nakamori-naoya/bdd-discovery-and-formulation-plugins --skill formulate-data-model-nakamori-naoya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: formulate-data-model
Source: https://github.com/nakamori-naoya/bdd-discovery-and-formulation-plugins/tree/main/plugins/bdd-discovery-and-formulation/skills/formulate-data-model
Command: npx skills add https://github.com/nakamori-naoya/bdd-discovery-and-formulation-plugins --skill formulate-data-model-nakamori-naoya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Existing logical data models drift out of sync with business rules as edge cases, boundary values, ordering, duplication, and concurrency concerns emerge. This Skill stress-tests an existing BDD-annotated RDB logical data model against its corresponding business knowledge documents and writes confirmed findings back into the same canonical document. ## Core Features & Use Cases - QA-Driven Refutation: Applies boundary values, counterexamples, ordering, duplication, concurrency, time, retroactivity, and failure-guarantee perspectives to persistence claims in the existing model. - Same-Path Updates: Guards that revisions are written back to the exact same canonical document path, never creating new or duplicated logical documents. - Structural Validation: Verifies scenario condition matrices, resource/event table classification, time conventions, and append-only event table declarations via deterministic scripts. - Use Case: Given an existing order/cancel/refund logical data model and its business knowledge documents, challenge it with deadline-boundary and double-cancellation scenarios, then update the same document with the confirmed BDD scenarios and revised tables. ## Quick Start Challenge my existing BDD-annotated logical data model at the given path against its business knowledge documents, testing boundary and concurrency scenarios, and update the same document with the confirmed findings.

Frequently Asked Questions about formulate-data-model

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

FAQPage Schema
How do I update an existing logical data model with new edge cases?▼

Provide the absolute path of the existing BDD-annotated logical data model plus its corresponding business knowledge documents. The skill challenges persistence claims with boundary, ordering, and concurrency scenarios, then writes confirmed findings back to the same document path.

What inputs are required to formulate a data model?▼

You must supply business_knowledge_paths as absolute paths of git-tracked files, plus the existing_logical_document_path of the model to revise. Missing, relative, symlinked, or untracked paths cause the skill to stop without modifying anything.

Does this skill create new logical data model documents?▼

No. It only updates the existing canonical document at the same path, verified by an update-guard script comparing resolved file identities. Creating a new model from scratch is handled by a separate discovery entry point.

Can it handle physical design like indexes or DBMS types?▼

No. Read patterns, indexes, physical types, DBMS features, isolation levels, and placement are explicitly excluded from the logical document. Those concerns are handed off to physical design instead of being mixed into the logical model.

What happens when a business question cannot be resolved?▼

Unresolved questions are recorded as open items with a recommended hypothesis, its rationale, and the interpretations not adopted. The revision proceeds with the most plausible hypothesis explicitly marked in the relevant BDD scenarios and model elements.