skills/golem-powers/archive/SKILL.md
Use when planning a sprint transition, archiving completed work, or resetting the PRD for a fresh start. Archives completed PRD stories to docs.local/. Covers archive, cleanup, sprint transition, reset PRD. NOT for: deleting stories mid-sprint (use prd-manager), viewing PRD status (use ralph-status).
npx skillsauth add etanhey/golems archiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Archive completed stories to
docs.local/prd-archive/with full history preservation. Optionally reset the working PRD for a fresh start.
Run these directly - standalone, no ralph.zsh dependency:
| Script | Purpose | Usage |
|--------|---------|-------|
| scripts/archive-snapshot.sh | Create archive snapshot | bash ~/.claude/commands/archive/scripts/archive-snapshot.sh |
| scripts/cleanup-completed.sh | Archive + remove completed | bash ~/.claude/commands/archive/scripts/cleanup-completed.sh |
| What you want to do | Workflow | |---------------------|----------| | Archive current PRD state (snapshot) | workflows/archive-snapshot.md | | Remove completed stories (cleanup) | workflows/cleanup-completed.md |
Each archive creates a timestamped directory:
docs.local/prd-archive/20260123-153000/
├── index.json # PRD index at time of archive
├── stories/ # All story files (completed + pending)
│ ├── US-001.json
│ ├── US-002.json
│ └── ...
└── progress.txt # Ralph progress log
When cleanup is triggered (via --clean or confirming prompt):
*.json files where passes=trueprogress.txt replaced with fresh start headerHistory is always preserved - The archive contains full state before cleanup.
docs.local/prd-archive/development
Create, edit, and verify golem-powers skills using the standard SKILL.md structure, workflow files, adapters, templates, and eval fixtures. Use for new skills, structural edits, workflows/adapters, and pre-deploy validation. NOT for invoking existing skills, superpowers skills, or skill-creator agent workflows.
testing
Extract structured knowledge from any video source — YouTube URLs or local screen recordings. YouTube → gems workflow (yt-dlp transcript → keyword hotspots → frame extract → brain_digest → structured gems). Screen recordings → QA workflow (reuses /qa-video stalker pipeline). Use when user shares a YouTube link wanting deep extraction with frames, shares a .mov/.mp4 for QA processing, says "extract from video", "video gems", "process this recording", or mentions gem extraction from video content.
testing
Use when running or reviewing any recurring monitor loop for merge queues, worker queues, collab tails, or agent completion. Enforces drive-to-completion ticks: every tick must query live state with `!`, classify whether real progress happened, and then dispatch, verify-and-decrement, or escalate-park. Triggers on: monitor loop, /loop, recurring tick, keep monitoring, silent autonomous, merge gate, blocked review, no-progress loop.
tools
MeHayom freelance client management — daily updates, decision tracking, time logging. Use when drafting Yuval updates, logging scope changes, tracking hours, or any MeHayom client communication. Triggers: 'draft Yuval update', 'client update', 'daily update', 'log decision', 'track time', 'mehayom'.