Menu
Manage explicitly requested OpenCaw goals as automated multi-task delivery flows with automatic per-task PR creation and required post-PR QA.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Plan original trading card game and card-battler visual direction for TCG/CCG card frames, card illustrations, board styling, tokens/minions, hand/deck/graveyard zones, VFX, and Hearthstone-like fantasy tabletop polish while keeping references IP-safe.
Plan and specify production-ready game art sheets, including environment tilesets, biome/terrain sets, autotile sets, prop atlases, and directional character animation sheets with 4, 6, 8, 16, or custom facing counts. Use when art roles need to create tilesets or sprite animation sets before implementation handoff.
Generate the host repository STYLE.md by composing one or more selected templates from ./.styles/.
Maintain, generate, or validate the host repository STYLE.md art contract from OpenCaw .styles templates. Use when visual work must preserve a project art direction, when a user asks to choose or change art styles, or when art roles need to verify that STYLE.md still references valid style templates.
Prepare game art assets for implementation handoff with style references, source/runtime file paths, atlas metadata, pivots, anchors, animation rows, collision assumptions, sorting layers, licensing, and validation checks. Use when art roles deliver assets to engineering, QA, game design, or documentation.
Review isometric and 2.5D game art for projection, tile metrics, anchors, elevation, depth sorting, occlusion, lighting, walkability, and gameplay readability. Use for isometric sprites, tiles, props, environments, VFX, maps, atlas handoffs, or style reviews.
| name | goal-flow |
| description | Manage explicitly requested OpenCaw goals as automated multi-task delivery flows with automatic per-task PR creation and required post-PR QA. |
Use when the user explicitly requests a goal, says goal flow, or a task planning artifact marks Goal Flow: enabled or Flow: goal.
Do not activate goal flow from the generic ## Goal section in a normal TASK.md. That section describes task intent; it is not the automated goal feature.
../.ai/goals/<goal_name>/GOAL.mdgoalGOAL_REPORT.md with ordered PR links, branch dependencies, QA evidence, and merge-conflict risk notes for human approval../commands/pr-readiness-check.sh --goal to create a durable readiness report that records the goal-flow exception../commands/create-goal-file.sh "<goal_name>" ["Goal Title"] [--dry-run] ./commands/create-goal-completion-report.sh "<goal_name|goal_dir|goal_file>" [--dry-run]