northstar-roadmaplisted

# North-Star Roadmap (북극성 정렬 로드맵 + 기능 제안) Turn a vision document into a forward direction and a ranked feature backlog, then write it somewhere durable. The point is alignment, not idea generation: every proposal must trace upward to the north-star, and the result must outlive the conversation that produced it. ## When to use Reach for this skill when the user steps back from day-to-day work and asks where the project should head — typically with one of these (their actual phrasings): - "앞으로 어떤 방향으로 개선·발전시킬지 고민해봐" - "NORTH.md / NORTH_STAR 보고 나아갈 방향 + 기능 제안" - "(제안) 수용 → 계획 수립하고 메모리에 기록" - English: "what direction next", "propose a roadmap from the north star", "save the plan to memory" Do **not** use it to find what's broken right now. Detecting defects, gaps, or quality regressions is the job of the sibling skills below; this skill consumes their findings and points forward. ## Why these steps (the frameworks underneath) The workflow chains four established product-strategy methods so the output is defensible rather than vibes. Reason with each — don't just cite it: - **North Star Framework** (Amplitude) — a single North Star Metric is the destination; 3–5 directly-influenceable *Inputs* are the levers. You assess "current vs goal" against the inputs (leading indicators teams can move), not lagging vanity numbers. https://amplitude.com/books/north-star/about-north-star-framework - **Working Backwards / PR-FAQ** (Amazon) — for a major proposal, sketch the future