light-orchestrator
Coordinate and recover multi-stage Light research projects through the canonical .light/passport.yaml state, stages 1-13, resident overlays, checkpoints, findings, parallel joins, stale propagation, handoffs and user-authorized reroutes. Use for a new/resumed/partial/dirty/failed/stale/delivered research project; when the user says continue, resume, take over, checkpoint, reroute, recover or deliver; or when work crosses two or more Light research stages. Never turn frontend-design/system-design/patent-disclosure/software-copyright or overlays into stages, never execute a suggested back-edge w
npx skills add Light0305/Light-skills --skill light-orchestrator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Light orchestrator Coordinate, route and recover the research lifecycle. Do not impersonate the stage skills and do not turn a deterministic check into a research judgment. Read [`references/orchestrator-resource-map.md`](references/orchestrator-resource-map.md) before a real lifecycle run. It defines intake, state authority, migration, evidence states, access tiers, resident budget and handoff. Read [`references/integration-contract.json`](references/integration-contract.json) when changing any role, gate or route. The detailed rationale is [`../../docs/design/orchestrator-spec.md`](../../docs/design/orchestrator-spec.md). ## Non-negotiable boundaries 1. Never choose the research direction, final idea, plan, venue, back-edge, revision-budget exception, known-limitation conversion or final delivery for the user. Present a recommendation, evidence, alternatives and consequences, then stop. 2. `reroute.py` is advisory. Only `passport.py add-back-edge --authorization-id <user-record>` may write a real back-edge, and only after the user authorizes that exact route. 3. A back-edge must go to an earlier stage (`to < from`). The 2⊣3 data feasibility result is an `admission_hold`, not a
- Non-negotiable boundaries
- 1. Intake every project
- 2. Keep one canonical state
- 3. Route only the defined roles
- Pipeline nodes
- Resident overlays
- Off-DAG engineering and IP handoff
- 4. Run a real checkpoint
- 5. Suggest, stop, then reroute
- 6. Propagate freshness and recover
- 7. Resident injection
- 8. Delivery
- Completion check
python scripts/lifecycle.py intake --root <project-root> python scripts/passport.py migrate --file .light/passport.yaml inspect the dry-run and UNKNOWN legacy authorization python scripts/passport.py migrate --file .light/passport.yaml --write python scripts/execution_mode.py --input task-profile.json python scripts/decision_checkpoint.py --input decision.json python scripts/workflow_ledger.py --input templates/workflow-ledger.example.json python scripts/run_checkpoint.py \ python scripts/reroute.py \ python scripts/passport.py add-back-edge \
What does the light-orchestrator skill do?
Coordinate and recover multi-stage Light research projects through the canonical .light/passport.yaml state, stages 1-13, resident overlays, checkpoints, findings, parallel joins, stale propagation, handoffs and user-authorized reroutes. Use for a new/resumed/partial/dirty/failed/stale/delivered research project; when the user says continue, resume, take over, checkpoint, reroute, recover or deliver; or when work crosses two or more Light research stages. Never turn frontend-design/system-design/patent-disclosure/software-copyright or overlays into stages, never execute a suggested back-edge w
How do I install it?
Run `npx skills add Light0305/Light-skills --skill light-orchestrator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Light0305/Light-skills, a repository with 505 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.