os-archive-item

Archive portfolio items by updating summary.md, TRACKER.md, and LEARNINGS.md.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/simonconway1979/os-intelligence --skill os-archive-item
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-archive-item
Source: https://github.com/simonconway1979/os-intelligence/tree/main/.claude/skills/os-archive-item
Command: npx skills add https://github.com/simonconway1979/os-intelligence --skill os-archive-item

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It closes out portfolio work without losing the reasoning, outcomes, and reusable lessons that you’ll want to reference later.

Core Features & Use Cases

  • Outcome-driven closeout: Captures whether the item was completed or stopped and records the correct stop reason when applicable.
  • Re-readable summary.md deliverable: Produces a structured summary that the user reviews and edits, preventing accidental overwrite of an existing summary.
  • Portfolio bookkeeping automation: Updates the item’s stage, moves its row in TRACKER.md from Active to Archived, and appends a one-line learning to the portfolio’s LEARNINGS.md.

Quick Start

Ask the assistant to archive your current portfolio item by running: /os-archive-item

Frequently Asked Questions about os-archive-item

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a portfolio item without losing lessons learned and outcome details?

Archiving a portfolio item requires creating a durable summary.md, updating the item stage metadata, moving its tracker row to Archived, and appending a one-line learning to LEARNINGS.md to preserve outcomes and reasoning.

What is the best way to close out campaigns and record stop reasons in product operations?

Closing out campaigns involves capturing whether the item was completed or stopped, recording the correct stop reason, and generating a structured summary that you review and edit to ensure accurate portfolio bookkeeping.

How do I update TRACKER.md and LEARNINGS.md when archiving portfolio work?

Updating TRACKER.md moves the item row from Active to Archived, while LEARNINGS.md receives a newly appended one-line learning, ensuring both files stay synchronized with the item's stage metadata during the archive process.

Can I overwrite an existing summary.md file when closing an opportunity or event?

You cannot overwrite an existing summary.md file; the archiving process requires producing a new structured summary for your review and edits to prevent accidental data loss of previous portfolio documentation.

Do I need an active portfolio item context to start the document synthesis process?

You need active item context, such as existing TRACKER.md artifacts, to begin document synthesis; otherwise, the system will prompt you for portfolio and item selection before generating the archived summary.

Why does portfolio archiving require reviewing the summary before finalizing the closeout?

Portfolio archiving requires review because the generated outcome-driven summary is structured for future reference, ensuring you verify the completion status, stop reasons, and lessons learned before updating your portfolio records.