Roadmap Planner FAQs

Question 1

How does the Roadmap Planner handle vague strategic goals?

Accepted Answer

The skill uses a structured Phase 1 analysis to identify strategic pillars and OKRs, and is programmed to ask targeted clarifying questions if the source material is too ambiguous to decompose effectively.

Question 2

How does the skill prioritize different tasks?

Accepted Answer

It utilizes the MoSCoW framework (Must have, Should have, Could have, Won't have) to ruthlessly prioritize deliverables based on their alignment with the core strategic objective.

Question 3

Are the acceptance criteria suitable for non-technical stakeholders?

Accepted Answer

Yes, the skill specifically enforces a plain-language 'Given-When-Then' format that avoids technical jargon, making it easy for business owners to verify that requirements have been met.

Question 4

Does this skill help with project timeline estimation?

Accepted Answer

While it doesn't provide calendar dates, it uses a T-shirt sizing guide (S, M, L, XL) and identifies the critical path to help teams understand the minimum duration and complexity of the project.

Question 5

What is the format of the generated planning documents?

Accepted Answer

All plans are saved as standardized Markdown files in the `docs/roadmaps/` directory, featuring executive summaries, dependency tables, and detailed deliverable breakdowns.

Roadmap Planner

主な機能

ユースケース

Roadmap Planner

主な機能

ユースケース