비즈니스 스킬

Explore features for a new product through product management, design, and engineering perspectives. Generate five ideas from each viewpoint, then select five priorities with reasoning and assumptions to test before developing the concept further.

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

• Exploring features for a startup idea
• Comparing ideas from three professional perspectives
• Choosing five ideas to validate first

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

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

• Grouping customer requests into themes
• Selecting the top three requests for product goals
• Considering alternatives to requested features

Turn product or feature ideas into a concise product requirements document that helps teams decide what to build first. Connect target customers, customer value, success measures, and release scope, or review an existing document for gaps.

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

• Drafting requirements for a new product or feature
• Agreeing on the scope of a first release
• Reviewing an existing product requirements document

Break a feature into job stories that describe the user's situation, motivation, and desired outcome. Add six to eight observable acceptance criteria per story, defining how success will be checked, and include links to designs or prototypes.

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

• Breaking a new feature into job stories
• Writing backlog items around user situations
• Defining acceptance criteria for desired outcomes

Draft three alternative sets of team OKRs, pairing a qualitative goal with three measurable results. Use company strategy and team context to propose numerical targets, explain each option, and support discussions about quarterly priorities and customer or business outcomes.

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

• Drafting quarterly team goals
• Aligning team priorities with company strategy
• Turning broad objectives into measurable results

Review a product plan by imagining a failed launch and tracing possible causes. Separate real risks, overblown concerns, and unspoken worries, then define mitigation actions, owners, and deadlines for issues that must be resolved before launch.

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

• Checking launch plans for possible failure causes
• Separating real risks from overblown concerns
• Surfacing assumptions the team has not discussed

Identify three to five distinct customer groups for a product. Describe their characteristics, goals, problems, and existing alternatives, then assess product fit, market potential, and competition to help compare target audiences and explore opportunities.

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

• Exploring potential customer groups for a product
• Comparing audiences to prioritize
• Assessing opportunities in a new market

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

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

• Choosing the first customer segment for a new product
• Focusing limited resources on a launch market
• Comparing segments using interviews and customer feedback

Identify untested assumptions behind a new product idea across eight areas, including customer value, usability, business viability, technology, ethics, market launch, strategy, and team. Rate confidence in each assumption and suggest a test, producing a Markdown analysis.

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

• Checking assumptions behind a new product concept
• Reviewing launch channels and messaging assumptions
• Examining technical and team risks together

Choose one North Star Metric, a central measure of customer value, and three to five supporting measures that influence it. Classify the business by how customers use it and assess the proposed metric against seven criteria.

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

• Choosing a central measure of customer value
• Organizing the metrics a team tracks
• Comparing candidates for a North Star Metric

Turn feature ideas into backlog items, a team's planned units of work, using Why, What, and Acceptance Criteria. Connect each item to business goals and define observable outcomes in independent pieces sized for one sprint.

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

• Breaking a feature into independent work items
• Explaining the business purpose behind development work
• Writing observable acceptance criteria

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

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

• Testing demand before building a new product
• Planning landing page or waitlist experiments
• Checking willingness to pay through pre-orders

Read sprint plans and work records to summarize completion, remaining time, blocked tasks, and emerging risks. Compare progress with elapsed time, flag stale work, and provide a concise status report with at most one recommended action.

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

• Get a quick snapshot of the current sprint
• Spot stalled work and blockers
• Check whether required work is at risk

Create or update a sprint plan, a short development work plan, using existing work items, completed work, and available capacity. Organize priorities, carryover, dependencies, and risks, and produce a progress report.

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

• Plan the next sprint around available capacity
• Re-estimate unfinished work carried into the next sprint
• Update task priorities and estimates

Plan a game season or limited-time event across content, story, rewards, pricing, measurement, and player communication. Coordinate role-based agents to produce a season design, analytics plan, and communication calendar for production.

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

• Plan a game season or limited-time event
• Design reward tracks and seasonal currency pricing
• Define success metrics and A/B tests

Compare a feature, sprint, or milestone with its original plan to identify scope creep, meaning unplanned growth in work. Quantify additions and removals, assess delivery risks, and recommend what to cut, defer, or keep.

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

• Checking whether a feature has grown beyond its plan
• Measuring scope changes during a sprint
• Choosing additions to cut or defer

Review a sprint or milestone by comparing planned work with actual results. Summarize completion, estimation gaps, and blockers, then produce a retrospective with specific improvement actions, owners, and deadlines for the next iteration.

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

• Reviewing completed work at the end of a sprint
• Investigating estimation gaps and carried-over tasks
• Checking progress on previous improvement actions

Estimate development effort using affected code, design documents, dependencies, and past sprint results. Get optimistic, expected, and pessimistic day estimates, along with a confidence level, key risks, and a suggested breakdown into smaller tasks.

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

• Estimating effort before starting a feature
• Planning changes that span several systems
• Assessing uncertainty when sprint history is missing

Check whether a game project is ready for its next development phase. Review required documents, test evidence, and quality criteria, then receive a readiness verdict with blockers, missing materials, and any checks that could not be completed.

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

• Checking readiness to begin production
• Reviewing missing materials before release
• Assessing a phase transition against project quality settings

Turn game design and architecture documents into epics, bounded groups of development work for individual modules. Produce scope documents and an index, showing which requirements have recorded design decisions and where guidance is missing.

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

• Turning game designs into module-level development scope
• Planning epics for a specific development layer
• Finding requirements without architecture decisions

Build a game launch checklist covering code, content, quality, stores, legal preparation, infrastructure, marketing, and operations. Tailor checks to the project's stage and release requirements, then summarize blockers, accepted risks, missing confirmations, and required sign-offs.

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

• Reviewing launch readiness across departments
• Preparing checks for itch.io, Steam, or console releases
• Separating launch blockers from unassessed items

Review a development milestone using sprint reports, feature status, bugs, and risks. Summarize completion, quality, and delivery pace, then recommend whether to proceed, proceed with conditions, or stop, with scope choices and action items.

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

• Reviewing progress before a milestone deadline
• Identifying blockers and quality risks
• Choosing features to protect or defer

Create or update STRATEGY.md through guided questions about a product’s purpose, users, success metrics, and investment areas. Capture a shared basis for product decisions, with draft review and focused updates to existing documents.

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

• Define product strategy at launch
• Review strategy after a change in direction
• Clarify target users and success metrics

Develop independent solutions to a defined problem, compare them against shared requirements, and combine useful contributions into a coherent recommendation. An independent assessment and evidence checks support the selection, while unresolved tradeoffs and verification needs remain explicit.

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

• Comparing concrete solutions to a defined problem
• Developing rough options before choosing an approach
• Comparing architectural or product proposals