ralph:archive

Archive Ralph run state by moving prd.json and progress.txt into a timestamped folder.

17|1|Updated Nov 17, 2024
One-click install
npx skills add https://github.com/mifunedev/orchestra --skill ralph-archive-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph:archive
Source: https://github.com/mifunedev/orchestra/tree/main/.claude/skills/ralph-archive
Command: npx skills add https://github.com/mifunedev/orchestra --skill ralph-archive-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive the current Ralph run state by relocating prd.json and progress.txt into a timestamped archive folder.

Core Features & Use Cases

  • Archives .ralph/prd.json and .ralph/progress.txt into .ralph/archive/[feat|bug]-<issue#>/ so a new Ralph run can start clean.
  • Creates the archive directory derived from the branchName; if the directory exists, appends a numeric suffix to avoid overwriting.
  • Removes the originals from the .ralph/ root after successful archival and confirms what was archived and where.

Quick Start

Archive the current Ralph run (prd.json and progress.txt) before starting a new feature.

Frequently Asked Questions about ralph:archive

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

FAQPage Schema
How do I archive Ralph run state files before starting a new feature?

To archive Ralph run state, relocate prd.json and progress.txt into a timestamped folder under .ralph/archive/. The Skill derives the archive path from the branchName in prd.json and removes the originals after a successful copy.

What happens if the Ralph archive directory already exists for a feature branch?

When the target archive directory already exists, the Skill appends a numeric suffix to the folder name. This prevents overwriting previous archives while preserving the full history of Ralph runs for that specific issue.

Do I need a specific branchName format to archive Ralph progress files?

Yes, archiving Ralph progress files requires a .ralph/prd.json file containing a branchName. The Skill uses this branchName to derive the archive path, creating a .ralph/archive/[feat|bug]-<issue#>/ directory structure.

When should I archive my Ralph run state for workflow automation?

You should archive your Ralph run state when starting a new feature or bug fix. This preserves the history of completed work while providing a clean slate for the new Ralph run.

Does the Ralph archive process delete the original prd.json and progress.txt files?

Yes, the Ralph archive process removes the original prd.json and progress.txt files from the .ralph/ root directory. This deletion only occurs after the files have been successfully copied to the timestamped archive folder.

What is the best way to preserve Ralph state management history across DevOps cycles?

The best way to preserve Ralph state management history is to use an automated archival process that relocates run files into timestamped directories. This ensures clean feature handoffs without losing previous progress tracking data.