ss-writing-plans

To turn a design spec into an implementation plan, generate a structured plan.md and a tasks.md file detailing required files, tests, and documentation. This process decomposes work into bite-sized tasks with explicit file paths, ensuring engineers execute design requirements systematically.

Cross-session tracking works by producing a persistent tasks.md file within a dedicated changes directory, enabling you to resume development where you left off across different conversations. This file survives session interruptions to maintain continuous progress tracking.

Yes, you can generate implementation plans for multi-subsystem features by creating structured plan and task files. The system organizes these artifacts in a changes/YYYY-MM-DD-<topic>/ directory, effectively scoping and isolating complex development workflows for multi-subsystem projects.

The best way to break down development work into bite-sized tasks is through guided decomposition, splitting features into 2-5 minute increments. Each task explicitly references required file paths, tests, and documentation to ensure disciplined and executable development steps.

Yes, you need to manually create the changes/YYYY-MM-DD-<topic> directory before running the plan generation. Once this directory exists, the system automatically outputs the corresponding plan.md and tasks.md files to structure your workflow artifacts.

Using a dedicated changes directory for implementation plans isolates repeatable workflows and scopes modifications effectively. By storing plan.md and tasks.md together under a dated topic folder, teams maintain organized, persistent artifacts for cross-session tracking and disciplined development.