project-manager

Project specifications are converted into structured task lists by producing atomic 30-60 minute tasks with clear acceptance criteria. This task breakdown includes dependency mapping, priority classifications, and suggested files to edit for sprint planning.

Creating a sprint-ready task list from user stories involves generating atomic 30-60 minute tasks with explicit estimates, dependency mapping, and acceptance criteria. This process sequences work for parallelization and assigns priority levels for backlog grooming.

Task breakdown can flag gaps in ambiguous product specifications by reading and quoting spec requirements verbatim. This specification analysis identifies missing details before converting the spec into executable development work and estimates.

This approach provides estimates and dependencies for sprint planning by mapping task dependencies, sequencing work for parallelization, and assigning priority levels. It translates user stories into a prioritized backlog for a two-week sprint.

A limitation of converting specs into 30-60 minute atomic tasks is that it deliberately avoids making technical implementation decisions. The output focuses strictly on scoping, estimates, and file suggestions, leaving code architecture choices to the developer.

You do not need a complete product spec to start, as the specification analysis flags gaps and ambiguous items verbatim. However, resolving these missing details is necessary to produce accurate estimates and clear acceptance criteria.