steering

To create steering documents for project planning, generate discipline-wide files like requirements.md, design.md, and tasklist.md within a steering folder to formalize plans and track progress. This reduces ambiguity by capturing work details in structured text.

The best way to track task progress in markdown files is maintaining a tasklist.md updated in real time to reflect completion status. This ensures disciplined implementation and provides a clear record of work completed across project phases.

Yes, you can use standard text editing for phase-based project reviews and retrospectives without external tooling. Compile and record retrospective insights directly into your steering documents at the end of each phase to inform future work.

No, you do not need external project management tools to use a steering workflow. The process requires no tooling beyond standard text editing and project docs, relying on generated steering files and tasklists to organize work.

Use steering files instead of other task tracking methods when your team needs to document requirements, design decisions, and task progress in a structured text format. This approach enforces completion before proceeding to validation and supports phase-based reviews.

Your tasklist needs to be updated in real time during implementation to ensure accurate progress tracking and enforce task completion before proceeding to validation. This discipline prevents missed steps and keeps steering documents aligned with actual work.