Archive
Close an ai-workspace plan by recording outcomes and learnings, then commit the renamed .done.md archive.
Overview
archive is an agent skill most often used in Build (also Operate) that finalizes ai-workspace plans with outcomes, learnings, and a committed .done.md archive.
Install
npx skills add https://github.com/camacho/ai-skills --skill archiveWhat is this skill?
- Resolves WORKTREE via session CWD or git rev-parse --show-toplevel
- Default target: newest non-.done.md plan under ai-workspace/plans/
- Structured Outcomes & Learnings section with Completed date, What Worked, What Didn't, Learnings
- Git mv to .done.md plus docs commit with Co-Authored-By trailer
- Non-blocking if user skips narratives—writes Outcomes: not recorded instead of failing
- Six numbered workflow steps from plan discovery through git commit
Adoption & trust: 665 installs on skills.sh; 1 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finished work tracked in a plan file but have no standard way to record results and mark the plan complete in git.
Who is it for?
Solo builders using git worktrees and ai-workspace plans who want repeatable post-mortems without a separate PM tool.
Skip if: Creating the initial plan or running implementation—use planning skills first; skip if the plan is already .done.md.
When should I use this skill?
User wants to fill Outcomes & Learnings in a plan file and rename it to .done.md in the current WORKTREE.
What do I get? / Deliverables
The plan gains an Outcomes & Learnings section, lives as a .done.md file under ai-workspace/plans/, and is committed with a docs message for future you.
- Plan file renamed to .done.md with Outcomes & Learnings section
- Git commit documenting the archived plan path
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build → pm because the ritual finalizes an implementation plan artifact in the worktree, even though you can run it whenever a planned chunk of work ends. The skill is pure planning hygiene—outcomes, learnings, and git archival—not code generation or shipping binaries.
Where it fits
After merging a feature branch, archive the plan that drove the agent tasks.
Record launch checklist results in Outcomes before marking the release plan done.
Capture incident response learnings when closing a remediation plan.
How it compares
Workflow closure for in-repo plans—not a standalone note app or issue tracker integration.
Common Questions / FAQ
Who is archive for?
Developers using ai-workspace plan files who want a scripted end-of-plan ritual with git history.
When should I use archive?
After Build or Operate milestones when implementation against a plan is done—infer outcomes from git log or answer prompts, then archive before starting the next plan.
Is archive safe to install?
It performs git mv and commit inside your worktree; review the Security Audits panel on this Prism page and ensure you are on the intended branch before archiving.
SKILL.md
READMESKILL.md - Archive
## Inputs - `WORKTREE`: absolute path to current worktree (resolve from session CWD or `git rev-parse --show-toplevel`) - Plan file path (default: most recent non-`.done.md` in `$WORKTREE/ai-workspace/plans/`) ## Steps 1. **Find the plan file**: ```bash ls -t "$WORKTREE/ai-workspace/plans/"*.md | grep -v '.done.md' | head -1 ``` If plan is already `.done.md` → error: "Already archived." 2. **Read the plan file** to understand what was planned. 3. **Gather outcomes**: Ask the user (or infer from git log + branch context): - What worked well? - What didn't go as planned? - What would you do differently? If user skips → write "Outcomes: not recorded" (don't block). 4. **Write Outcomes & Learnings section** to the plan file: ```markdown ## Outcomes & Learnings **Completed**: [date] ### What Worked - [bullet points] ### What Didn't - [bullet points] ### Learnings - [bullet points] ``` 5. **Rename to .done.md**: ```bash git -C "$WORKTREE" mv ai-workspace/plans/<name>.md ai-workspace/plans/<name>.done.md ``` 6. **Commit the archive**: ```bash git -C "$WORKTREE" add ai-workspace/plans/<name>.done.md git -C "$WORKTREE" commit -m "docs: archive plan <name> Co-Authored-By: Claude <model>" ``` Output: Confirmation that the plan is archived with path to `.done.md` file.