planning-with-files

Create persistent markdown plan files by structuring directories under plans/<plan-id>/ with requirements.md, plan.md, and tasks.md to capture goals, track progress, and store knowledge for multi-step workflows.

A plan-package structure organizes project workflows into a directory containing requirements.md, plan.md, tasks.md, and optional contract.json, providing durable records for planning, progress tracking, and machine-readable assurances.

Track decisions and changes across workflow phases using an evolution loop that supports preview, approve, and apply actions, ensuring per-item traceability and durable change records within markdown plan files.

Yes, markdown plan files are suitable for research planning and project management at scale, converting complex multi-step workflows into structured plans with requirements, tasks, and optional contract.json for machine-readable assurances.

Organize plan files centrally by storing plan packages under hello-scholar/plans/<plan-id>/ to consolidate research management, drafting requirements.md first to capture goals, constraints, and success criteria.

No, contract.json is optional for workflow traceability; the core plan-package structure relies on markdown files like requirements.md, plan.md, and tasks.md to provide per-item traceability and track decisions across phases.