---
name: markdownto-gantt
description: Create or edit Markdown To project schedules with explicit dates, progress, and dependencies.
---
# Markdown To gantt
## Contract and workflow
Read `mdto spec gantt` (or the adjacent `SPEC.md` in a checkout) and the
[shared conventions](https://markdownto.ai/specs/conventions.md) before authoring or
repairing content. Outside a checkout, use the [published spec](https://markdownto.ai/specs/gantt.md).
This skill accompanies `[email protected]`. The spec and its fixtures govern conformance;
editorial advice below is non-normative and should adapt to the user's brief.
If the source declares another version, obtain its matching contract before changing it.
Use `markdownto: [email protected]`. Level-2 headings are workstreams. Tasks carry inclusive
start/end dates; consult the spec for schedule, progress, and dependency constraints.
Use `schedule`, `progress`, `depend`, and other declared verbs for mutations. Progress
100 checks a task; a dependency does not authorize silently rescheduling its successors.
## Content quality
Build the schedule around deliverables and real dependencies. Distinguish committed
dates from proposed dates in accompanying prose rather than presenting guesses as facts.
Check whether parallel work is plausible for the people doing it and whether handoffs
have room to happen. Keep workstreams coherent, expose critical assumptions, and choose
a task size at which progress can be assessed honestly.
## Check and deliver
Validate the file with `mdto validate <path>` before editing existing content and again
after changes. Read diagnostics against the spec's rationale; preserve meaning when
repairing syntax. Prefer spec-owned verbs for edits they support, checking their current
`--help`; otherwise make a focused source edit, preserving unrelated content and IDs.
Render with `mdto render <path>` and inspect the result when available. Validation checks
structure, not editorial quality: review the content against the user's purpose as well.
Without the CLI, use the contract and examples and report that validation was not run.
Deliver the Markdown source and any requested artifacts, stating what was actually checked.
Give this guide to your agent, or read it as an author. It covers workflow and editorial judgment; the specification defines conformance.
Contract and workflow
Read mdto spec gantt (or the adjacent SPEC.md in a checkout) and the shared conventions before authoring or repairing content. Outside a checkout, use the published spec. This skill accompanies [email protected]. The spec and its fixtures govern conformance; editorial advice below is non-normative and should adapt to the user's brief. If the source declares another version, obtain its matching contract before changing it.
Use markdownto: [email protected]. Level-2 headings are workstreams. Tasks carry inclusive start/end dates; consult the spec for schedule, progress, and dependency constraints. Use schedule, progress, depend, and other declared verbs for mutations. Progress 100 checks a task; a dependency does not authorize silently rescheduling its successors.
Content quality
Build the schedule around deliverables and real dependencies. Distinguish committed dates from proposed dates in accompanying prose rather than presenting guesses as facts. Check whether parallel work is plausible for the people doing it and whether handoffs have room to happen. Keep workstreams coherent, expose critical assumptions, and choose a task size at which progress can be assessed honestly.
Check and deliver
Validate the file with mdto validate <path> before editing existing content and again after changes. Read diagnostics against the spec's rationale; preserve meaning when repairing syntax. Prefer spec-owned verbs for edits they support, checking their current --help; otherwise make a focused source edit, preserving unrelated content and IDs. Render with mdto render <path> and inspect the result when available. Validation checks structure, not editorial quality: review the content against the user's purpose as well. Without the CLI, use the contract and examples and report that validation was not run. Deliver the Markdown source and any requested artifacts, stating what was actually checked.