plan-writing

Breaking down multi-step project work involves splitting features or refactoring into small, focused tasks with independent verification criteria. This approach ensures every step is actionable and validated before moving forward.

Dependency-aware sequencing in task planning is organizing tasks based on their explicit relationships rather than rigid phases. It maps dependencies to ensure prerequisite work is completed before dependent tasks begin, producing a runnable plan.

You create a runnable plan for feature development by defining project-specific task granularity and mapping explicit dependencies. The plan is then saved as a dynamically named `{task-slug}.md` file in your project root.

Yes, you can use this task planning approach for both refactoring and new feature implementation. It is designed for any multi-step project that requires breaking down complex work into actionable, verifiable components.

The best way to store plan files is to save them directly at the project root using a simple naming convention. Files are dynamically named as `{task-slug}.md` to maintain organization and accessibility.