Game Design Goal Framing

Turn a vague feature idea or design direction into a clear game design goal with purpose, scope, fit, success criteria, and constraints. Use when a feature s...

Security Scan

Instruction-only game-design framing skill that is internally consistent with its description and requests no credentials, installs, or external access.

Purpose & Capability

The name and description match the SKILL.md instructions: the skill refines vague feature ideas into goal statements. It declares no binaries, env vars, or unrelated requirements, so requested capabilities align with the stated purpose.

Instruction Scope

Runtime instructions are limited to asking clarifying questions and producing a structured goal/purpose/fit/success/constraints output. The only file referenced is the included references/family-conventions.md. The instructions do not require reading system files, environment variables, or contacting external endpoints.

Install Mechanism

No install spec or code files are present — instruction-only. This is the lowest-risk model: nothing is written to disk or downloaded during install.

Credentials

The skill requests no environment variables, credentials, or config paths. There is no disproportionate access requested relative to the simple design-framing purpose.

Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous invocation allowed (disable-model-invocation false). Autonomous invocation is the platform default and, given the skill's minimal scope and lack of credentials, presents no additional incoherence.

Assessment

This is a low-risk, instruction-only skill that does what its name says: help you turn fuzzy feature ideas into clear goals. Before installing, confirm you trust the skill source (unknown) and be mindful about feeding any confidential design documents into an agent that may invoke skills; if you prefer, disable autonomous invocation for the agent or review outputs manually. No credentials or external downloads are requested.

Define what the feature is actually for.

Use this skill to sharpen a game design idea into a clear goal statement. The aim is to prevent fuzzy concepts, circular design discussion, and features that exist without a real reason. Keep the framing practical and explicit.

Read references/family-conventions.md when you need the shared conventions for this GROW-derived skill family.

What to produce

Generate:

1. Goal statement - what the feature is meant to achieve
2. Purpose - why it should exist
3. Fit - how it connects to the rest of the game
4. Success criteria - player-facing and KPI-facing signals
5. Constraints - quality, scope, time, and resource limits

Process

1. Clarify purpose

Ask:

• what problem does this solve
• what player behavior should change
• what player need or business need it serves

2. Check game fit

Ask:

• how it connects to existing loops and systems
• what player expectations it should meet
• what it must not break or dilute

3. Define success

Use a SMART-style lens:

• Specific - clear feature vision
• Measurable - success signals or KPIs
• Attainable - feasible with current constraints
• Relevant - connected to strategy and player value
• Time-boxed - aligned to a release or milestone

4. Write the framed goal

Use a compact format such as:

Goal statement
We want to [player or business outcome] by introducing or changing [feature or system], measured by [signals], within [timeframe].

Response structure

Goal Statement

• ...

Purpose

• ...

Fit with the Game

• ...

Success Criteria

• ...

Constraints

• ...

Fast mode

• What is this feature for?
• How should it help the player or the game?
• What would success look like?
• What constraints matter most?

Working principle

A feature without a clear goal is just a vague wish wearing design clothes.