477건 · 관련도순
[omh] Engineering leadership over roadmap and risk: roadmap, PM, technical tradeoffs, risk, delivery, release, and follow-up operating cadence. Use when the user says: cto-loop, cto loop, cto, cto pm, pm dev qa security ops, roadmap technical tradeoffs, technical tradeoff, delivery risk.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Roadmap parsing, analysis, and mutation operations for ROADMAP.md. Handles phase and milestone lifecycle including add, insert (decimal), remove, complete, and requirements coverage analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Roadmap-specific validation checks for architecture reviews. Load when reviewing roadmaps for implementation readiness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Roadmap concision rules, step decomposition efficiency, AC abstraction guidelines, and step-to-scenario mapping. Load when creating implementation roadmaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prioritize outcome-based product roadmaps, manage capacity and displaced work trade-offs, sequence learning milestones, and maintain portfolio coherence without dual ledgers or fake ROI. (triggers: `product roadmap prioritization`, `product portfolio trade-off`)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
After the founder brief and the market research, turn them into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the user returns to every session to see where they are and the single next move. Use right after start-here, whenever the user doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides privacy program maturity assessment using the AICPA/CIPT Privacy Maturity Model with five levels: Ad Hoc, Repeating, Defined, Managed, and Optimized. Covers assessment methodology across ten privacy domains, scoring criteria, gap analysis, maturity roadmap generation, and benchmarking against industry peers. Keywords: privacy maturity, AICPA, maturity model, assessment, roadmap, benchmarking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides conversion of gap analysis findings into phased implementation plans with milestones and risk-based prioritisation. Activate when building compliance programmes or allocating privacy budgets. Keywords: remediation roadmap, implementation plan, phased approach, prioritisation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master prioritization frameworks, roadmap planning, timeline estimation, and resource allocation. Create executable roadmaps that drive focus and alignment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build product roadmaps with quarterly planning, feature prioritization, dependency mapping, and stakeholder alignment. Create actionable roadmaps that communicate strategy and guide execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates and manages project roadmaps with milestones and PRD queues. Use after architecture is defined for project planning. Triggers on: create roadmap, plan milestones, organize prds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read the feature roadmap, find the next unplanned phase, brainstorm it, and update the roadmap with the resulting document name
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints. Use when cto-architect needs to create actionable technical roadmaps from architecture designs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate runs one seat, a second on BLOCK, and runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate (one seat, a second on BLOCK) runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Close out a finished memex milestone slice by writing the handoff trail: update `docs/CONTINUE_HERE.md` §1 current-state and §3 next-slice, tick the `docs/ROADMAP.md` scoreboard (milestone header ✅ + version, `- [x]` items), confirm any new observation is logged (deferring to memex-observe), and propose the git tag plus a `MN Slice X:` commit subject. Use after you finish a milestone slice in the memex repo and before you commit/tag it, when handing the next slice to a fresh session, or whenever CONTINUE_HERE and ROADMAP have drifted behind what actually shipped.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Onderhoudt de inhoud van de roadmap op /roadmap — werkpakketten toevoegen, wijzigen, verplaatsen of verwijderen, onderzoeksvragen schrijven en aan een sectie van het position paper koppelen, en RFC's koppelen die het ontwerp beschrijven. Gebruik dit bij "voeg een werkpakket toe", "verplaats X naar de Hoe-fase", "zet er een onderzoeksvraag bij", of het bijwerken van fases, disciplines en swimlanes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Synthesize project documentation and codebase into comprehensive roadmap status, gaps analysis, and blockers. Use when assessing project health, identifying blockers, tracking progress, comparing plan vs reality, documenting risks, or planning next milestones. Triggers: "roadmap", "project status", "blockers", "risks", "progress", "next milestone", "gaps", "what's done".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update or milestone selection: outcome milestones, MVP scope, non-goals, risks, evidence gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when materialising a roadmap into a ticket bundle — 'turn this roadmap into tickets', 'materialise tickets', 'mach Tickets aus der Roadmap', 'emit tickets for this plan'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an approved PRD roadmap must go to GitHub — 'publicar o roadmap no GitHub', 'criar o project e as issues do PRD', 'publish PRD roadmap' — handing over to pwdev-github (Project from a template, issues, sub-issues, blocked-by). Do NOT use for a single issue with the whole PRD (prd-export).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.