project-archive

Index historical build and strategic docs for Inventory Full.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/thingperson/pileofshame --skill project-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-archive
Source: https://github.com/thingperson/pileofshame/tree/main/.claude/skills/project-archive
Command: npx skills add https://github.com/thingperson/pileofshame --skill project-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized index to Inventory Full's evergreen historical archive, linking to three purpose-built docs that capture past build history, road-mapping decisions, and blue-sky philosophy and branding rationale. Use this to quickly locate context about what was built, why decisions were made, and how the product strategy evolved.

Core Features & Use Cases

  • Historical reference: Access BUILD_HISTORY.md for shipped features and their timelines.
  • Strategic planning: Consult ROADMAP_PHASES.md to understand future priorities and rationale.
  • Philosophy and branding: Read BLUE_SKY.md for the brand, design tokens, and conceptual foundations.
  • Use Case: When planning a new feature, review prior work and the strategic rationale to avoid rework and align with the product vision.

Quick Start

Open the project-archive page and read the relevant document (BUILD_HISTORY.md, ROADMAP_PHASES.md, or BLUE_SKY.md) to review historical context.

Frequently Asked Questions about project-archive

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

FAQPage Schema
How do I review past feature timelines and historical build archives for my project?

To review historical build archives, you need an indexing mechanism that routes you to specific docs like BUILD_HISTORY.md. This provides a read-only reference to past features and timelines without aggregating all content.

Where can I find strategic roadmaps and branding rationale for product planning?

Strategic roadmaps and branding rationale are typically stored in dedicated docs like ROADMAP_PHASES.md and BLUE_SKY.md. An archive index routes you to these specific files to understand future priorities and conceptual foundations.

What is the best way to locate historical product strategy and design token decisions?

The best way to locate historical product strategy is through a centralized archive index linking to specific purpose-built docs. This allows you to quickly find context on design tokens and strategy without manually searching the entire codebase.

Can I use a project archive to prevent duplicated work when planning new features?

Yes, you can use a project archive to prevent duplicated work. By consulting prior build history and strategic rationale, you align new features with the existing product vision and avoid rework.

Does the project-archive skill aggregate all historical documentation into a single view?

No, the project-archive skill does not aggregate all content into a single view. It functions as a read-only index that routes you directly to the specific historical doc you need, such as BUILD_HISTORY.md or ROADMAP_PHASES.md.