dtpr-datachain-structure
The meta-structure schema-tier skill. Critiques or proposes changes to the datachain-type shape itself — which categories exist, which are required vs optional, whether a whole category should retire or split. This is distinct from auditing elements inside one category (dtpr-category-audit) or drafting a new element (dtpr-element-design).
When to fire
- The user wants to critique the datachain-type's category set.
- The user identifies a system class that the current 11-category shape does not fit.
- The user proposes retiring a whole category or merging two categories.
- The user asks how DTPR's taxonomy should evolve for a regulatory regime (EU AI Act tiers, NIST RMF alignment).
Trigger phrases
"critique the taxonomy", "brainstorm DTPR structure", "how should DTPR handle this system shape", "should DTPR add a category", "does the datachain-type miss X", "restructure DTPR", "what categories is DTPR missing".
Workflow
Phase 0 — Classify input. Scenario / change proposal / document / critique-the-existing-shape.
Phase 1 — Load the current datachain-type. Calls get_schema with include: "full"; captures version and content_hash.
Phase 2 — Corpus lookup. Reads the research corpus INDEX.md with tags typically including concept:<slug>, framework:<name>, standard:<name>, jurisdiction:<iso>. Dispatches a researcher on miss if Task is available.
Phase 3 — Draft the proposal. Uses the Scenario / Gaps / Proposed changes {Add/Edit/Retire} template. When a proposal retires a whole category, the output must include an element-migration plan: a list of affected elements with their proposed new homes plus explicit "elements with no migration path" flagged for user decision.
Phase 4 — Inline the Comprehension check. Copies the comprehension block template verbatim, grading the proposal against the rubric. Symbol legibility is typically n/a at meta-structure scope.
Phase 5 — Emit the handoff line pnpm --filter ./api schema:new <type> <YYYY-MM-DD>-beta. The skill does not invoke it.
Phase 6 — Recommend a sibling handoff when the proposal implies element-level drafting or category-level audit.
Output
A Markdown proposal (Scenario / Gaps / Proposed changes) + the inline Comprehension check + the schema:new command line + any sibling-skill recommendation. A human edits the beta directory by hand after running schema:new.
Non-goals
Does not invoke schema:new or modify files under api/schemas/. Does not write element-level YAML — route to dtpr-element-design. Does not audit one category's coherence — route to dtpr-category-audit.
Source
plugin/dtpr/skills/dtpr-datachain-structure/SKILL.md in the repository.