A launch execution skill aimed not at "making one more game" but at "making one more game memorable."
When to Apply
- When the user wants game idea review + implementation + launch automation
- When the existing automated game pipeline is only at the level of a simple generator and quality promotion is needed
- When converting the daily game cron into an actual launch circle
Core Goals
Once a day, perform the following to the end .
- Idea review
- Design 5 wow factors
- Write spec/test cases
- Implementation
- QA
- Launch
The completion criterion is not "idea generation" but reflecting the actual deployment path + securing verification evidence다.
Input Priority
specs/game-idea-backlog.mdspecs/daily-game-lv4.mdspecs/game-production-pipeline.mdMEMORY.md's game constraints/prohibition rules- Existing
eastsea-blog/games/와eastsea-blog/games/games-list.json
Absolute Rules
- No rhythm games
#0a0a1aNo neon darkneon-No prefix- No simple "click + wave / click + idle / click + card"
- No more than 90% mechanic overlap with existing games
- If possible,
eastsea-blog/games/use as the launch source - git은
eastsea-blog/perform only in - No reporting before completion
5 Wow Factors Mandatory
For every game, explicitly designthe 5 items below, and implement at least 3 in the actual play loop.
- Input hook
- An input/judgment differentiator that makes you feel "this game's controls are different" within the first 10 seconds
- Escalation hook
- A rising structure where difficulty/rhythm/patterns come alive in the 30–90 second range
- Choice hook
- At least 1 meaningful choice during play (upgrade, branch, risk/reward)
- Showoff hook
- Moment staging that makes screenshots/GIFs/score bragging easy
- Retention hook
- A goal that gives a reason to retry (missions, ranks, daily variations, unlocks, etc.)
Wow Factor Evaluation Criteria
Write each item not as a one-line exclamation but in the format below.
## Wow Factors
1. 이름
- 왜 강한가:
- 실제 구현 표면:
- 리텐션/공유 효과:
Execution Phases
Phase 0 — Candidate Selection
specs/game-idea-backlog.mdIn🔍 검토중priority exploration- If none,
💡 신규or generate a new proposal based on genre rotation - Select 1 based on the criteria below
- Differentiation from existing games
- Feasibility of 1-day implementation
- Mobile controllability
- Showoff potential
- Monetization/expansion potential
- Record the selection result at the top of
specs/games/<slug>/spec.mdRecord at the top
Phase 1 — Spec Writing
Must include the following.
- One-line game definition
- Core mechanics
- Auxiliary systems
- Game loop
- 5 wow factors
- Prohibited rules review results
- Launch path
Phase 2 — Writing test cases
Include at least the following.
- Title screen
- Start → enter play
- Core mechanic response
- At least 3 TCs related to wow factors
- Game over/restart
- Mobile 390x844
- localStorage
- JS pageerror 0개
Phase 3 — Implementation
Principles:
- Implement in small slices
- At least 3 of the 5 wow factors reflected in actual code
- The remaining 2 reflected at least as UI/meta/launch hooks
- Game file is
eastsea-blog/games/<slug>/index.html - List reflection is
eastsea-blog/games/games-list.json
Phase 4 — QA
Required verification:
- File creation confirmed
- Game can be entered
- Controls work
- At least 3 wow factors confirmed to actually work
undefinedtext 0- JS pageerror 0
- Mobile viewport confirmed
- Score/result/restart confirmed
If possible, prioritize MiniPC/browser verification, but if not possible, leave traces of local static verification + smoke testing.
Phase 5 — Launch
Launching must do all of the following.
eastsea-blog/games/<slug>/index.htmlreflectedeastsea-blog/games/games-list.jsonreflected- Reinforce OG/description copy if needed
git -C /Users/kjaylee/.openclaw/workspace/eastsea-blog add ...git commitgit push
Even if the current worktree has unrelated dirty changes, commit only the relevant game path and list file with pathspec.
Subagent usage rules
If implementation gets long, you may use subagents. However, the spawn instructions must include the following.
- Current state
- Test/verification criteria
- Completion conditions
- Artifact path
Main closes only final verification and launch.
Status record
Leave the following file on every run.
.state/pipelines/game-wow-launch-YYYYMMDD.json
Required fields:
- job_id
- selected_slug
- selected_title
- wow_factors
- status
- test_commands
- completion_criteria
- artifacts
- launch_commit
- launch_url
- risks
Final report format
Keep the final report short, but it must include the following.
- Selected game
- Summary of the 5 added wow factors
- Number of wow factors actually implemented
- Verification results
- Launch path/commit
- Remaining risk in 1 line
Failure handling
If any of the following applies, stop/hold immediately.
- Overlap with existing games is too high
- Implementation complexity clearly exceeds the 1-day scope
- QA failure repeated 2 or more times
- Launch pathspec conflicts with dirty state
In this case, do not force a launch:
- Leave the spec/TC/reason for stopping
- Move on to the next candidate, or
- End that run as
보류.
Recommended cron prompt
Read and follow:
/Users/kjaylee/.openclaw/workspace/misskim-skills/skills/game-wow-launch-circle/SKILL.md
Today, run one full cycle only.
Do not stop at idea generation.
Do not report before launch verification.
Use eastsea-blog as the launch repo.