'roadmap' 검색 결과

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

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

Evaluate and plan Amazon marketplace expansion across countries and regions. Use when a seller asks which Amazon marketplace to enter, how to compare international demand and economics, what tax, product-compliance, logistics, localization, account, or launch workstreams to investigate, or how to build a gated global-selling roadmap. Do not use as legal, tax, customs, or certification advice.

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

Issue 池全生命周期管理（开发范式 v1 规划段）。核心是一条 issue 驱动的流程：用户随手丢想法，你把糊的 issue 变成能开工的 task——产出的是“问题定义”，不是“解决方案实现”；载体就是仓库根的 ISSUES.md。五个动作：记、并、拆、转、pending。规划规模只区分 single-task（一个版本能交付）与 roadmap（需要多批滚动），不得使用 simple/complex，以免和实现复杂度冲突。

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

Build content strategies, editorial calendars, topic clusters, and content plans. Map content to buyer journey stages and plan distribution. Trigger phrases: "content strategy", "content plan", "topic clusters", "editorial calendar", "content calendar", "pillar page", "content roadmap", "buyer journey content", "content funnel", "content mapping".

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

Dispatches an expert reviewer agent to critique workflow artifacts. Use when a roadmap, implementation, or step needs quality review before proceeding.

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

[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking

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

Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.

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

Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.

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

Plan a rewrite as vertical slices and hand each one to /phx:plan as a requirements seed with binding decisions, contracts and acceptance criteria. Use after /rewrite:architect, or for the next slice.

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

中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU/MAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A/B Test、用户反馈、客服/销售反馈、竞品冲击、资源不足、项目延期、需求反复、老板临时插需求、跨部门协作、团队冲突、OKR/KPI、目标拆解、复盘等。触发时像资深互联网产品负责人一样，先判断真实问题、当前阶段、核心阻塞、关键约束、相关方和证据充分性，再给出最值得执行的下一步。默认中文回答，不讲理论、不引用原文、不解释历史、不暴露后台方法来源。

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

Builds a product strategy and stress-tests your moat, then writes a one-page strategy doc (diagnosis, where to play, how to win, guiding policy, coherent actions, moat verdicts). Use for 'we need a product strategy', 'is our moat real', 'do we have a competitive advantage', 'where should we play', 'defensibility', 'should we expand into X', 'our roadmap has no strategy', or 'write a product vision'. Draws on 909 insights from 236 Lenny's Podcast guests incl. Roger Martin, Richard Rumelt and Hamilton Helmer.

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

Assist with core product management activities including writing PRDs, analyzing features, synthesizing user research, planning roadmaps, and communicating product decisions. Use when you need help with PM documentation, analysis, or planning workflows that integrate with your codebase.

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

Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not enterprise documentation. Handles briefs, roadmaps, phase plans, and context handoffs.

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

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

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

Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs → roadmap → backlog), continuous discovery, backlog craft (epics, INVEST stories, acceptance criteria), prioritization frameworks (RICE, MoSCoW, Kano, WSJF), sprint delivery, metrics (North Star, AARRR), stakeholder management, and anti-patterns. The PO/PM owns what gets built, in what order, and why — including the end-to-end user flows and user journeys. Use when scoping a product or feature, decomposing an idea into outcomes/epics/stories, prioritizing a backlog, defining an MVP, mapping user journeys, measuring success, or saying no to a stakeholder. Pairs with super-ui-ux-design, which owns how each screen looks and behaves.

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

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

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

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

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

When the user needs to organize product initiatives into a prioritized, time-sequenced plan with outcomes and dependencies.

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

When the user needs to prepare for SOC 2, build a compliance roadmap, assess security posture, quantify security risk, or says "we need SOC 2", "security audit", "compliance", "enterprise customer wants SOC 2", "CISO advice".

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

Analyze spending patterns and find savings. 50/30/20 rule, subscription audit, debt payoff strategies, emergency fund roadmap.

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

Comprehensive audit of all construction data sources and systems. Map data flows, identify silos, assess quality, and create integration roadmap.

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

Go outside the founder brief and research the real market before the plan is written: the exact communities, newsletters, and venues where the user's ICP already sits, how comparable products launched and what worked, the problem in strangers' own words, and the rivals and openings the user never mentioned. Saves docs/gtm-cofounder/market-research.md with a link for every finding. Use right after start-here and before strategy-and-roadmap, before picking channels in first-50-users or planning launch-it, or whenever the plan feels like it only repeats what the user already said.

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

Refresh the user's competitive and market context. Re-scan named rivals and the category for what changed since the brief was written (rebrands, repositioning, new entrants, pricing shifts, renamed categories) and update docs/gtm-cofounder/founder-brief.md and the roadmap with anything that moves positioning. Use on a cadence, or whenever a competitor rebrands, a new tool appears, or the user senses the market has shifted under them.

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

Run developer customer discovery via a Technical Advisory Board (TAB). Use when the user has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.

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