Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Game Producer Specialist

    1

    Turn your game direction into a workable milestone, with explicit scope, dependencies, capacity assumptions and the next task your team can finish.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Game Producer Specialist

    Game Producer Specialist

    Example session with this skill installed

    Plan the next milestone for our offline garden puzzle game. Confirmed requirement: ten puzzles, undo/restart, readable solution feedback and a packaged desktop build. The first puzzle used 9 person-days including tool setup. Three later comparable puzzles used 2, 3 and 3 person-days for content authoring only. Six comparable puzzles remain. One designer is allocated 3 person-days per week; programmer availability, integration, revision, device checks and player sessions are unmeasured. The owner wants a launch in two weeks but has not authorized a scope cut. Show the calculation, dependency plan and concrete next task; do not pretend this is a committed launch schedule.

    • Read your context and instructions
    • Compiled the game producer specialist

    Illustrative preview: this representative editorial result is not a recorded runtime session.

    The content-only projection is 12–18 person-days for the six remaining comparable puzzles. At the supplied designer allocation, that is 4–6 weeks of content-authoring capacity. It excludes programming, integration, revision, device checks and player sessions. The requested two-week launch is not supported by this scope/capacity model, and no cut is authorized.

    Envelope
    task_id: GARDEN-MILESTONE-01
    artifact_id: GARDEN-PRODUCTION-PLAN / version: 1
    status: COMPLETE_LOCAL for planning; milestone date NEEDS_DECISION and NEEDS_EVIDENCE
    producer: Game Producer Specialist
    recipient: owner, designer, programmer and evidence collector when available
    objective: prepare an inspectable milestone plan around the confirmed ten-puzzle requirement
    scope: content and integration planning; no scope change or launch commitment
    inputs_and_sources: supplied effort records, allocation and required behavior
    confirmed_decisions: ten puzzles, undo/restart, solution feedback, desktop package
    recommendations_and_pending: representative integration milestone, programming capacity, proof/revision effort and actual launch decision
    criteria: locally proposed PROD-G1–G3 preserve the confirmed requirement
    next_action: owner resolves the scope/date conflict while the programmer measures one representative integration

    Capacity calculation
    Remaining content: 6 comparable puzzles × observed 2–3 person-days = 12–18 person-days.
    Designer allocation: 3 person-days/week, giving 12/3–18/3 = 4–6 weeks for that component only, assuming comparable complexity and uninterrupted allocation.
    Do not multiply the setup-heavy 9-day first puzzle as the routine rate. Do not add the programmer's unknown effort as zero. Two weeks provides 6 designer person-days, below even the 12-day content-only scenario. Actual elapsed delivery may be longer and cannot be derived by summing concurrent people's effort.

    Next milestone — integrated representative puzzle
    Purpose: expose the implementation/integration/proof path before projecting all ten.
    Player scope: one existing comparable puzzle with complete undo, restart, readable solution feedback and desktop export. This milestone is not a substitute for the ten-puzzle launch scope.
    Pipeline: approved puzzle data → runtime integration → undo/restart → feedback → identified export → target-device observations → review.
    Dependencies: settled puzzle-data/state contract; available programmer/engine environment; target-device and participant arrangements. Rights status of assets has not been supplied and must be recorded before distribution.
    Evidence: PROD-G1 undo restores the prior authoritative puzzle state; PROD-G2 restart restores the puzzle's initial state; PROD-G3 solution outcome is represented in the packaged build under the approved contract. Human interpretation of the feedback is a separate track.

    Prepared task PROD-G-INTEGRATE-01
    Proposed owner: programmer, not an actual assignment made here.
    Inputs: selected puzzle/data revision and confirmed undo/restart/feedback contract.
    Deliverable: integrated candidate with source/data/assets/settings identity and desktop run instructions.
    Acceptance/evidence: demonstrate PROD-G1–G3 in editor and target as separate records; record elapsed integration/revision time and blockers against the selected unit. Any missing behavior decision returns to its actual owner.
    Receiver: QA collector and reviewer; freeze candidate before collection.

    Scope/date options for the owner
    Retain ten puzzles and revise the date after actual integration/proof capacity is known. Add real capacity and reassess handoff/integration constraints rather than scaling a solo rate blindly. Alternatively approve a smaller complete game, explicitly losing breadth while retaining undo/restart/feedback and target proof; a count cannot be selected here without that authorization.

    The plan and next task are delivered. No production meeting, implementation, export, playtest or commitment occurred. The actual owner resolves the conflict; independent integration and capacity measurement can continue within authorization.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Give ambition a production path.

    Game Producer Specialist turns your game direction into bounded milestones and work your team can act on. Use it when content keeps expanding, a target date lacks a capacity model, or too many tasks start while integration and review wait.

    The method separates setup effort from repeatable production, maps the real dependencies and makes estimate assumptions visible. It includes the work that polished schedules often miss: integration, revision, asset delivery, target checks and waiting. When scope and date conflict, it compares concrete alternatives and explains their effect on the player promise.

    Your plan can include

    • A milestone with a clear purpose, player scope and completion criteria.
    • A dependency and ownership map, capacity calculation or planning scenarios.
    • A bounded next task and a targeted intervention for a production bottleneck.

    For example, plan the remaining puzzles after the first puzzle included expensive tool setup. The specialist can use comparable later units, calculate the content component and keep unmeasured programming or testing work visible before calling the date feasible.

    Provide the game direction, required scope, current inventory, actual capacity and any effort observations. The complete standalone method and reference are included. No particular planning service, Scrum process or staffed squad is required. You supply AI access; the usefulness of a forecast depends on your production data, and schedule or scope commitments remain yours to make.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean 16 days ago

    • Passed all security checks, Safe to install

    Listed16 days ago

    What's inside

    Frequently Asked Questions