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

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

momentum-lanes

Étoiles3

Forks1

Mis à jour6 juillet 2026 à 08:29

Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.

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

LiminaLabsAI

LiminaLabsAI/momentum

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	momentum-lanes
description	Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.

momentum-lanes

Use this skill when you detect concurrent workstreams or need to coordinate across branches. Key behaviors:

Lane binding: your phase is the phase bound to your branch (phase-N-shortname). specs/status.md is the cross-lane overview.
Lane-scoped tracking: write ONLY your own phase's artifacts (tasks.md, history.md, evidence/). Shared files (status.md, backlog.md, changelog/) are append / own-row-touch only.
Landing order: one lane at a time, suite green on updated main between landings, remaining lanes rebase.

When the user starts a second workstream or asks about what's in flight, read the lane board before proceeding.

When NOT to apply

Single-lane, single-branch sessions with no cross-lane coordination

References

Rule 15 in AGENTS.md — concurrent workstreams
/lanes command — board, queue, signal, land
specs/status.md — cross-lane overview

Plus depuis ce dépôt

même dépôt

start-phase

LiminaLabsAI/momentum

Begin a new implementation phase. Activates when the user invokes /start-phase or asks momentum to run the start-phase recipe.

2026-07-063

momentum-track

LiminaLabsAI/momentum

Record a new backlog item (bug, feature, tech debt, or enhancement) when you discover work that needs tracking. Activates when the session identifies unplanned work that should be tracked in the backlog.

2026-07-063

momentum-validate

LiminaLabsAI/momentum

Check spec structure health of the momentum project. Activates when the user runs `/validate`, asks for a health check, or when spec changes need verification before phase completion.

2026-07-063

agy-customizations

LiminaLabsAI/momentum

2026-07-053

swarm-supervisor

LiminaLabsAI/momentum

Drive a single repo through its phase as part of a swarm. Activates when spawned by the conductor (the user's primary session) with a spawn directive. State lives in files; the conductor reads board.json between turns. Loads on the swarm-supervisor invocation only — not invoked directly by the user.

2026-07-053

momentum-orient

LiminaLabsAI/momentum

Read specs/status.md before starting any work in a momentum-managed project. Activates at the start of every new task to ensure the agent has current phase context. Codifies Rule 1 (Orient First).

2026-07-033

name	momentum-lanes
description	Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.

momentum-lanes

Use this skill when you detect concurrent workstreams or need to coordinate across branches. Key behaviors:

Lane binding: your phase is the phase bound to your branch (phase-N-shortname). specs/status.md is the cross-lane overview.
Lane-scoped tracking: write ONLY your own phase's artifacts (tasks.md, history.md, evidence/). Shared files (status.md, backlog.md, changelog/) are append / own-row-touch only.
Landing order: one lane at a time, suite green on updated main between landings, remaining lanes rebase.

When the user starts a second workstream or asks about what's in flight, read the lane board before proceeding.

When NOT to apply

Single-lane, single-branch sessions with no cross-lane coordination

References

Rule 15 in AGENTS.md — concurrent workstreams
/lanes command — board, queue, signal, land
specs/status.md — cross-lane overview