steering

To create steering documents for task-based project planning, you generate a date-stamped steering directory with template files like requirements.md, design.md, and tasklist.md. This skill automates that process from user directives to capture plans and progress reproducibly.

Progress logging and retrospective tracking for feature implementation is handled by maintaining a transparent record of plan versus execution. This skill provides a dedicated space for post-mortems and improvements within the generated steering files.

No specific dependencies are required to generate tasklists and planning templates. This skill operates independently using frontmatter-guided metadata, structured task tracking, and optional tooling to produce steering files.

Yes, you can use steering files for cross-team planning and validation across different phases. This skill applies to planning, implementing, and validating work, ensuring progress is captured and traceable throughout the workflow.

To start planning a new feature request using a tasklist workflow, you issue the directive and generate an initial steering plan. The skill creates a date-stamped directory with tailored template documents and an actionable tasklist to track implementation.

Automated steering file creation prevents the tedious and error-prone nature of manual task management documentation. It ensures plans, tasks, and progress are captured reproducibly through structured templates and explicit progress logs.