Story: Claude Code skills introduction

Table of Contents

This page documents a story in Sprint 04. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

Goal

Lay the foundations for the Claude Code skills layer. Sprint 04 is where skills go from "we'll use them eventually" to "they're part of the build". Three things land: the first concrete skill (PlantUML), build targets to deploy site + skills, and the analysis that ties skills to documentation.

Status

Field Value
State DONE
Parent sprint Sprint 04
Now Completed 2025-11-15.
Waiting on None.
Next None.
Last touched 2025-11-15

Acceptance

  • A PlantUML skill exists at doc/skills/ and exports to Claude Code's expected shape.
  • CMake exposes deploy_site and deploy_skills targets that invoke emacs against the appropriate build scripts.
  • The weaving analysis is captured and points at concrete follow-on work.

Tasks

Task State Start End Description
Weaving skills and documentation together DONE 2025-11-15 2025-11-15 Analyse how skills and project docs should link and overlap; capture the convention.
Create a skill for PlantUML documentation DONE 2025-11-15 2025-11-15 First Claude Code skill: how to author and refresh PlantUML diagrams within the project.
Add CMake targets for site and skills DONE 2025-11-15 2025-11-15 Add deploy_site and deploy_skills custom CMake targets that invoke emacs in batch mode.

Decisions

MASD as the framing
source code is the single source of truth; docs and skills are projections. The same content serves humans (via org-roam) and LLMs (via skills).
Skills live under doc/skills/ and export at build time
keeps them in version control as org-mode source.

Out of scope

  • A full taxonomic analysis of skills (the weaving analysis identifies it as a future deliverable).
  • PDF generation of the documentation set as a book (future).

See also

Emacs 29.1 (Org mode 9.6.6)