Project Management Bootstrapper
Initialize a comprehensive project management system with folder structures, TODO tracking, resource catalogs, and Claude-specific project configuration.
Every new project starts with 30 minutes of creating folders, setting up tracking docs, writing the README, and configuring your tools. By project #20, you realize you've done this setup dance hundreds of times and it's never consistent.
Who it's for: project managers setting up new project workspaces regularly, team leads establishing consistent project structures across their team, consultants who start new client projects frequently, developers who want every project to have proper documentation from day one, organizations standardizing project setup across departments
Example
"Bootstrap a new client project with full PM setup" → Complete project structure: folder hierarchy, README with project overview, TODO tracking system, resource catalog, meeting notes template, CLAUDE.md for AI-assisted workflows, and stakeholder communication templates
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Project Management Bootstrapper
## Your Role
You initialize comprehensive project management systems, adapting to existing structure and workflows. You never assume, never overwrite, and never reorganize without permission.
## Instructions
### Phase 1: Discovery (DO THIS FIRST)
Before making ANY changes, assess the current state:
1. **Explore existing folder structure** — list all folders and files, note any organizational systemGet new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Bootstraps a complete project management system for any project — folder structures, TODO tracking, a resource catalog, and Claude-specific configuration. It explores your existing setup first, never overwrites, and only creates what's missing.
Quick Start
Step 1: Navigate to Your Project
cd ~/Projects/my-project
Step 2: Download the Template
Click Download above, then:
mv ~/Downloads/CLAUDE.md ./
Step 3: Run Claude Code
claude
Then: "Set up project management for this project"
The 6-Phase Process
| Phase | What Happens | Changes Made? |
|---|---|---|
| 1. Discovery | Explores existing folders, docs, tools | No |
| 2. Gap Analysis | Identifies what's missing | No |
| 3. Design Discussion | Asks about project type, preferences | No |
| 4. Propose Plan | Presents specific changes for approval | No |
| 5. Implementation | Creates approved files and folders | Yes |
| 6. Verification | Confirms everything is correct | No |
Nothing changes until you approve in Phase 4.
What Gets Created
| File | Purpose |
|---|---|
TODO.md |
Project tasks with routing links |
PROJECT_INDEX.md |
Master resource catalog with links |
.claude/CLAUDE.md |
Claude-specific project instructions |
AI_Collaboration/Transcripts/ |
Meeting transcript storage |
AI_Collaboration/Weekly_Reviews/ |
Weekly review outputs |
Project Types
| Type | Folder Focus |
|---|---|
| Quantitative / RCT | IRB, Survey Instruments, Field Materials, Data |
| Qualitative | Fieldwork, Interview Memos, Transcripts, Consent |
| Theory / Writing | Minimal structure, Paper drafts, References |
| Policy Brief | Streamlined for non-academic deliverables |
| Multi-method | Combined quantitative and qualitative |
Key Principles
- Never assume — always explore before proposing
- Never overwrite — check for existing files first
- Never reorganize without permission — existing structure may have reasons
- Iterate — go back and forth until the plan is right
- Preserve what works — don't fix what isn't broken
Execution Modes
| Mode | Command | What It Does |
|---|---|---|
| Discover | "discover only" |
Phases 1-2 only (assessment) |
| Plan | "plan only" |
Through Phase 4 (no implementation) |
| Full | "full setup" |
All 6 phases |
| Minimal | "minimal setup" |
Only .claude/CLAUDE.md and essentials |
Tips
- Works for any project type — software, research, writing, policy, business
- Adapts to existing tools — Google Docs, Overleaf, GitHub, Slack, WhatsApp
- Run "discover" first — see what's there before committing to changes
- Data sensitivity — asks about IRB status and handling requirements
Troubleshooting
Proposed structure doesn't fit my workflow Tell Claude what to change — Phase 3 is a discussion, iterate until it's right
Want to redo the setup
Run again with discover to reassess, then propose new changes
Existing files conflict Claude will flag conflicts and ask how to resolve them