Menu
Archive a completed reespec request. Use when the user wants to finalize and archive a request after implementation is complete.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
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.
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.
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.
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.
Based on SOC occupation classification
| 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"} |
Archive a completed reespec request.
Input: A request name. If not provided, run reespec list and ask the user to select. Do NOT auto-select or guess.
Run reespec list to show active requests. Ask the user to confirm which one to archive if not specified.
Read reespec/requests/<name>/tasks.md.
Count - [ ] (incomplete) vs - [x] (complete).
If incomplete tasks exist:
If all tasks complete: proceed without prompt.
Run:
reespec status --request "<name>"
If any artifacts are missing or empty, warn the user. Do not block — inform and confirm.
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.
reespec archive --request "<name>"
This moves the request to reespec/requests/archive/YYYY-MM-DD-<name>.
## 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.