project-planner

Turn a vague feature request into a sprint-ready implementation plan by mapping affected backend and frontend modules, generating acceptance criteria, and outlining clear non-goals to align stakeholders.

The best way to break down Python and React features for backlog refinement is to split the request into distinct backend and frontend modules with clear responsibilities and estimate the effort for each.

Generate a module map and risk assessment for new feature work by analyzing the request to identify impacted Python and React modules, evaluate complexity, and highlight potential risks to guide planning.

Yes, you can use this for sprint planning to define measurable acceptance criteria and explicitly outline non-goals, ensuring the development team and stakeholders share a clear implementation boundary.

Yes, this planning approach works for both frontend and backend module mapping, specifically supporting Python and React projects to ensure full-stack coverage and clear responsibility assignment.

You should not use an automated feature planning skill for requirement breakdown if your project falls outside Python and React stacks, or if your feature lacks enough detail to map modules and assess risks.