goal-planner

To turn vague ideas into well-scoped GitHub issues, describe your objective and the tool drafts a goal description, acceptance criteria, scope notes, and ready-to-file issues. This structured format ensures outcomes are testable and decomposed for incremental delivery.

The best way to separate product goals from feature tasks is to clarify the desired outcome first, then decompose it into linked features. This approach aligns teams on the result before filing work, ensuring goals remain distinct from the executable tasks needed to achieve them.

You manage dependencies and blocked_by relationships by defining scope notes and linking tasks during issue creation. This ensures safe, incremental delivery by mapping which features must be completed before others can proceed across your repositories.

Yes, you can use this for feature planning across multiple GitHub repositories. It applies to conversations about product direction and task filing across repositories, ensuring outcomes are testable, decomposed, and formatted consistently for filing.

Yes, this works for planning product direction from a rough idea of what to build next. It translates vague user ideas into clear, actionable goals and well-scoped GitHub issues, applying structured formatting to ensure the resulting tasks are ready for filing.