climber-game-iteration

Maintains a backlog of 3-5 active climber-game tasks and queues the next one.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/muddyrain/valley-mas --skill climber-game-iteration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: climber-game-iteration
Source: https://github.com/muddyrain/valley-mas/tree/main/.codex/skills/climber-game-iteration
Command: npx skills add https://github.com/muddyrain/valley-mas --skill climber-game-iteration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill manages the sustained backlog and iteration cadence for the climber-game package, ensuring a clear boundary between core logic and mounting points.

Core Features & Use Cases

  • Maintains an active backlog of 3 to 5 tasks for climber-game, moving completed items out and queuing the next task.
  • Enforces strict scope: only the climber-game iteration workflow; excludes apps/web and apps/unity from this skill.
  • Provides a decoupled coordination reference to guide cross-team collaboration via references/CLIMBER-GAME-TASKS.md.

Quick Start

Maintain the climber backlog by ensuring 3 to 5 active tasks and selecting the next item.

Frequently Asked Questions about climber-game-iteration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a development backlog and control iteration cadence for a game package?▼

You can enforce iteration cadence by stabilizing the development process to maintain 3 to 5 active backlog tasks, automatically moving completed items out, and queuing the next task for the climber-game package.

What is the best way to decouple core game logic from web mounting points during task coordination?▼

The best way to decouple core game logic from web mount entries is by enforcing strict iteration boundaries that exclude apps/web and apps/unity tasks, relying on a decoupled coordination reference file for guidance.

How many active tasks should I keep in my iteration workflow for effective task management?▼

Effective iteration workflow management requires maintaining an active backlog of 3 to 5 tasks, moving completed tasks out, and queuing the next item to keep development cadence stable.

Does the climber-game iteration workflow support cross-team collaboration with apps/web and apps/unity tasks?▼

No, the climber-game iteration workflow explicitly excludes apps/web and apps/unity tasks to maintain clear boundaries, focusing solely on core climber-game workflow and tasks for iteration management.

When do I need a dedicated coordination reference for my game backlog management?▼

A dedicated coordination reference is needed when stabilizing the climber-game development process, specifically to decouple from the web mount entry and guide cross-team collaboration through a markdown tasks reference file.