{phase}-PLAN.md — the phase plan as a set of executable task prompts, written by gsd-planner under gsd-plan-phase and gated by gsd-plan-checker before execution. Each task becomes a unit of work for a gsd-executor in an execution wave. In MVP mode on Phase 1 a SKELETON.md is produced alongside it.
Produced by (backlinks)
GSD:
- gsd-plan-phase — orchestrates planning and gating.
- gsd-planner — authors the executable task prompts.
Addy Osmani — Agent Skills:
- addy-planning — writes
tasks/plan.md+tasks/todo.md.
OpenSpec:
- openspec-propose — emits
tasks.md, a hierarchically numbered (1.1, 1.2, …) checklist with checkboxes, as the last of its four planning artifacts. - openspec-apply — walks and checks off that checklist (its resumable progress ledger).
Spec Kit:
- speckit-tasks — emits
tasks.md: an ordered list with[P]markers on independently parallelizable tasks, sequenced test-first (contract → integration → unit). - speckit-converge — appends new tasks to the list from the codebase-vs-spec gap.
Compound Engineering:
- ce-plan — enriches requirements into
docs/plans/guardrail plans (U-IDs + test scenarios, WHAT-not-HOW).
Builder Methods — BM Skills:
- bm-prd-creator — emits a sequence of milestone prompt files (
milestones/N-{slug}/prompt.md) alongside the PRD — ready-to-build prompts that drive a coding agent through implementation (a specify→plan bridge for non-technical builders).
nano-spec:
- nano-spec-create — the pack’s
todo.md: research/implementation/verification checklists + Must/Nice/Out acceptance criteria (part of the artifact-nano-spec-pack).
pstack — one entry, and a reluctant one (“i don’t believe in planning. the best spec is code”):
- pstack-figure-it-out — the designed phase list, written down explicitly because that list is what the human reviews. Produced only when no bundled playbook fits, and paired with an artifact-decision-log rather than standing alone.
builder-skills:
- builder-plan-arbiter — the arbitrated execution plan, with Borrowed From Other Plans, Rejected, and Executor Recommendation sections.
- builder-visual-plan — the plan as a commentable MDX review surface with diagrams, file maps, and an optional wireframe or prototype.
See Also
- artifact-plan-record — the direct contrast: seeds refuses a markdown plan outright (“No markdown plan documents anywhere in the artifact path”) and emits a schema-validated JSONL row instead, gaining enforceability and machine-consumption at the cost of a plan a human can read as prose.
- artifact-research-md — research feeding the plan.
- artifact-atomic-commit — what executing each task produces.
- artifact-design-md — OpenSpec’s design record that
tasks.mdis derived from.