'roadmap' 검색 결과

Scores backlog items with RICE/WSJF/Kano and files GitHub issues for top candidates. Use when triaging a roadmap or prioritizing features for a sprint.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when planning with fixed deadline or target outcome, working backward from future goal to present, defining milestones and dependencies, mapping critical path, identifying what must happen when, planning product launches with hard dates, multi-year strategic roadmaps, event planning, transformation initiatives, or when user mentions "backcast", "work backward from", "reverse planning", "we need to launch by", "target date is", or "what needs to happen to reach".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect and manage product feedback with Canny. Use when a user asks to set up a feature request board, prioritize product feedback, build a public roadmap, or let users vote on features.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in feature prioritization - the art and science of deciding what to build and in what order. Covers prioritization frameworks, roadmap planning, stakeholder management, and the trade-offs between different approaches. Knows that prioritization is about saying no, and how to make those decisions defensible. Use when "prioritization, roadmap, what to build, feature request, backlog, scope, trade-off, " mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in designing community strategies that align with business goals while creating genuine value for members. Covers community-market fit, positioning, culture design, governance models, and long-term roadmapping. Understands that great communities are intentionally designed, not accidentally grown. Use when "community strategy, build a community, community vision, community culture, community roadmap, community-market fit, why community, " mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prioritize roadmap initiatives with tradeoffs. Use when a senior developer needs help ranking projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides founder-PM discovery, roadmaps, prioritization, and PMF measurement. Use when planning product strategy, metrics, or roadmaps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product strategist — roadmaps, competitive analysis, OKRs, strategic narratives. Use when asked to "build a roadmap", "analyze competitors", "write a strategy memo", "prioritize features", or "set OKRs".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when exploring the CodyMaster skill ecosystem roadmap, marketplace, or distro validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CodyMaster ecosystem roadmap, marketplace, and distro validation reference.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic product leadership guidance for SaaS and technology companies. Covers product strategy, roadmap planning, product discovery, user research, growth product management, platform strategy, product analytics, and product launches. Use when defining product vision, prioritizing features, conducting discovery, analyzing metrics, or launching products. Use for "product strategy", "roadmap planning", "feature prioritization", "product discovery", "product metrics", "PRD writing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants to contribute a fix or roadmap item back to the Hedgehog project itself (skyf0xx/hedgehog) rather than their own project. Triggers on "let's fix that in Hedgehog", "I want to contribute", "let's pick up a roadmap item", or when `tweaker` offers this at the end of a build and the user says yes. Covers forking/branching, making the change under Hedgehog's own repo rules, committing with Conventional Commits, and opening the PR.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when keeping imp's docs and config examples coherent after a change - updating docs/internals/ARCHITECTURE.md / README / docs/GOAL.md / docs/MODELS.md / docs/ROADMAP.md / imp.conf.example / CHANGELOG / MISSION_JOURNAL, or "is this doc stale", "document this change", "the example config is out of date", "the README says X but the code does Y", "add a roadmap ledger row". Do NOT use for layer/frontmatter/lint questions (docs-layers), structural code audits (codebase-audit), measuring perf or refreshing the perf baseline (benchmark-cuda), or the agent's private memory (MEMORY.md).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Linear project management - issues, projects, cycles, and roadmaps. Use for Linear-related tasks like managing issues, tracking sprints, and organizing projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Customer feedback analysis — sentiment detection, NPS/CSAT frameworks, feature request clustering, support ticket triage, churn signal detection, and feedback-to-roadmap translation

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで役割を分けて進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Net-zero transition playbook: GHG inventory (ISO 14064-1, GHG Protocol Scope 1/2/3), science-based targets (SBTi), TCFD and ISSB S1/S2 climate disclosure, Taiwan carbon fee, decarbonization roadmap, internal carbon pricing, supply-chain carbon, product carbon footprint, green electricity and T-REC. Use for corporate decarbonization roadmap, carbon inventory, carbon-fee response, TCFD/ISSB reporting, supply-chain decarbonization, or responding to international customers (Apple, RE100). Triggers: 『碳盤查』『SBTi』『碳費』『TCFD』『淨零路徑』『範疇 3』『綠電』『CBAM』『ISO 14064』『ISSB』『T-REC』. For Taiwan EMBA ESG/sustainability/operations/strategy/finance cases. Focuses on Taiwan listed-company and supply-chain practice; sustainability strategy theory: use Asgard `grad-sustainability`; ERM 框架整合氣候風險: use `biz-erm`; 董事會 ESG 委員會結構設計: use `biz-corporate-governance`; 併購 ESG 盡職調查: use `fin-m-and-a`.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", "SEO roadmap", "keyword strategy", "content calendar", "site architecture plan", "SEO budget", or "SEO timeline".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit a roadmap or backlog to distinguish outcomes from outputs. Use when the user says "outcome vs output", "escaping the build trap", "are we building the right things", "roadmap review", "feature factory", "output-driven team", "we keep shipping but nothing changes", or wants to shift focus from shipping features to delivering value - even if they don't explicitly say "outcome vs output".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.