diagram-edit

Diagram Edit

Apply a natural-language instruction to one workhub diagram note by rewriting only the affected lines.

The workhub app's Diagrams tab launches this skill with the file path and the instruction (and, in confirm mode, asks for a diff instead of a write). It also works when invoked by hand. It is the one skill for every kind of diagram: it carries the shared procedure and nothing about any single format.

Find the format first

The rule file is the source of truth for the notation. This skill does not repeat it. Read the note, then its rule, before changing a line:

1. Read the whole target file and take the frontmatter type.

2. Read the rule for that type (the vault's .claude/rules/):

   type	Rule to read
   schedule	schedules.md
   mindmap	mindmaps.md
   matrix2x2, flow, pfd, algorithm, usecase, architecture, ifdam	diagrams.md - the shared section and the section named after the type

   The rule normally loads on its own when you read a note under diagrams/, schedules/ or mindmaps/; a note inside a backlog item does not always trigger it, so open the file yourself when it did not appear.

3. A type that is none of those nine, or a file with no type outside schedules/ and mindmaps/, is not a diagram: say so and change nothing.

A kind added to the app later works the same way: its rule names its format, and everything below still applies.

Procedure

1. Identify the elements the instruction names, by title or by id. If it is ambiguous which element is meant, say so and stop - do not guess and edit.
2. Work out the new content from the current file: relative instructions ("a week later", "one level up", "group these") can only be computed from what is there. Moving an element moves what hangs off it (a mindmap subtree, an element's indented note lines, its stickies stay pinned).
3. Rewrite only the affected lines, in place, keeping the order of everything else.
4. Validate against the rule before writing: every line you touched still parses by the kind's grammar, ids are unchanged and unique, colours are in the list, and no element lost a task: link, a note line or a modifier unless the instruction asked for that.
5. Set updated: to today's date in the frontmatter and leave every other key as you found it.
6. Write the file, then report in one paragraph: which element ids changed, from what to what, and anything you declined to do. In confirm mode, do not write: report the exact lines you would change, as a diff, and stop.