skills.rest
iroh4-labs
iroh4-labsCOMMUNITY
Explore all skills by this author →
GitHub

shelve

Archive completed features to a directory in Claude Code projects.

2|1|Updated May 2, 2026
Search Tags:#Claude Code#project organization#archive#feature management#automated workflow
One-click install
npx skills add https://github.com/iroh4-labs/mumei --skill shelve-iroh4-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shelve
Source: https://github.com/iroh4-labs/mumei/tree/main/skills/shelve
Command: npx skills add https://github.com/iroh4-labs/mumei --skill shelve-iroh4-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of moving completed features to an archive directory in Claude Code projects, reducing manual effort and ensuring a clean workspace.

Core Features & Use Cases

  • Automated Archiving: Moves completed features to an archive directory once they reach the 'done' phase.
  • Auto-Detection: Automatically detects the active vehicle (spec or plan) by checking specified directories.
  • User-Invocable: Allows users to explicitly trigger the archiving process or upon completion of certain workflows.
  • Use Case: Ideal for projects using Claude Code where users want to organize completed features into a historical archive for reference.

Quick Start

To archive a feature, run the command: /mumei:shelve <feature>

Frequently Asked Questions about shelve

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

FAQPage Schema
How do I archive completed features in a Claude Code project?▼

To archive completed features in a Claude Code project, you can run the `/mumei:shelve <feature>` command to automatically move the finished feature to an archive directory.

What directory structure is required to automate feature archiving?▼

Automated feature archiving requires your project to have `.mumei/specs/` or `.mumei/plans/` directories, along with a `state.json` file that tracks the feature's current phase.

When does a feature get moved to the archive directory?▼

A feature gets moved to the archive directory automatically when it reaches the 'done' phase, or you can explicitly trigger the archiving process by invoking the command.

How does automated feature archiving detect active specs or plans?▼

Automated feature archiving detects active specs or plans by checking the specified `.mumei/specs/` or `.mumei/plans/` directories to identify the active vehicle for archiving.

Can I manually trigger feature archiving before a workflow completes?▼

Yes, you can manually trigger feature archiving at any time by running the user-invocable command, moving the target feature to the archive directory without waiting for workflow completion.

Why is my completed feature not moving to the archive directory?▼

If your completed feature is not moving to the archive directory, check that your `state.json` file accurately indicates the feature has reached the 'done' phase and required directories exist.

Related Skills

Explore More Software Engineering Skills→
iroha924iroha924
2

compose

Orchestrate mumei feature development by automating specifications, design documents, and task plans.

Community
Advanced
jossteijosstei
453

archive

Archive active Maestro sessions and associated plans to dedicated directories.

Community
Intermediate
Kabilan108Kabilan108
2

Hook Development

Develop Claude Code plugin hooks with structured JSON and scripts to enforce safety and automate workflows.

Community
Advanced
nnexainnexai
1

gsd-cleanup

Archive completed phase directories into versioned milestone folders within .planning.

Community
Advanced