import-project

Imports existing repositories into the PoP vault with codebase recon and an organization gate.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill import-project-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: import-project
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/import-project
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill import-project-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bringing an existing repository or local project into a managed vault workflow is risky: agents may start changing code before anyone understands what the project actually is. This Skill onboards existing projects through read-only reconnaissance, a structured interview, and a mandatory Epoch 1 of organization that blocks any project changes until the knowledge harness is complete. ## Core Features & Use Cases - Read-only codebase recon: Generates a RECON.md via the recon-project script, then launches parallel subagents covering structure, build/test, docs, git history, and fragile spots, consolidated into a short map confirmed by the user. - Vault fit and materialization: Determines project type (uni-repo vs multi-repo), default language, i18n needs, and PR branch, then installs the pop/ harness with pop_install_unirepo.py and creates PROJECT.md and ROADMAP.md. - Organization gate: Adds a rule to the project's AGENTS.md blocking any change to project content until Epoch 1 (Organization) completes; specs are deferred and created only work-driven via write-spec. - Use Case: You have a legacy codebase you want an AI agent to maintain. Run the import so the agent maps the code, builds DOX documentation, skills, and notes first, and only then starts accepting change tasks through the kanban. ## Quick Start Ask the agent to import your existing repository into the PoP vault by providing its URL or local path.

Frequently Asked Questions about import-project

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

FAQPage Schema
How do I import an existing repository into the PoP vault?▼

Provide the repository URL or local path and the agent clones it read-only, runs recon with parallel subagents, interviews you about type, language, and workflow, then materializes the project structure with a pop/ harness and an Epoch 1 organization roadmap.

What is the difference between uni-repo and multi-repo project types?▼

A uni-repo keeps the AI specs and harness committed inside the repository itself, with the clone at projects/<name>/ being the project. A multi-repo is a parent folder with no harness, containing one clone per repository, each with its own complete pop/ harness.

Does importing a project modify the original repository?▼

No. Recon is strictly read-only and the import never changes the imported repo. An organization gate in the project's AGENTS.md blocks any content changes until Epoch 1 (Organization) is completed, and all later changes flow through the kanban.

Why are no specs created when importing a project?▼

Writing specs at import time is reverse engineering, which is expensive and error-prone without supervision. Specs are born work-driven: when a future task touches an undocumented topic, the agent proposes creating the spec via write-spec and the user decides.

What happens when recon findings conflict with my answers?▼

Any divergence between the codebase recon and your answers becomes a RECON NEEDED item with a defined check to resolve it, or an open question filed in open_questions/. The agent never picks a side on its own.