一键在 Manus 中运行任何 Skill

reespec-archive

星标3

分支0

更新时间2026年3月23日 09:16

Archive a completed reespec request. Use when the user wants to finalize and archive a request after implementation is complete.

安装

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

在 Manus 中运行

来源

bnenu

bnenu/pi-file-watcher

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

下载

在 Manus 中运行

Steps

1. Select the request

Run reespec list to show active requests. Ask the user to confirm which one to archive if not specified.

2. Check task completion

Read reespec/requests/<name>/tasks.md.

Count - [ ] (incomplete) vs - [x] (complete).

If incomplete tasks exist:

Show warning: "N task(s) are not complete"
List the incomplete tasks
Ask the user: "Archive anyway? [y/N]"
Only proceed if user confirms

If all tasks complete: proceed without prompt.

3. Check artifact completeness

Run:

reespec status --request "<name>"

If any artifacts are missing or empty, warn the user. Do not block — inform and confirm.

4. Sync delta specs (if applicable)

Check reespec/requests/<name>/specs/ for capability specs.

If specs exist, compare with any corresponding specs in reespec/specs/<capability>/spec.md.

If updates are needed, ask: "Sync capability specs to main specs before archiving? [Y/n]"

Apply sync if confirmed.

5. Perform the archive

reespec archive --request "<name>"

This moves the request to reespec/requests/archive/YYYY-MM-DD-<name>.

6. Show summary

## Archived — <request-name>

Archived to: reespec/requests/archive/YYYY-MM-DD-<name>
Tasks:       M/M complete
Specs:       synced / not applicable / skipped
Artifacts:   brief ✓  design ✓  specs ✓  tasks ✓

<request-name> is now archived.

Guardrails

Always confirm request name — never auto-select without telling the user
Warn on incomplete tasks — don't block, but always inform
Date-stamp archive — YYYY-MM-DD prefix on archive folder
Show clear summary — what was archived, what state it was in
Don't lose data — archive is a move, not a delete

同仓库更多 Skills

同仓库

reespec-discover

bnenu/pi-file-watcher

Enter discover mode for a reespec request — a thinking partner that challenges the human to explore all sides of their intent before planning begins. Use when the user wants to explore an idea, start a new request, or deepen understanding of a problem.

2026-04-173

reespec-evaluate

bnenu/pi-file-watcher

Adversarial post-execute evaluator for reespec requests. Reads brief + specs as the contract, scans actual outputs, returns structured verdicts per capability with a triage summary, and appends the result to evaluations.md. Use after execute completes to verify implementation against the contract.

2026-04-173

reespec-execute

bnenu/pi-file-watcher

Implement tasks from a reespec request, one RED→GREEN cycle at a time. Use when the user wants to start or continue implementing a planned request.

2026-04-173

reespec-plan

bnenu/pi-file-watcher

Produce all planning artifacts for a reespec request — brief, design, specs, and tasks with explicit 3-step RED/GREEN checklists. Use when the user wants to plan a request, create a task list, or generate implementation artifacts after discovery.

2026-03-233

## Archived — <request-name> Archived to: reespec/requests/archive/YYYY-MM-DD-<name> Tasks: M/M complete Specs: synced / not applicable / skipped Artifacts: brief ✓ design ✓ specs ✓ tasks ✓ <request-name> is now archived.

name	reespec-archive
description	Archive a completed reespec request. Use when the user wants to finalize and archive a request after implementation is complete.
license	MIT
metadata	{"author":"reespec","version":"1.0"}

name	reespec-archive
description	Archive a completed reespec request. Use when the user wants to finalize and archive a request after implementation is complete.
license	MIT
metadata	{"author":"reespec","version":"1.0"}