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.

⭐6stars🔀3forks📁View on GitHub🕐Updated Jan 7, 2026

When & Why to Use This Skill

The AI Builder - Project Restore skill is a powerful utility designed to automate the recovery and reconstruction of development projects. It seamlessly restores projects from local archives, remote Git repositories, or existing codebases into the workspace root. Beyond simple file restoration, it intelligently reconstructs missing project metadata, including 'ideas.md', stage-based folder structures, and sprint backlogs, ensuring a developer can resume work immediately with full context and organized documentation.

Use Cases

  • Project Resumption: Quickly reactivate a project from a '99-archive' folder, restoring the workspace to its exact previous state including all submodules and stage folders.
  • Git Repository Onboarding: Automatically clone and configure a remote Git repository into the local workspace environment, ensuring the 'src' directory and project stages are correctly aligned.
  • Documentation Reconstruction: Use reverse-engineering capabilities to generate missing project documentation, feature specs, and sprint histories for legacy codebases that lack structured metadata.
  • Workspace Migration: Move a local codebase into a standardized project structure by re-adding source submodules and generating required organizational folders (stages 00-10).
namedev-swarm-project-restore
descriptionRestore 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.

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

See dev-swarm/docs/general-dev-stage-rule.md for role selection guidance.

Role Communication

See dev-swarm/docs/general-dev-stage-rule.md for the required role announcement format.

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/, follow references/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-* through 10-*
  • sprints and backlogs in 09-sprints/
  • feature specs under features/

Expected Output

  • Archived project content restored to workspace root
  • ideas.md present at the root
  • src/ re-added as a submodule at the correct commit
  • 99-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 src submodule state
  • Ask for user approval before destructive or irreversible operations