Agent skill
dev-swarm-project-restore
Restore a project from 99-archive, a remote git repo, or a local codebase back to the workspace root, including reconstructing missing docs, stages, and sprints. Use when the user asks to resume work on an existing project.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/dev-swarm-project-restore-x-school-academy-ai-dev-swarm
SKILL.md
AI Builder - Project Restore
This skill restores an existing project to the workspace root from an archive, remote git repo, or local codebase, including re-adding src and reconstructing missing docs when needed.
When to Use This Skill
- User asks to restore a project from
99-archive/ - User wants to restore a project from a remote git repository or a non-archived local codebase
- User needs
ideas.md, stage folders, or sprints reconstructed to resume work
Your Roles in This Skill
- Project Manager: Coordinate the restore flow, confirm the target archive, and ensure the workspace is consistent after restore.
- DevOps Engineer: Handle git operations, submodule re-attachment, and repository integrity.
- Technical Writer: Document decisions and confirm restore outcomes for human approval.
Role Communication
As an expert in your assigned roles, you must announce your actions before performing them using the following format:
As a {Role} [and {Role}, ...], I will {action description}
This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.
Instructions
Follow these steps in order:
Step 1: Archive the Current Project
Archive the current project using agent skill dev-swarm-project-archive.
Step 2: Identify the Restore Source
Confirm whether the source is:
99-archive/{archive-folder}- Remote git repository URL
- Local codebase path (not created by archive; with or without git history)
Record the source in your notes before proceeding.
Step 3: Restore the Project
- If restoring from
99-archive/, followreferences/restore-procedure.md. - If restoring from a remote git repo or local codebase, follow
references/external-restore.md.
Step 4: Reverse-Engineer Missing Docs (If Needed)
If the codebase has little or no documentation, follow references/reverse-engineering.md to reconstruct:
ideas.md- stage folders
00-*through10-* - sprints and backlogs in
09-sprints/ - feature specs under
features/
Expected Output
- Archived project content restored to workspace root
ideas.mdpresent at the rootsrc/re-added as a submodule at the correct commit99-archive/retains the archived snapshot- Reconstructed stages, sprints, and features when docs were missing
Key Principles
- Keep the restore process reversible and traceable in git history
- Prefer existing git history to restore the
srcsubmodule state - Ask for user approval before destructive or irreversible operations
Didn't find tool you were looking for?