← ClaudeAtlas

os-archive-itemlisted

Archive a portfolio item (campaign, opportunity, idea, etc.). Marks it complete or stopped, writes a structured summary.md, moves the TRACKER row from Active to Archived, and appends a one-line entry to portfolio-level LEARNINGS.md. The summary is the durable record that informs future items in the same portfolio.
simonconway1979/os-intelligence · ★ 3 · AI & Automation · score 69
Install: claude install-skill simonconway1979/os-intelligence
# /os-archive-item — Archive a Portfolio Item Generic skill for closing out any portfolio item. Works for campaigns, job opportunities, ideas, events — anything in a portfolio. The point of this skill is to produce a **summary that's actually re-read.** The user reviews and edits the summary; that's the deliverable, not the file move. Treat the move/tracker updates as housekeeping around the real work. --- ## Step 1 — Identify the item If `[workspace-root]/.current-session` points to a portfolio item (format: `[Portfolio Name] / [Item Name]`), use that automatically. Confirm with the user: `Archiving [Item Name] from [Portfolio]?` If standalone (no active item context): 1. Read `projects.md`, filter to `**Type:** portfolio` 2. Ask which portfolio 3. Read that portfolio's `TRACKER.md`, list active items 4. Ask which item --- ## Step 2 — Read what's already there Read the item file (e.g., `campaign.md`, `opportunity.md` — name comes from portfolio CLAUDE.md `**Item name:**`). Extract for pre-filling the summary: - Goal / objective - Any performance tables, metrics, dated activity logs - Stage history if recorded - Key files referenced If the item folder contains a `summary.md` already, **stop and ask** — never overwrite an existing summary. Offer to update it instead. --- ## Step 3 — Outcome and reason Ask: ``` Outcome? 1. Complete — the work finished as intended (or close enough) 2. Stopped — pulled before completion (deprioritised, killed, blocked) ``` If **St