Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

spec-driven-execution

Étoiles7

Forks1

Mis à jour1 juillet 2026 à 18:53

Orchestrate feature work in this MMO repo by dispatching Planner, Implementer, and Verifier sub-agents through the tlc-spec-driven pipeline. The orchestrator picks the ROADMAP phase, cleans env, sequences sub-agents, and handles PASS/FAIL — it does not plan, implement, or verify itself. Use for "build the next phase", "implement this feature", "advance the roadmap", "/loop".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

tech-leads-club

tech-leads-club/nj-mmo

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	spec-driven-execution
description	Orchestrate feature work in this MMO repo by dispatching Planner, Implementer, and Verifier sub-agents through the tlc-spec-driven pipeline. The orchestrator picks the ROADMAP phase, cleans env, sequences sub-agents, and handles PASS/FAIL — it does not plan, implement, or verify itself. Use for "build the next phase", "implement this feature", "advance the roadmap", "/loop".

Spec-Driven Execution

Driver only. All planning, task format, implementation rules, and validation live in tlc-spec-driven. This skill does not duplicate them.

What this repo adds

Delta	Meaning
Sub-agent roles	Planner → Implementer → Verifier, each a fresh Composer 2.5 sub-agent (`model: composer-2.5`). Orchestrator sequences them; never writes spec/code/tests.
Single Implementer	One sub-agent runs every task in `tasks.md`. Skip tlc's per-phase worker offer.
Auto-commit in flow	Implementer may commit per task without asking (only while this flow is active).
ROADMAP loop	Autonomous mode walks `.specs/ROADMAP.md` one unchecked phase at a time.

Orchestrator flow

Pick phase — .specs/ROADMAP.md (or loop payload); resume in-flight work from .specs/STATE.md ## Handoff if present.
Clean env — free ports 2567 and 4200 before gates.
Dispatch Planner sub-agent.
Dispatch Implementer sub-agent (only after Planner artifacts exist under .specs/features/<feature>/).
Dispatch Verifier sub-agent (always; orchestrator handles fix→re-verify ≤3 iterations per tlc).
On Verifier PASS — flip ROADMAP [x], update STATE.md Handoff, commit docs(spec): mark phase <N> complete in ROADMAP and STATE.

Sub-agent prompts

Sub-agents cannot see this chat. Each prompt is self-contained:

Activate tlc-spec-driven by name and follow it for the assigned role (Specify/Design/Tasks, Execute, or Validate). If the skill cannot be activated, STOP.
Feature context — ROADMAP phase title + goal, feature slug, output dir .specs/features/<feature>/, repo path /Users/wneto/Dev/nj.
Autonomous mode (loop / unattended) — resolve ambiguities as spec assumptions; no user confirmation gates.
Project glue (below) — repo inputs tlc does not know about.
Role footnotes only:

Implementer: paths to existing spec.md / design.md / tasks.md; authorized to commit per task; do not run Verifier.
Verifier: git diff/commit range for the feature; Implementer deviation summary if any.

Do not paste tlc templates, reference filenames, or quality rules into the prompt — the skill owns that.

Project glue

Append to every sub-agent prompt. Point at repo docs; do not restate their contents.

.specs/ROADMAP.md — phase scope and dependencies
.specs/STATE.md — ## Decisions (AD-NNN), ## Handoff
AGENTS.md — testing contract for this monorepo
L2J Classic reference (parse only, never depend): ~/Dev/L2J_Mobius/L2J_Mobius_Classic_1.0/dist/game/data/

Plus depuis ce dépôt

même dépôt

game-designer

tech-leads-club/nj-mmo

Build production-quality visual game assets for this Three.js + Colyseus MMO: rigged characters, monsters/mobs and NPCs (rigged GLTF + skeletal animation via the game-core animation state machine), equipped-weapon/bone attachments, combat and world VFX, UI/item icons, and environment props. Use when asked to create or add a character, monster, mob, creature or NPC; skin the player or remote players; replace a capsule; attach or show an equipped weapon; add a skill, hit, death, level-up, target-ring or other VFX; add skill or item icons for the hotbar/shop/inventory; replace primitive buildings/trees/rocks with props; import a model; or advance any visual-asset roadmap item (Phases 8+). After this file, read the matching recipe in references/: create-character, create-monster, create-attachment, create-vfx, create-icon, create-prop. Do NOT use for combat balance, server rules, XP/drop formulas, or non-visual gameplay logic (use spec-driven-execution / tlc-spec-driven instead).

2026-06-297

name	spec-driven-execution
description	Orchestrate feature work in this MMO repo by dispatching Planner, Implementer, and Verifier sub-agents through the tlc-spec-driven pipeline. The orchestrator picks the ROADMAP phase, cleans env, sequences sub-agents, and handles PASS/FAIL — it does not plan, implement, or verify itself. Use for "build the next phase", "implement this feature", "advance the roadmap", "/loop".

Spec-Driven Execution

Driver only. All planning, task format, implementation rules, and validation live in tlc-spec-driven. This skill does not duplicate them.

What this repo adds

Delta	Meaning
Sub-agent roles	Planner → Implementer → Verifier, each a fresh Composer 2.5 sub-agent (`model: composer-2.5`). Orchestrator sequences them; never writes spec/code/tests.
Single Implementer	One sub-agent runs every task in `tasks.md`. Skip tlc's per-phase worker offer.
Auto-commit in flow	Implementer may commit per task without asking (only while this flow is active).
ROADMAP loop	Autonomous mode walks `.specs/ROADMAP.md` one unchecked phase at a time.

Orchestrator flow

Pick phase — .specs/ROADMAP.md (or loop payload); resume in-flight work from .specs/STATE.md ## Handoff if present.
Clean env — free ports 2567 and 4200 before gates.
Dispatch Planner sub-agent.
Dispatch Implementer sub-agent (only after Planner artifacts exist under .specs/features/<feature>/).
Dispatch Verifier sub-agent (always; orchestrator handles fix→re-verify ≤3 iterations per tlc).
On Verifier PASS — flip ROADMAP [x], update STATE.md Handoff, commit docs(spec): mark phase <N> complete in ROADMAP and STATE.

Sub-agent prompts

Sub-agents cannot see this chat. Each prompt is self-contained:

Activate tlc-spec-driven by name and follow it for the assigned role (Specify/Design/Tasks, Execute, or Validate). If the skill cannot be activated, STOP.
Feature context — ROADMAP phase title + goal, feature slug, output dir .specs/features/<feature>/, repo path /Users/wneto/Dev/nj.
Autonomous mode (loop / unattended) — resolve ambiguities as spec assumptions; no user confirmation gates.
Project glue (below) — repo inputs tlc does not know about.
Role footnotes only:

Implementer: paths to existing spec.md / design.md / tasks.md; authorized to commit per task; do not run Verifier.
Verifier: git diff/commit range for the feature; Implementer deviation summary if any.

Do not paste tlc templates, reference filenames, or quality rules into the prompt — the skill owns that.

Project glue

Append to every sub-agent prompt. Point at repo docs; do not restate their contents.

.specs/ROADMAP.md — phase scope and dependencies
.specs/STATE.md — ## Decisions (AD-NNN), ## Handoff
AGENTS.md — testing contract for this monorepo
L2J Classic reference (parse only, never depend): ~/Dev/L2J_Mobius/L2J_Mobius_Classic_1.0/dist/game/data/