Format Reference
Each task is one line. All fields use keyword: value format.
@task: <num> name: <name> start: <MM/DD/YYYY> dur: <days> dep: <dep1,dep2>
@task: line marker and task number — use dotted hierarchy e.g. 1 1.1 2.3
name: task name (required)
start: start date MM/DD/YYYY (required unless dep: is given)
dur: duration in working days Mon–Fri (required)
dep: comma-separated dependencies (optional)
Rules
· Keywords can appear in any order after the task number.
· Weekends are skipped — duration and chart both count Mon–Fri only.
· A dependent task starts the next working day after ALL its deps finish.
· When both start: and dep: are given, dep: takes priority.
· Tasks sharing the same top-level number (e.g. 1.x) are grouped together.
· Blank lines and lines starting with // or -- are ignored.
Example
@task: 1 name: Project Kickoff start: 04/13/2026 dur: 1
@task: 1.1 name: Requirements start: 04/13/2026 dur: 5
@task: 1.2 name: Design dur: 5 dep: 1.1
@task: 2.1 name: Development dur: 10 dep: 1.2
@task: 2.2 name: Testing dur: 5 dep: 2.1