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

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

Commencer

spectr-apply

Étoiles3

Forks2

Mis à jour31 janvier 2026 à 18:59

Apply or accept a change proposal and implement its tasks

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

connerohnesorge

connerohnesorge/spectr

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	spectr-apply
description	Apply or accept a change proposal and implement its tasks

Change Proposal Application/Acceptance Process

Guardrails

Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
Keep changes tightly scoped to the requested outcome.
Refer to spectr/AGENTS.md and spectr/project.md (located inside the spectr/ directory—run ls spectr) for project and Spectr conventions or clarifications.

Steps

Track these steps as TODOs and complete them one by one.

Run spectr accept <id> to convert tasks.md to tasks.jsonc format for stable task tracking. Note: Both tasks.md (human-readable source) and tasks.jsonc (runtime source of truth) coexist after accept—update task statuses in tasks.jsonc.
Read spectr/changes/<id>/proposal.md, design.md (if present), and tasks.jsonc to confirm scope and acceptance criteria.
Work through tasks sequentially, keeping edits minimal and focused on the requested change. Update the task status in tasks.jsonc after verifying the work.
Confirm completion before updating statuses—make sure every item in tasks.jsonc is finished.
Verify/Update all task status in tasks.jsonc after all work is done. Tasks have status values: pending, in_progress, completed.
Read spectr/changes/ and spectr/specs/ directories when additional context is required.

Reference

Read spectr/changes/<id>/proposal.md for proposal details.
Read spectr/changes/<id>/specs/<capability>/spec.md for delta specs.

Plus depuis ce dépôt

même dépôt

spectr-proposal

connerohnesorge/spectr

Create a new change proposal with delta specs and tasks

2026-01-313

spectr-accept

connerohnesorge/spectr

Accept Spectr change proposals by converting tasks.md to tasks.jsonc without requiring the spectr binary. USE WHEN you're in a sandboxed or restricted execution context and spectr is not available in your path. DO NOT USE WHEN you need a lightweight alternative for task acceptance, but have the spectr binary available. DO NOT USE when you have the spectr binary available.

2026-01-313

spectr-accept-wo-spectr-bin

connerohnesorge/spectr

2026-01-313

spectr-next

connerohnesorge/spectr

Execute the next pending task from a change proposal

2026-01-313

name	spectr-apply
description	Apply or accept a change proposal and implement its tasks

Change Proposal Application/Acceptance Process

Guardrails

Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
Keep changes tightly scoped to the requested outcome.
Refer to spectr/AGENTS.md and spectr/project.md (located inside the spectr/ directory—run ls spectr) for project and Spectr conventions or clarifications.

Steps

Track these steps as TODOs and complete them one by one.

Run spectr accept <id> to convert tasks.md to tasks.jsonc format for stable task tracking. Note: Both tasks.md (human-readable source) and tasks.jsonc (runtime source of truth) coexist after accept—update task statuses in tasks.jsonc.
Read spectr/changes/<id>/proposal.md, design.md (if present), and tasks.jsonc to confirm scope and acceptance criteria.
Work through tasks sequentially, keeping edits minimal and focused on the requested change. Update the task status in tasks.jsonc after verifying the work.
Confirm completion before updating statuses—make sure every item in tasks.jsonc is finished.
Verify/Update all task status in tasks.jsonc after all work is done. Tasks have status values: pending, in_progress, completed.
Read spectr/changes/ and spectr/specs/ directories when additional context is required.

Reference

Read spectr/changes/<id>/proposal.md for proposal details.
Read spectr/changes/<id>/specs/<capability>/spec.md for delta specs.