plan-w-team

To break a feature request into GitHub Issues with dependencies and acceptance criteria, provide a high-level prompt describing your objective. The system decomposes the request, conducts an interview to clarify requirements, and files linked issues to the GitHub Project board.

Multi-agent GitHub planning handles UI wireframing by coordinating a dedicated UI agent when interface design is needed. It generates wireframes alongside the structured issues, ensuring visual requirements are captured before filing the issues to the project board.

An epic dependency graph is a structured representation of issue relationships written to a YAML file. It is generated after decomposing high-level requests into GitHub Issues, mapping the dependencies between epics to enable continuous tracking by an epic manager.

Yes, a GitHub Project board is required to file the decomposed issues. The planning process creates GitHub Issues with labels, dependencies, and acceptance criteria, then files these issues directly to the project board for tracking.

Yes, you can use structured planning for bugs by describing the bug. The process decomposes the bug into GitHub Issues with appropriate labels, dependencies, and acceptance criteria, then files them to the project board and generates an epic dependency graph.

Automated GitHub issue decomposition relies on an interview process to clarify requirements, meaning incomplete or vague initial prompts may result in less accurate issues. It also requires manual epic tracking using the generated dependency graph file.