'roadmap' 검색 결과

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).

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

Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).

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

지역 식품 슈퍼마켓의 이익률 회복을 위해 문제 요인, 실행 과제의 우선순위, 실행 계획을 정리합니다. 차분한 색상의 HTML 슬라이드로 경영 판단용 자료를 만듭니다.

• 식품 슈퍼마켓의 이익률 회복 방안을 제안합니다
• 운영위원회에 실행 과제의 우선순위를 설명합니다
• 따뜻한 색감의 자문 및 제안 자료를 만듭니다

기존 보험사의 디지털 전환 계획을 현황 진단, 과제 순서, 실행 체계까지 정리한 HTML 슬라이드로 만듭니다. 경영진의 의사결정을 위한 자료 작성에 활용합니다.

• 보험사의 디지털 전환 계획을 제안합니다
• 과제 우선순위와 실행 순서를 설명합니다
• 경영진의 의사결정 자료를 만듭니다

Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.

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

• Consolidating bug reports that share a root cause
• Turning an issue backlog into a repair roadmap
• Routing new bugs into existing plans

Prioritize product features, analyze customer interviews, and draft product requirements documents. Scoring scripts and document templates help turn customer problems, expected impact, and development effort into a roadmap with clear scope and success measures.

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

• Prioritizing features within team capacity
• Extracting customer problems from interviews
• Drafting requirements for a new feature

Turn interview notes, survey responses, and customer feedback into findings supported by evidence. Group recurring themes, assess frequency and impact, and produce prioritized recommendations to guide product improvements and future research.

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

• Finding shared issues across user interviews
• Organizing themes in open-ended survey responses
• Prioritizing improvements from support tickets

Turn feature requests and customer interviews into product plans. Rank features with RICE, a scoring method for reach, impact, confidence, and effort, extract research findings, and draft requirements and roadmaps that reflect team capacity.

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

• Ranking feature requests within team capacity
• Finding shared pain points across customer interviews
• Drafting product requirements with success metrics

Compare competing products using pricing pages, reviews, hiring information, and other market signals. Produce evidence-backed scores across 12 dimensions, pricing and usability analyses, and a prioritized action plan with a presentation outline for stakeholders.

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

• Comparing competitors before a product strategy meeting
• Assessing a competitor’s new feature or pricing change
• Preparing competitor comparison material for a sales pitch

Build a product launch strategy from product and market research. Define marketing channels, audience messages, measurable goals, and launch milestones, then organize them into a practical 90-day roadmap with risks and decision points.

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

• Planning a new product launch
• Preparing to enter a new market
• Choosing marketing channels and messages

Review a product requirements document, roadmap, or strategy by challenging the assumptions it depends on. Rank potential failures by impact, likelihood, and testing cost, then propose small tests, evidence to gather, and criteria for stopping or changing course.

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

• Challenging critical assumptions before starting a plan
• Preparing a strategy document for executive review
• Choosing low-cost tests to run this week

Compare five growth loops, mechanisms where user activity brings in more users, to find a suitable approach for a product. Develop an implementation roadmap, measurement plan, and growth estimates based on sharing, collaboration, content, or referrals.

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

• Designing product features that attract new users
• Planning growth with less reliance on paid acquisition
• Comparing sharing, collaboration, and referral mechanisms

Turn a vague research direction into a focused proposal and a detailed experiment roadmap. This workflow connects method refinement with validation planning, producing review records, an experiment tracker, and a summary of what to run next.

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

• Turn a rough research idea into a focused proposal
• Plan experiments that test the paper's claims
• Organize experiment order, budget, and decision points

Plan smart contract audits using research from security organizations. Combine threat modeling, static code analysis, fuzzing that varies test inputs, and manual review, while using attack patterns and a four-phase roadmap to guide further learning.

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

• Planning a smart contract security audit
• Setting up Echidna or Medusa fuzzing
• Reviewing attack patterns and past audit findings

Prepare an AI-SPEC.md design agreement for an AI development phase. The skill coordinates framework selection, documentation and domain research, and evaluation planning so the phase has a defined technical direction and assessment strategy.

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

• Define the design agreement for an AI development phase
• Research frameworks, documentation, and the application domain
• Plan how to evaluate an AI system

Prepare an existing codebase for GSD planning by mapping its structure, ingesting documentation, and initializing project records. The workflow creates or confirms planning files and produces an onboarding summary with findings and the next command to run.

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

• Preparing an existing project for GSD
• Organizing code findings and existing documentation
• Setting up requirements and a roadmap before implementation

Prioritize feature requests, analyze customer interviews, and draft product requirements documents. Use RICE scoring—a method weighing reach, impact, confidence, and effort—alongside templates and team capacity planning to turn findings into a quarterly roadmap.

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

• Rank feature requests using RICE scores
• Extract customer problems and themes from interviews
• Draft a product requirements document from a template

Assesses smart contract and blockchain codebases against Trail of Bits’ nine-category maturity framework. Produces evidence-backed ratings covering areas such as arithmetic, access controls, documentation, and testing, plus a prioritized improvement roadmap with effort estimates.

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

• Assessing the maturity of a smart contract project
• Identifying gaps in tests and documentation
• Reviewing access controls and operational practices together

Plan competitive and market research across public news, financial records, statistics, patents, hiring, and operational signals. Separate observations from inferences and cross-check independent evidence to support market sizing, roadmap choices, pricing, and sales materials.

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

• Cross-check signs of a competitor's planned market entry
• Find evidence for market size estimates
• Choose sources for a competitive research plan

Design, review, and implement Gantt charts for project schedules. Assess source data, task dependencies, and resource needs, then define suitable views, editing behavior, rendering tools, accessibility, exports, and tests—or recommend a clearer alternative.

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

• Choose between a Gantt chart, Kanban board, or timeline
• Map project-management exports into schedule data
• Review dependencies, critical path, and baseline variance

Design and review how a system is divided into modules, cohesive parts with clear responsibilities. Evaluate data ownership, communication rules, dependencies, and failure handling, and decide when to split or merge parts without assuming a particular technology.

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

• Define responsibilities and boundaries for a new module
• Review dependencies between system modules
• Clarify data ownership and communication rules

Turn ordered steps into a vertical or horizontal timeline whose progress line and active step update as readers scroll. Keep the sequence readable across screen sizes, with keyboard navigation and support for reduced-motion preferences.

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

• Present onboarding or service steps as a scroll timeline
• Show a roadmap or history with visible progress
• Adapt a timeline for small screens

Review Chinese and English academic papers in LaTeX, Typst, or PDF. Get findings tied to specific passages, a prioritized revision roadmap, submission readiness decisions, and comparisons with earlier reviews after revision.

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

• Reviewing a manuscript before submission
• Checking whether submission blockers remain
• Prioritizing methodological and logical revisions

Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.

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