From dwsd-md
Read, write, and review DWSD organization entities — the Dynamic Work Systems Design markdown format (entity types, frontmatter contracts, wikilink relationships, the board and flightroute DSLs, and the flat per-type folder layout). Use whenever creating, editing, or reviewing files in a DWSD org folder, or when asked about the DWSD format.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dwsd-md:dwsd-formatThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
DWSD describes an organization as a folder of Markdown files: **one file = one entity**,
DWSD describes an organization as a folder of Markdown files: one file = one entity,
and the type: field in the frontmatter decides what it is. Entities are grouped into flat
plural per-type folders (individuals/, roles/, units/, work-systems/,
interactions/, agreements/, signals/, insights/, drivers/, proposals/,
design-records/, visualizations/, flight-item-types/, flight-routes/,
ai-agents/) — the folder is a convenience; the type: is authoritative.
This skill is a thin pointer; the full contract lives in the bundled spec (the same
files as the dwsd-markdown repo). Before authoring or validating, read:
${CLAUDE_PLUGIN_ROOT}/conventions.md — rules for every entity: frontmatter, the
type field, [[wikilink]] relationships, reports-to (structure) vs member-of
(flow), tracking fields, the sources block, the embedded DSL fences, and .mw siblings.${CLAUDE_PLUGIN_ROOT}/types/<type>.md — the per-type contract (required vs optional
frontmatter, relationships, body sections, a worked example). Always open the specific
type page before authoring that type.${CLAUDE_PLUGIN_ROOT}/templates/<type>.md — a bare copy-paste skeleton per type.${CLAUDE_PLUGIN_ROOT}/examples/goldcrust-bakery/ — a complete worked example.type: value is not always the conceptual typeTwo conceptual types are expressed as a base type: plus a discriminator — there is no
type: work-system or type: meeting. Recognize them by the discriminator, and place them
by the conceptual type, not the bare type::
type: unit whose unit-type includes work-system (e.g.
unit-type: [team, work-system]); it also carries a flightlevel: 1|2|3. Lives in
work-systems/ and carries the full domain description. A unit without work-system in
its unit-type is just a structural unit (e.g. unit-type: team) and lives in units/.type: interaction with interaction-type: meeting. Lives in
interactions/, alongside non-meeting interactions.When scanning an org, key off the discriminator (unit-type containing work-system,
interaction-type), not type: alone.
[[wikilinks]] in frontmatter, pointing at the target's label
(its filename without .md). [[Target]] and [[Target|Alias]] both resolve to
Target. Hyphen and underscore field spellings are both accepted.reports-to = structure (individuals only). member-of = flow (individual or
unit). derived-from and delegator are metadata, not typed edges.<base>-type: unit-type, interaction-type,
agreement-type, visualization-type. Each may hold a single token or a YAML list
(e.g. unit-type: [team, work-system]). flightlevel is one word.visualization → ```board; flight-route →
```flightroute. Inside the DSL, work systems and item types are referenced by
@-handle (the target's slug). See ${CLAUDE_PLUGIN_ROOT}/types/visualization.md and
${CLAUDE_PLUGIN_ROOT}/types/flight-route.md.signal → insight → driver → proposal → agreement,
linked downward with derived-from.${CLAUDE_PLUGIN_ROOT}/types/<type>.md for its contract.${CLAUDE_PLUGIN_ROOT}/templates/<type>.md.[[wikilinks]].When in doubt, the bundled spec wins — this skill never overrides it.
npx claudepluginhub worksystems-design/dwsd-markdownCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.