'roadmap' 검색 결과

Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.

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

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

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

Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.

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

Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.

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

Detect drift in .arkhe/roadmap/ context files and regenerate them from the current codebase state. Scaffolds context directory if missing. Use when user runs /roadmap:refresh, mentions "refresh context", "update context", "init roadmap", "stale context", or "scaffold roadmap".

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

Create or update a strategic project roadmap with major milestones. Generates .unikit/ROADMAP.md — a high-level checklist of project goals. Use when user says "roadmap", "project plan", "milestones", "what to build next", "strategic goals", or wants to see big-picture progress. Also use when the user asks to check which milestones are done or wants to plan the overall project direction.

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

Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.

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

Use when authoring or rewriting a roadmap in agents/roadmaps/ — phases, goal, acceptance criteria, council notes; fires even on 'write a plan for X' / 'draft a roadmap'.

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

Use when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).

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

Build a three slide quarterly review or roadmap presentation with a retro blue, orange, and cream palette. The self-contained HTML includes a cover, three priorities, a timeline, key performance indicators, keyboard navigation, and animated transitions.

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

• Presenting a quarterly review
• Sharing three priorities with a team
• Showing a roadmap alongside key performance indicators

Build a marketing plan matched to a company's budget, team, and stage. Organize acquisition, first use, retention, referrals, and revenue into a 90-day roadmap and 12-month outlook, with owners, metrics, and tools in Notion-ready Markdown.

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

• Build a marketing roadmap for founders or investors
• Turn audit findings into a prioritized action plan
• Combine scattered marketing work into one plan

Support product planning for Auri, a voice assistant combining Alexa and Claude. Covers product vision, the Vitoria Neural persona, AWS architecture, service tiers, a four-phase roadmap, market launch planning, success metrics, and competitive analysis.

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

• Reviewing Auri product requirements
• Organizing service tiers and the development roadmap
• Considering market launch plans and competitors

Structure a post-acquisition improvement plan linking revenue, cost, and operational initiatives to EBITDA, a profit measure. Produce a roadmap with 100-day priorities, performance targets, responsible owners, and an Excel model showing each initiative’s profit contribution.

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

• Planning the first 100 days after an acquisition
• Mapping growth and cost initiatives to profit targets
• Preparing a value creation roadmap for the board

Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.

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

• Justify security budgets with estimated financial losses
• Plan SOC 2 or ISO 27001 compliance work
• Prepare incident coordination and communication plans

Prepare a graded Claude Managed Agent for recurring schedules, event triggers, or on-demand use. Validate timing, build deployment request data, optionally include self-evaluation for each run, and document the next steps in a roadmap.

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

• Schedule an agent to run every morning or weekly
• Prepare a curl trigger for an external event
• Add self-evaluation to each recurring run

Convert an existing GEO audit, a review of website readiness for AI search, into a client-ready PDF. Add a branded cover, color-coded scores, severity labels, and formatted sections for a 90-day roadmap.

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

• Turn an existing GEO audit into a client-ready PDF
• Present scores and findings with clear color coding
• Format a 90-day improvement roadmap for sharing

Set up a new project by gathering context, optionally researching the domain, defining requirements, and building a roadmap. It creates planning files that record the project’s background, workflow preferences, phased structure, and ongoing state.

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

• Clarify a new project idea through questions
• Define requirements and a phased roadmap
• Save project context and workflow preferences

Start a new development milestone for an existing project. The skill gathers goals, updates project documents, optionally researches new features, and creates scoped requirements and a phased roadmap for the next cycle of work.

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

• Planning the next release of an existing project
• Defining requirements for new features
• Updating goals and a phased roadmap

Build a starting roadmap for student legal research, including likely statutes, case law topics, background sources, and search terms. Review uploaded research for gaps, while clearly marking suggested citations as unverified leads that students must investigate themselves.

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

• Find a starting point for researching a legal issue
• Develop search queries for Westlaw or CourtListener
• Identify gaps in research already completed

Guide a team from product positioning and customer problem research to prioritized initiatives and a roadmap. Coordinate validation, stakeholder feedback, and execution planning so the team can connect its strategic direction to concrete work.

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

• Establishing direction for a backlog without a clear strategy
• Planning a new product or major initiative
• Revisiting target customers and product differentiation

Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.

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

• Planning a gradual replacement of a legacy system
• Comparing service separation and consolidation strategies
• Preparing a language or framework migration

Analyze a monolithic codebase before splitting it into modules or services. The skill inventories components, examines duplication, hierarchy, and dependencies, then proposes groupings aligned with business domains, with optional checks against business terminology and boundaries.

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

• Assessing component sizes before splitting a monolith
• Finding duplicated business logic across modules
• Reviewing module hierarchy and dependencies

Track multiple pull requests or merge requests across repositories with LoopX. Reconcile meaningful status changes, preserve requirement priorities and dependencies, and maintain a roadmap with one shared monitor for the whole delivery program.

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

• Inventory PRs and MRs across repositories
• Order pending work by requirements and dependencies
• Update completed and pending work in a roadmap

[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.

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