Description
Dotabase Design and Creation helps a user decide where a kind of knowledge should live, then stands up the corresponding Dotabase. It supports fresh guided design, deterministic creation from an approved redline, import-oriented stores, derived Dotabases, and ongoing management. Properties, views, behaviors, fill rules, and edge needs are treated as one information-design problem rather than disconnected schema commands.
The workflow uses conversational rounds for decisions only the owner should make, then hands mechanical work to scripts with explicit read-back. It can recognize when an existing Dotabase is the better answer and avoids silently changing fixed schema vocabulary. This is a shared feature: Dots supplies the data primitive, while IAGREED supplies the guided operating workflow.
Selling Points
- Turns a vague “I need somewhere for this” into a usable knowledge system with an understandable structure.
- Keeps schema, views, behaviors, and imports coherent instead of accumulating one-off fields.
- Supports both new stores and transformations of existing knowledge.
- Uses deterministic creation and verification after the human-facing design decisions are settled.
- Preserves the owner’s taxonomy while preventing agents from inventing schema options during writes.
User Story
A researcher has a folder of vendor notes and wants a durable comparison system. The workflow inventories the corpus, proposes properties and views, runs concise redline rounds, and creates the approved Dotabase with an import path. The researcher walks away with a working store shaped around real questions rather than a generic table.
Extension Surface
The feature is configurable because users shape schemas, views, properties, behaviors, and derivations through supported options. payload/skills/dotabase/workflows/create-dotabase.md governs guided design, and payload/skills/dotabase/scripts/create-dotabase.mjs applies the result. Reference playbooks under payload/skills/dotabase/references/ cover imports and derived stores. The plugin workflow does not expose a code-level provider interface.
Capabilities & Limits
- Designs and creates fresh Dotabases with properties, views, and behavior decisions.
- Imports existing corpora, derives new stores, and manages supported schema evolution.
- Validates live schema values and reads back deterministic operations.
- Limit: it cannot invent locked platform options, bypass environment or tenancy rules, or decide the owner’s taxonomy when multiple product meanings remain plausible.
Implementation Map
payload/skills/dotabase/SKILL.mdpayload/skills/dotabase/workflows/create-dotabase.mdpayload/skills/dotabase/workflows/manage-dotabase.mdpayload/skills/dotabase/scripts/create-dotabase.mjspayload/skills/dotabase/references/properties-and-views.md