Automatic scheduling
PlanQ can compute dates for eligible unscheduled tasks without changing the source plan:
planq solve project.plan --now 2026-10-05solve validates the complete entry closure first. It returns a versioned JSON result and exits with 0 for solved or not-required. Incomplete inputs, infeasible constraints, and unproven results exit with 1 and never include a partial schedule.
Eligibility
PlanQ keeps items with explicit dates fixed. It computes:
todoleaf tasks withpdeffort and at least one assignmenttodomilestones with anafterdependency whose endpoint is known
A completed item without dates stays unscheduled. A task without effort or an assignment also stays unscheduled unless another computed constraint requires its endpoint. In that case, PlanQ returns input-incomplete.
Effort, load, and capacity
Effort is total demand in person-days. An assignment load is the fixed daily demand that a task places on that person. Capacity is the person's total daily supply shared by all tasks.
For example, effort 3pd at load 0.5 needs six execution days. PlanQ does not reduce the load or replace the assignee. If leave, a work schedule, or a capacity override makes an assignee unable to provide the declared load, the task pauses for that project workday and resumes later. The result records the actual workDates; the Gantt bar remains one continuous envelope.
Planning date
The planning date is selected in this order:
--now YYYY-MM-DD- the entry plan's
:now - the session date in the project calendar timezone
An included plan cannot override the entry date. now is a reproducibility boundary and the earliest date for computed work. It does not represent task progress or reduce effort.
Use the same override for a live preview:
planq dev project.plan --now 2026-10-05The VS Code extension can pass the same value through the machine-scoped plan.preview.now setting.
Hard constraints
Dependencies, deadlines, summary and include boundaries, project workdays, and per-person daily capacity are hard constraints. PlanQ never publishes dates that violate them. A proven conflict returns infeasible; a deterministic limit, runtime failure, or exhausted finite horizon returns unknown.
During a live re-solve, the workbench keeps the previous complete frame. If the new constraints fail, it keeps that last renderable schedule, marks it as not updated, and shows diagnostics from the current input. It does not present the old schedule as a new successful result.
Cache and source ownership
PlanQ may cache a validated result under .plan/solve/. The cache is local, Git-ignored, and keyed by the source, resources, planning date, engine version, and deterministic parameters. A mismatch causes a fresh solve.
Computed dates are never written to .plan, normalized IR, or an edit set. Replace effort with explicit start and end fields only when you intentionally want to freeze a task's dates.