Gsp project state assessment
Skill mike007jd/game-superpowers/publish/clawhub/gsp-project-state-assessment
Use before major game work to classify the repo as greenfield, prelaunch, shipped, or live-risky.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-project-state-assessmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.5 KB, 285 tokens by cl100k_base, as published. Nobody here has run it
Game Project State Assessment
Goal
Determine what kind of project this is before choosing scope, architecture, or task sizing.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present project state assessment in conversation.
- minimal or full: write
docs/game-studio/project-state.mdusing./shared/templates/project-state-assessment.md.
Use:
./schemas/project-state.schema.json
What to inspect
Look for evidence such as:
- existing source tree size and maturity
- deployment configs
- CI / CD pipelines
- release notes / changelogs
- analytics / telemetry
- app store or distribution metadata
- save data, migrations, versioning, or liveops systems
- production environment files or operational runbooks
- existing user-facing docs or screenshots
Classification rules
- greenfield: empty repo, tiny scaffold, or explicit from-scratch instruction
- existing prototype / prelaunch: meaningful code exists, but little evidence of live-product operational risk
- shipped product: release / deployment / store / production signals exist
- live-risky: shipped product plus clear signals of live users, data compatibility, or operational constraints
Unknowns
If critical status cannot be inferred, ask only a few decisive questions. Do not ask long interviews.
What ships with it: 7 files
6.4 KB alongside SKILL.md
examples/
- usage.md649 B
schemas/
shared/
tests/
- smoke.md467 B
- CHANGELOG.md217 B
- MANIFEST.yaml2.2 KB
- README.md1.0 KB