Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

ito-archive

Sterne2

Forks0

Aktualisiert31. Mai 2026 um 15:03

Archive a completed change and update main specifications. Use when the user has finished implementing and wants to integrate the change into the main codebase.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

withakay

withakay/ito

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	ito-archive
description	Archive a completed change and update main specifications. Use when the user has finished implementing and wants to integrate the change into the main codebase.

Run the CLI-generated archive instructions for a specific change.

Rules

Do NOT archive without explicit user confirmation.

Steps

Determine the target change ID:
- If the user provided a change ID, use it.
- If no change ID was provided, run:
```
ito list --completed --json
```
  - Related filters (not for archiving, but useful for triage):
```
ito list --partial
ito list --pending
```
  - If no completed changes exist, inform the user: "No completed changes found. Run ito list to see all changes and their status."
  - If one or more completed changes exist, present them to the user and ask which one to archive.

Generate instructions (source of truth):

ito agent instruction archive --change "<change-id>"

Follow the printed instructions exactly.
After archive/spec sync succeeds, refresh relevant .ito/wiki/ topic pages when .ito/wiki/index.md exists. Prefer topic-page synthesis that links to the archived change, specs, modules, research, architecture notes, and documentation instead of creating one wiki page per archived change. If wiki coverage is absent, stale, or contradictory, note the risk and continue from raw Ito artifacts; wiki refresh is recommended follow-through, not an archive blocker.

Mehr aus diesem Repository

gleiches Repository

ito-lite-apply

withakay/ito

Implement Ito Lite markdown changes by reading proposal/spec/design/tasks artifacts and updating manual task statuses. Use when applying or executing a prompt-only Ito Lite change without the ito CLI.

2026-06-182

ito-lite-archive

withakay/ito

Archive completed Ito Lite changes by manually merging spec deltas into current specs and moving the change to archive. Use after implementation and verification when no ito CLI is available.

2026-06-182

ito-lite-proposal

withakay/ito

Create prompt-driven Ito Lite change proposal packages in markdown. Use for drafting proposal.md, spec deltas, optional design.md, and tasks.md without the ito CLI or validation executable.

2026-06-182

ito-lite-review

withakay/ito

Review Ito Lite markdown proposal packages before implementation. Use to check proposal.md, spec deltas, design.md, and tasks.md for consistency, risk, testability, and manual validation without the ito CLI.

2026-06-182

ito-lite-setup

withakay/ito

Initialize a markdown-only Ito Lite workspace with no executables. Use when setting up prompt-driven change proposals, creating .ito-lite/project.md, or preparing a repo for Ito-style specs, changes, and tasks without the ito CLI.

2026-06-182

ito-lite

withakay/ito

Coordinate the prompt-only Ito Lite workflow for proposals, specs, tasks, reviews, implementation, and archive without the ito executable. Use when the user asks for Ito-style planning, change proposals, lightweight specs, or markdown-only change management.

2026-06-182

name	ito-archive
description	Archive a completed change and update main specifications. Use when the user has finished implementing and wants to integrate the change into the main codebase.

Run the CLI-generated archive instructions for a specific change.

Rules

Do NOT archive without explicit user confirmation.

Steps

Determine the target change ID:
- If the user provided a change ID, use it.
- If no change ID was provided, run:
```
ito list --completed --json
```
  - Related filters (not for archiving, but useful for triage):
```
ito list --partial
ito list --pending
```
  - If no completed changes exist, inform the user: "No completed changes found. Run ito list to see all changes and their status."
  - If one or more completed changes exist, present them to the user and ask which one to archive.

Generate instructions (source of truth):

ito agent instruction archive --change "<change-id>"

Follow the printed instructions exactly.
After archive/spec sync succeeds, refresh relevant .ito/wiki/ topic pages when .ito/wiki/index.md exists. Prefer topic-page synthesis that links to the archived change, specs, modules, research, architecture notes, and documentation instead of creating one wiki page per archived change. If wiki coverage is absent, stale, or contradictory, note the risk and continue from raw Ito artifacts; wiki refresh is recommended follow-through, not an archive blocker.