Convert an existing project (with scattered markdown/docs) to use `.context/project/` structure.
Scans your project to discover existing docs and structure, then automatically creates a `.context/project/` planning framework with pre-filled content based on your actual codebase. Use this to organize scattered markdown files and establish a single source of truth for project planning.
/plugin marketplace add unclecode/claude-code-tools/plugin install unclecode-cc-toolkit@unclecode-toolsConvert an existing project (with scattered markdown/docs) to use .context/project/ structure.
Note: For small projects needing only one subproject, use the name "main" as the default.
$ARGUMENTS
This command:
.context/project/ structure with pre-filled contentLaunch 5 parallel explorer agents to gather project information:
Agent 1: Markdown Discovery
Find all markdown files in the project. For each file:
- Path
- Title/purpose (from content)
- Type: documentation, decision log, notes, readme, spec, etc.
Report as structured list.
Agent 2: Project Structure Analysis
Analyze the codebase structure:
- Main directories and their purposes
- Identify potential subprojects/modules (e.g., frontend/, backend/, api/)
- Key technologies used
- Entry points and main files
Report the logical structure.
Agent 3: Current State Discovery
Find indicators of current project state:
- TODOs in code comments
- README status sections
- Any existing tracking files
- Recent git commits (last 10) for context
- Package.json, requirements.txt, etc. for dependencies
Report what's working, what's in progress.
Agent 4: Configuration & Environment
Find configuration details:
- Environment files (.env.example, config files)
- Build/deployment configs
- API endpoints or external services
- Database schemas if present
Report environment setup.
Agent 5: Documentation Quality
Assess existing documentation:
- Is there a main README?
- API docs?
- Architecture docs?
- Are docs up to date or stale?
Report documentation gaps and strengths.
After agents complete:
Present findings and ask:
Create .context/project/ structure using pp-init-assets/templates/ but:
Pre-fill root INDEX.md instead of placeholders:
For each subproject:
Present migration plan:
Files to move:
- docs/api-spec.md → .context/project/{subproject}/docs/
- DECISIONS.md → .context/project/{subproject}/docs/
- old-notes.md → .context/project/archive/
Files to keep in place:
- README.md (root)
- CONTRIBUTING.md (root)
Ask: "Should I proceed with moving these files? (y/n)"
If yes, execute moves. If no, skip migration, just create structure.
Show:
Uses same templates as /pp-init from:
~/.claude/commands/pp-init-assets/templates/
But fills content from discovered information instead of placeholders.
# Basic migration
/pp-migrate
# With context hint
/pp-migrate This is a Facebook ads automation project with webhook server and analytics dashboard
# Skip file migration
/pp-migrate --no-move
--no-move: Create structure but don't move existing files--dry-run: Show what would be done without making changesgit mv when possible.context/project/ already exists, asks before overwriting