usecase-md-to-json

Convert Cockburn Markdown use cases into JSON and PlantUML diagrams.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/atanaka/uml-workflow-v3 --skill usecase-md-to-json
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: usecase-md-to-json
Source: https://github.com/atanaka/uml-workflow-v3/tree/main/skills/usecase-md-to-json
Command: npx skills add https://github.com/atanaka/uml-workflow-v3 --skill usecase-md-to-json

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts Cockburn-format Markdown use case specifications into structured JSON and regenerates the corresponding PlantUML use case diagram, keeping Markdown as the single source of truth and updating downstream artifacts for Step 3 and Step 4.

Core Features & Use Cases

  • Markdown-first workflow: converts Cockburn-formatted use cases to JSON and PlantUML diagrams.
  • Automatic synchronization: updates usecase-output.json and usecase-diagram.puml when Markdown files change.
  • Diagram regeneration: regenerates PlantUML diagrams to reflect the latest use cases and actor relationships.
  • Language-aware labeling: inherits language settings from existing JSON to produce bilingual labels in diagrams.
  • Versioned outputs: preserves existing metadata and merges changes with an existing output when present.

Quick Start

Edit UC-*.md files under usecase-specifications/ and run usecase-md-to-json to synchronize JSON and diagrams with your Markdown specs.

Frequently Asked Questions about usecase-md-to-json

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

FAQPage Schema
How do I convert Cockburn use case Markdown into JSON and diagrams?

To convert Cockburn use case Markdown, run a synchronization tool that parses Markdown specs, validates structure, and generates a JSON data file alongside a regenerated PlantUML diagram.

What is the best way to keep PlantUML diagrams synchronized with Markdown use case specifications?

The best way to keep PlantUML diagrams synchronized with Markdown is to maintain a Markdown-first workflow where editing source files automatically triggers regeneration of both the JSON output and the use case diagram.

Can I merge new Markdown use case changes with an existing JSON file without losing metadata?

Yes, you can merge new Markdown use case changes with an existing JSON file. The conversion process preserves existing metadata and merges updates, while inheriting language settings to maintain bilingual labels in diagrams.

Does this Markdown to JSON conversion approach support bilingual labels in PlantUML use case diagrams?

This Markdown to JSON conversion supports bilingual labels in PlantUML diagrams by inheriting language settings from the existing JSON output file during the diagram regeneration process.

How do I automate MBSE workflow artifacts when Cockburn Markdown specs are updated?

To automate MBSE workflow artifacts when Cockburn specs change, run a conversion process that automatically updates downstream usecase-output.json files and regenerates PlantUML diagrams to satisfy subsequent workflow steps.