One-click install
npx skills add https://github.com/howarddierking/mermaid-event-model --skill spec-slices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-slices
Source: https://github.com/howarddierking/mermaid-event-model/tree/main/skills/spec-slices
Command: npx skills add https://github.com/howarddierking/mermaid-event-model --skill spec-slices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of manually keeping slice documentation and slice tests aligned with an evolving Event Model DSL, which otherwise becomes tedious to update and risky to let drift out of date.

Core Features & Use Cases

  • Generates slice specification files: Creates one markdown spec per slice <id>["Label"] in your Event Model DSL.
  • Auto-refreshes the Model section: Rebuilds only the slice’s ## Model eventModel snippet from the current DSL while preserving your authored ## Description and ## Tests.
  • Safely handles renamed or removed slices: Detects orphan specs and deletes untouched stubs, or interactively merges authored content into the correct current slice to avoid losing work.

Quick Start

Run spec-slices with the path to your Event Model DSL file to generate or refresh the per-slice markdown specs in the corresponding -slices directory.

Frequently Asked Questions about spec-slices

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

FAQPage Schema
How do I generate markdown documentation from an Event Model DSL?

To generate markdown documentation from an Event Model DSL, parse the fenced mermaid DSL to extract slices, then write one specification markdown file per slice into a sibling slices directory.

How do I keep slice specifications synchronized with an evolving Event Model DSL?

To keep slice specifications synchronized with an evolving Event Model DSL, rebuild each spec's derived Model section from the latest DSL while preserving your authored Description and Tests sections.

What happens to slice documentation when slices are renamed or removed from the DSL?

When slices are renamed or removed from the DSL, the tool detects orphan specifications, deletes untouched stubs, and interactively merges authored content into the correct current slice to prevent data loss.

Can I use this to maintain slice tests alongside documentation for code generation workflows?

Yes, you can maintain slice tests alongside documentation for code generation workflows by using this tool to document and test event-model slices for validation and iterative model refactoring.

Do I need any external dependencies to parse the eventModel mermaid DSL for slice extraction?

No external dependencies are required to parse the eventModel mermaid DSL for slice extraction; the tool operates standalone to extract referenced nodes and edges directly from the fenced DSL block.