genesis-orchestrator_skill

This skill helps orchestrate Next.js full-stack projects by converting intent into phased, verifiable, tokenized execution.

Python

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill cleanexpo/nodejs-starter-v1 --skill genesis-orchestrator

SKILL.md5.3 KB

Overview

This skill is an autonomous orchestration protocol for Next.js full-stack projects that converts natural language intent into phase-locked execution. It enforces a token economy to split work into verifiable phases, activates specialised sub-agents for focused tasks, and provides gated verification before advancing.

How this skill works

On activation the orchestrator runs a Discovery scan to classify the repo as Greenfield or Brownfield, indexes package and infra manifests, and computes a technical debt score when applicable. It then runs a Vision Board interview, locks a Blueprint, and executes work in sequential, committed Sections with verification gates (type-check, lint, tests, build) before advancing. Sub-agents are triggered by intent keywords to handle design, math, planning, or development concerns.

When to use it

Starting a new project or feature (build, create, implement)
Planning or locking architecture and project phases
Executing multi-phase development where verification is required
Breaking complex tasks into small, verifiable sections
On repository sync (git pull) to reassess project state

Best practices

Always follow SECTIONAL_EXECUTION: complete, verify, commit each section before proceeding
Answer Vision Board questions (outcome, user, constraints) before Blueprint lock
Run verification gates (type-check, lint, tests, build) after each phase
Use sub-agents for specialised tasks to keep responses focused and concise
Commit after each Section with a clear message to enable rollbacks

Example use cases

Onboarding a Greenfield Next.js repo: run Discovery, create Vision Board, generate phased plan
Adding a new feature: activate GENESIS_DEV, produce Sectioned implementation steps, verify each chunk
Refactoring a Brownfield app: calculate technical debt, plan incremental reductions, enforce tests at each gate
Design handoff: trigger TITAN_DESIGN for UI spec generation, then lock design into Section D for visual verification
Pre-release health check: run pnpm turbo verification commands and produce a PLAN_LOCKED status for deployment

FAQ

Sub-agents activate based on intent keywords: MATH_COUNCIL for optimisation, TITAN_DESIGN for UI, GENESIS_DEV for building features, BLUEPRINT_MODE for architecture, DISCOVERY_MODE for explanations.

How do I recover from a failed verification gate?

Follow the Rollback Protocol: git stash, checkout HEAD~1, analyse and fix, then git stash pop. Re-run the failing verification locally before resuming.