Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

momentum-validate

Estrelas3

Forks1

Atualizado6 de julho de 2026 às 08:29

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

LiminaLabsAI

LiminaLabsAI/momentum

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	momentum-validate
description	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.

momentum-validate

When spec health validation is needed:

Read specs/status.md — verify required fields are present
Read specs/backlog/backlog.md — verify all 4 section tables
For each phase directory under specs/phases/: verify all required files and frontmatter
Check .momentum/installed.json — verify schema and agent entries
Verify AGENTS.md or CLAUDE.md primary instruction file has the ## Project Extensions marker
Report all failures found

This skill supports the /validate command for deep spec structure checks. Use it proactively before /complete-phase to catch structural issues early.

When NOT to apply

During active implementation work (validation should not interrupt flow)
When the user explicitly asks for no validation

References

/validate command — run health checks
specs/status.md — project status
Rule 9 in AGENTS.md — doc sync protocol

Mais deste repositório

mesmo repositório

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-lanes

LiminaLabsAI/momentum

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.

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

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-validate
description	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.

momentum-validate

When spec health validation is needed:

Read specs/status.md — verify required fields are present
Read specs/backlog/backlog.md — verify all 4 section tables
For each phase directory under specs/phases/: verify all required files and frontmatter
Check .momentum/installed.json — verify schema and agent entries
Verify AGENTS.md or CLAUDE.md primary instruction file has the ## Project Extensions marker
Report all failures found

This skill supports the /validate command for deep spec structure checks. Use it proactively before /complete-phase to catch structural issues early.

When NOT to apply

During active implementation work (validation should not interrupt flow)
When the user explicitly asks for no validation

References

/validate command — run health checks
specs/status.md — project status
Rule 9 in AGENTS.md — doc sync protocol