一键在 Manus 中运行任何 Skill

spectra-esl-hop

星标1

分支0

更新时间2026年7月4日 00:52

ESL lifecycle hop — when the cortex routes a non-trivial change to SPECTRA in an ESL-enabled project (tonberry MCP available), SPECTRA owns the proposed→specify hop: right-size, propose the change folder, emit the spec into it. Absent tonberry → produce the spec normally (ESL opt-in).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Rynaro

Rynaro/TabRelay

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

SPECTRA — ESL Lifecycle Hop

Use this skill in an ESL-enabled project (mcp__tonberry__* tools available) when the cortex routes a non-trivial change to you. You own the proposed → specify hop of the Eidolons Spec Lifecycle (ESL).

For the full lifecycle, stage definitions, and role bindings, see the nexus cortex methodology/cortex/esl-protocol.md.

Your hop

right_size — call mcp__tonberry__right_size. Provide your /12 complexity score, a files-touched estimate, and the trade-off rationale. Tonberry returns the tier. Trivial work routes to Kupo, not you; you take lite or full.
propose — call mcp__tonberry__propose --change_id <id> --maker vivi --checker <kupo|vigil> --has_code <bool>. This scaffolds .spectra/changes/<id>/change.json.
specify — run your normal S → P → E → C → T → R → A cycle and emit the spec into the change folder:
- lite → one-page spec.md (GIVEN / WHEN / THEN + acceptance_checks).
- full → spec.{md,yaml} (the standard dual-format SPECTRA spec).
compose_manifest — call mcp__tonberry__compose_manifest to set tier and acceptance_checks (ids referencing your GIVEN / WHEN / THEN) in change.json.
hand off to the implementer (Vivi at in_progress) with your normal ECL PROPOSE envelope (see skills/planning.md "ECL emission").

Invariants

maker(vivi) ≠ checker(kupo/vigil) — distinct roles, always.
Tonberry composes artifacts; you provide spec content + signals. You supply the /12 score, the spec text, and the acceptance-check ids; tonberry writes the change.json structure.
Graceful skip — if mcp__tonberry__* tools are unavailable, produce the spec normally via your standard cycle and never hard-fail. ESL is opt-in; SPECTRA is EIIS-standalone-conformant and works without tonberry.

SPECTRA — ESL Lifecycle Hop

同仓库更多 Skills

同仓库

spectra-planning

Rynaro/TabRelay

Decision-ready specifications via the SPECTRA cycle. Use for complex features (complexity ≥7/12), multi-component/service changes, ambiguous requirements needing structured decomposition, or any task where 'just start coding' would require significant rework. Produces a dual-format spec (Markdown + YAML/JSON), never code.

2026-07-041

spectra-verify-incoming

Rynaro/TabRelay

Load when reading any upstream artefact handed off to SPECTRA that carries a sibling .envelope.json. BLOCKING per ECL §6.2.2: the orchestrator MUST have verified the envelope's SHA-256 (eidolons verify-envelope --block / eidolons run --verify) and recorded a verify_pass before dispatch. If no verify_pass exists for the message_id, or a verify_fail is present, REFUSE to process the payload and hand back to the orchestrator. Symmetric receiver gate — every Eidolon enforces it identically.

2026-07-041

name	spectra-esl-hop
description	ESL lifecycle hop — when the cortex routes a non-trivial change to SPECTRA in an ESL-enabled project (tonberry MCP available), SPECTRA owns the proposed→specify hop: right-size, propose the change folder, emit the spec into it. Absent tonberry → produce the spec normally (ESL opt-in).
metadata	{"methodology":"SPECTRA"}

SPECTRA — ESL Lifecycle Hop

For the full lifecycle, stage definitions, and role bindings, see the nexus cortex methodology/cortex/esl-protocol.md.

Your hop

right_size — call mcp__tonberry__right_size. Provide your /12 complexity score, a files-touched estimate, and the trade-off rationale. Tonberry returns the tier. Trivial work routes to Kupo, not you; you take lite or full.
propose — call mcp__tonberry__propose --change_id <id> --maker vivi --checker <kupo|vigil> --has_code <bool>. This scaffolds .spectra/changes/<id>/change.json.
specify — run your normal S → P → E → C → T → R → A cycle and emit the spec into the change folder:
- lite → one-page spec.md (GIVEN / WHEN / THEN + acceptance_checks).
- full → spec.{md,yaml} (the standard dual-format SPECTRA spec).
compose_manifest — call mcp__tonberry__compose_manifest to set tier and acceptance_checks (ids referencing your GIVEN / WHEN / THEN) in change.json.
hand off to the implementer (Vivi at in_progress) with your normal ECL PROPOSE envelope (see skills/planning.md "ECL emission").

Invariants

maker(vivi) ≠ checker(kupo/vigil) — distinct roles, always.
Tonberry composes artifacts; you provide spec content + signals. You supply the /12 score, the spec text, and the acceptance-check ids; tonberry writes the change.json structure.
Graceful skip — if mcp__tonberry__* tools are unavailable, produce the spec normally via your standard cycle and never hard-fail. ESL is opt-in; SPECTRA is EIIS-standalone-conformant and works without tonberry.

SPECTRA — ESL Lifecycle Hop