agentleFS
WhorideChickenWhorideChicken/first-playable/skills/scope/SKILL.md

scope

Skill3 starsChanged 32 days agoMITView on GitHub

Defines the First Playable — the smallest playable build that proves the core fun — including success/failure conditions, development order, and playtest hypotheses. Use after design review approval, or when the user says /first-playable:scope.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frames, develop and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sanmidableSkill

    frames

    Also in 3 projects that use this

  • hong9LeeSkill

    develop

    빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

    Also in 6 projects that use this

  • minhtran3124Skill

    visual

    Skill graph visualizer — scans all SKILL.md files in skills/, builds a directed relationship graph from explicit `relationships` frontmatter (falling back to content inference), and generates both a Mermaid markdown summary and an interactive HTML graph at .docs/skill-graph.html. Trigger: /visual

    Also in 3 projects that use this

  • MicrosoftSkill

    sync

    Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

    Also in 7 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • Skeln-ioSkill

    copy

    Direct response copywriting using proven frameworks. Brand-aware — reads ICP, voice, and tone from your brand config. Covers product descriptions, SEO meta, email, social, press angles.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only the UI/feedback needed to understand what is happening

    line 20
  2. Distinctive:

    If the user insists on including an excluded-by-default item, record it but flag it under Scope Risks.

    line 32
  3. Very specific:

    Write to Docs/Design/ (templates in this plugin's templates/design/):

    line 37

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

First Playable Scope

You are running Phase 3 of the FirstPlayable workflow. A First Playable is not the whole game — it is the minimum build in which the core fun can be directly played and judged. Prerequisite: Docs/Game/DESIGN_REVIEW.md is Approved. If it is not, stop and point the user to /first-playable:review-design.

Include (default yes)

  • Player input
  • Core movement or the core action
  • The minimum set of interaction targets
  • A success condition and a failure condition
  • Restart
  • Only the UI/feedback needed to understand what is happening

Exclude (default no — record under Excluded, don't argue each one)

  • Content unrelated to validating the core fun
  • Final art quality
  • Multiple maps or characters
  • Long-term progression systems
  • Shops and monetization
  • Live-ops features
  • Abstractions "for future expansion"

If the user insists on including an excluded-by-default item, record it but flag it under Scope Risks.

Output documents

Write to Docs/Design/ (templates in this plugin's templates/design/):

Docs/Design/
├─ FIRST_PLAYABLE.md        # core fun to validate, start/end state, in/out scope, success/failure/done conditions, manual checks
├─ DEVELOPMENT_ORDER.md     # ordered feature list: input → movement → camera → core action → targets → win/lose → restart
└─ PLAYTEST_HYPOTHESES.md   # falsifiable hypotheses (HYP-001 ...) about why this is fun

Hypothesis format

Each hypothesis must be falsifiable by watching someone play:

## HYP-001

### Hypothesis
The player enjoys controlling the direction and strength of physics-based pushes.

### How to validate
- Does the player retry after failing?
- Do they use a different strategy on the next attempt?
- Do they attribute the outcome to their own input?

### Failure signals
- The outcome feels random to them.
- They say luck matters more than control.
- They do not retry after the first failure.

Completion

Done when all three documents exist, every included feature traces to a rule ID in GAME_RULES.md, and at least one hypothesis exists. Then suggest /first-playable:bootstrap (requires an open Unity project).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.