Menu
Generates docs/kanban/board.json from Meridian user story frontmatter. Use after creating or changing user stories.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Closes a Meridian sprint after sprint review — fills Retrospective, sets status complete, logs decisions. Use with /complete-sprint vX-SY.
Closes a Meridian user story after implementation — fills Record, acceptance, status and board. Use when marking US done, completing US-XXXX, or after implementing a user story.
Creates a Meridian epic file in docs/epics after architecture is approved. Use when defining a new product capability block before user stories.
Creates a Meridian sprint file in docs/sprints linked to a version. Use when planning execution slices within a release.
Creates a valid Meridian user story after epics and versions are approved. Use when adding work to docs/us and keeping acceptance criteria concrete.
Creates a Meridian release file in docs/versions. Use when defining a new product version before user stories.
| name | generate-board-json |
| description | Generates docs/kanban/board.json from Meridian user story frontmatter. Use after creating or changing user stories. |
| allowed-tools | Read, Glob, Grep, Bash, Edit, Write |
| File | When to read |
|---|---|
references/board-schema.md | Field validation and divergences |
docs/us/US-XXXX.md → derived → docs/kanban/board.json
Never edit the board as primary source.
docs/us/US-*.mdid, title, epic, version, status, moscow, depends_on, done_when, tests, tests_status, readyreferences/board-schema.md and epics/versions foldersdocs/kanban/board.jsonpython .agent/scripts/validate_meridian.py <project-root>
Stories read:
Stories exported:
Invalid stories:
Board path:
Warnings: