Planning, sales, accounting, legal, and project management (4K skills)
Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.
Create a concise sales reference comparing your product with a specific competitor. Organize product and pricing differences, strengths on both sides, responses to common objections, and win/loss patterns into a Markdown document for use during sales conversations.
Turn a new feature into user stories: short descriptions of what people need and why. Each story includes a design reference and testable acceptance criteria, with scope intended to fit within one sprint.
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.
Map project stakeholders by their influence and interest, then create a communication plan for each group. Specify update frequency, channels, and key messages, while identifying competing interests and suggesting ways to align people across teams.
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.
Rewrite a feature-based roadmap around the changes customers and the business should experience. The result pairs each initiative with an outcome statement, success metrics, sequencing notes, and context connecting the plan to company strategy.
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.
Use customer research, surveys, and usage data to define an ideal customer profile: the customers most likely to gain value, stay, and expand. Summarize their characteristics, buying behavior, goals, needs, and fit criteria to guide sales and marketing priorities.
Estimate a product’s total, serviceable, and realistically obtainable markets using industry data and customer-level calculations. Produce market estimates, growth projections, source references, and explicit assumptions to support investment pitches or market entry decisions.
Turn survey responses, interviews, and other research data into three distinct user personas. Each profile explains the outcome users seek, their main difficulties, desired benefits, an unexpected behavioral insight, and how well the product meets their needs.
Examine feature ideas for existing products to uncover risky assumptions about customer value, usability, business support, and technical feasibility. Consider product, design, and engineering perspectives, then record potential failures, confidence levels, and suggested ways to test each assumption.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Generate improvement ideas grounded in the project or topic, critique every candidate, and rank the survivors with explanations. Produce a document that helps users choose which ideas deserve further exploration before defining requirements.