writing-plans

To convert software requirements into an actionable task plan, provide your feature description and acceptance criteria to generate a structured, bite-sized implementation plan with explicit file paths, tests, and commit guidance.

The best way to plan multi-step features for subagents is to generate a task-level implementation plan that includes exact file paths, code skeletons, and complete tests, ensuring clear task ownership and explicit acceptance criteria.

Yes, you can generate exact file paths, complete code skeletons, and documentation scaffolding directly from your project specs by creating a structured, task-level implementation plan.

You create a ready-to-commit workflow for new team members by converting project requirements into a structured plan with bite-sized tasks, explicit acceptance criteria, and complete test scaffolding.

Yes, this task planning approach works for both multi-step software features and design tasks, converting project requirements into a structured, task-level implementation plan with explicit acceptance criteria.

You need a task-level implementation plan for software development when delegating work to subagents, design reviewers, or new team members to ensure explicit acceptance criteria and exact file paths are defined.