Skip to content

Add diagrams as a prep question and a fixed Mermaid shape for the DAG - #8

Open
petaltank wants to merge 2 commits into
feat/roadmap-0.4from
feat/mermaid-diagrams
Open

petaltank wants to merge 2 commits into
feat/roadmap-0.4from
feat/mermaid-diagrams

Conversation

@petaltank

Copy link
Copy Markdown
Collaborator

Summary

Roadmap item 2 (meta/roadmap-0.4.md). Based on #6; GitHub retargets to master once #6 merges.

Two separate things, kept separate everywhere they're written:

(A) Diagrams as a tool. New prep question 5, diagrams: mermaid | ascii | none (unset → mermaid). Pass 2 offers a picture where a section is shaped enough to earn one — a when-to-draw table in the spec (erDiagram for ≥3 related tables, sequenceDiagram for multi-hop paths, flowchart LR for component maps, stateDiagram-v2 for lifecycles). Rule: draw when the picture is shorter than the paragraph. Prose is the decision; the picture is a rendering.

(B) The DAG, always, in one shape. Regardless of (A), the Pass 3 DAG is always Mermaid in a fixed form: flowchart TD, one subgraph per phase, node id = ticket id, one edge per blocked-by, four verbatim classDefs (open / inprogress / done / blocked) where node class = checkbox state. Re-rendered in both notes.md and TODO.md in the same commit as every status change — dstack-ticket (confirm → [~]), dstack-yolo ([~], [x], [!], DAG growth) and dstack-retro (a mismatch is a process observation) all name it. Ticket one-liners stay the source of truth.

Reference project: both ASCII DAGs converted; diagrams: mermaid in front matter; a Grounding bullet explains why Pass 2 drew nothing (two-table schema — shorter as prose).

Verification

  • Rendered both Mermaid blocks (reference TODO.md and the SKILL.md sample) with @mermaid-js/mermaid-cli — both parse; the four status classes show as intended.
  • ./install.sh into a scratch repo; grep diagrams: / classDef across spec, skill, commands, example, README.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr

petaltank and others added 2 commits September 11, 2026 14:53
Two separate things. (A) A fifth prep question, diagrams: mermaid | ascii | none, sets
the notation Pass 2 uses when a section is shaped enough to earn a picture; the rule is
draw when the picture is shorter than the paragraph it replaces, and the prose stays the
decision. (B) The Pass 3 DAG is always drawn in one rigid Mermaid form — flowchart TD,
one subgraph per phase, one edge per blocked-by, four verbatim classDef status classes —
and re-rendered in the same commit as every ticket state change, in both notes.md and
TODO.md. The ticket one-liners remain the source of truth; the diagram is derived.

dstack-ticket, dstack-yolo, and dstack-retro name the re-render at each status flip.
The reference project's ASCII DAGs are converted to the conventional shape.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant