Initialize Blueprint Development structure in current project
Sets up Blueprint Development structure for project documentation and workflow management
/plugin marketplace add laurigates/claude-plugins/plugin install blueprint-plugin@lgates-claude-pluginsInitialize Blueprint Development in this project.
Steps:
Check if already initialized:
docs/blueprint/manifest.jsonUse AskUserQuestion:
question: "Blueprint already initialized (v{version}). What would you like to do?"
options:
- "Check for upgrades" → run /blueprint:upgrade
- "Reinitialize (will reset manifest)" → continue with step 2
- "Cancel" → exit
Gather project context (use AskUserQuestion):
question: "What type of project is this?"
options:
- "Personal/Solo project" → recommend .gitignore for .claude/
- "Team project" → recommend committing .claude/ for sharing
- "Open source" → recommend .claude/rules/ for contributor guidelines
Ask about modular rules:
question: "How would you like to organize project instructions?"
options:
- "Single CLAUDE.md file" → traditional approach
- "Modular rules (.claude/rules/)" → create rules directory structure
- "Both" → CLAUDE.md for overview, rules/ for specifics
allowMultiSelect: false
Ask about feature tracking (use AskUserQuestion):
question: "Would you like to enable feature tracking?"
options:
- label: "Yes - Track implementation against requirements"
description: "Creates feature-tracker.json to track FR codes from a requirements document"
- label: "No - Skip feature tracking"
description: "Can be added later with /blueprint-feature-tracker-sync"
If "Yes" selected: a. Ask for source document:
question: "Which document contains your feature requirements?"
options:
- label: "REQUIREMENTS.md"
description: "Standard requirements document (most common)"
- label: "README.md"
description: "Use README as requirements source"
- label: "Other"
description: "Specify a different document"
b. Create docs/blueprint/feature-tracker.json from template
c. Set has_feature_tracker: true in manifest
Ask about document detection (use AskUserQuestion):
question: "Would you like to enable automatic document detection?"
options:
- label: "Yes - Detect PRD/ADR/PRP opportunities"
description: "Claude will prompt when conversations should become documents"
- label: "No - Manual commands only"
description: "Use /blueprint:prd, /blueprint:adr, /blueprint:prp-create explicitly"
Set has_document_detection in manifest based on response.
If modular rules enabled and document detection enabled:
Copy document-management-rule.md template to .claude/rules/document-management.md
Check for root documentation to migrate:
# Find markdown files in root that look like documentation (not standard files)
fd -d 1 -e md . | grep -viE '^\./(README|CHANGELOG|CONTRIBUTING|LICENSE|CODE_OF_CONDUCT|SECURITY)'
If documentation files found in root (e.g., REQUIREMENTS.md, ARCHITECTURE.md, DESIGN.md):
Use AskUserQuestion:
question: "Found documentation files in root directory: {file_list}. Would you like to organize them?"
options:
- label: "Yes, move to docs/"
description: "Migrate existing docs to proper structure (recommended)"
- label: "No, leave them"
description: "Keep files in current location"
If "Yes" selected: a. Analyze each file to determine type:
docs/prds/docs/adrs/docs/prps/docs/
b. Move files to appropriate docs/ subdirectory
c. Rename to kebab-case if needed (REQUIREMENTS.md → requirements.md)
d. Report migration results:Migrated documentation:
- REQUIREMENTS.md → docs/prds/requirements.md
- ARCHITECTURE.md → docs/adrs/0001-initial-architecture.md
Create directory structure:
Blueprint structure (in docs/blueprint/):
docs/
├── blueprint/
│ ├── manifest.json # Version tracking and configuration
│ ├── work-overview.md # Progress tracking
│ ├── work-orders/ # Task packages for subagents
│ │ ├── completed/
│ │ └── archived/
│ ├── ai_docs/ # Curated documentation (on-demand)
│ │ ├── libraries/
│ │ └── project/
│ └── README.md # Blueprint documentation
├── prds/ # Product Requirements Documents
├── adrs/ # Architecture Decision Records
└── prps/ # Product Requirement Prompts
Claude configuration (in .claude/):
.claude/
├── rules/ # Modular rules (including generated)
│ ├── development.md # Development workflow rules
│ ├── testing.md # Testing requirements
│ └── document-management.md # Document organization rules (if detection enabled)
├── skills/ # Custom skill overrides (optional)
└── commands/ # Custom command overrides (optional)
Create manifest.json (v3.0.0 schema):
{
"format_version": "3.0.0",
"created_at": "[ISO timestamp]",
"updated_at": "[ISO timestamp]",
"created_by": {
"blueprint_plugin": "3.0.0"
},
"project": {
"name": "[detected or asked]",
"type": "[personal|team|opensource]",
"detected_stack": []
},
"structure": {
"has_prds": true,
"has_adrs": true,
"has_prps": true,
"has_work_orders": true,
"has_ai_docs": false,
"has_modular_rules": "[based on user choice]",
"has_feature_tracker": "[based on user choice]",
"has_document_detection": "[based on user choice]",
"claude_md_mode": "[single|modular|both]"
},
"feature_tracker": {
"file": "feature-tracker.json",
"source_document": "[user selection]",
"sync_targets": ["work-overview.md", "TODO.md"]
},
"generated": {
"rules": {},
"commands": {}
},
"custom_overrides": {
"skills": [],
"commands": []
}
}
Note: Include feature_tracker section only if feature tracking is enabled.
Create work-overview.md:
# Work Overview: [Project Name]
## Current Phase: [Phase name - e.g., "Planning", "Phase 1", "MVP"]
### Completed
- (none yet)
### In Progress
- (none yet)
### Pending
- (none yet)
## Next Steps
1. Create a PRD to define project requirements
2. Generate project-specific skills from PRDs
3. Generate workflow commands for your stack
Create initial rules (if modular rules selected):
development.md: TDD workflow, commit conventionstesting.md: Test requirements, coverage expectationsdocument-management.md: Document organization rules (if document detection enabled).gitignore based on project type:.claude/ to .gitignore.claude/ (ask about secrets)docs/, .claude/rules/, gitignore docs/blueprint/work-orders/Blueprint Development initialized! (v3.0.0)
Blueprint structure created:
- docs/blueprint/manifest.json
- docs/blueprint/work-overview.md
- docs/blueprint/work-orders/
- docs/blueprint/ai_docs/
- docs/blueprint/README.md
[- docs/blueprint/feature-tracker.json (if feature tracking enabled)]
Project documentation:
- docs/prds/ (Product Requirements Documents)
- docs/adrs/ (Architecture Decision Records)
- docs/prps/ (Product Requirement Prompts)
Claude configuration:
- .claude/rules/ (modular rules, including generated)
- .claude/skills/ (custom skill overrides)
- .claude/commands/ (custom command overrides)
Configuration:
- Project type: [personal|team|opensource]
- Rules mode: [single|modular|both]
[- Feature tracking: enabled (source: {source_document})]
[- Document detection: enabled (Claude will prompt for PRD/ADR/PRP creation)]
[Migrated documentation:]
[- {original} → {destination} (for each migrated file)]
Architecture:
- Plugin layer: Generic commands from blueprint-plugin (auto-updated)
- Generated layer: Rules/commands regeneratable from docs/prds/
- Custom layer: Your overrides in .claude/skills/ and .claude/commands/
Prompt for next action (use AskUserQuestion):
question: "Blueprint initialized. What would you like to do next?"
options:
- label: "Create a PRD"
description: "Write requirements for a feature (recommended first step)"
- label: "Generate project commands"
description: "Detect project type and create /project:continue, /project:test-loop"
- label: "Add modular rules"
description: "Create .claude/rules/ for domain-specific guidelines"
- label: "I'm done for now"
description: "Exit - you can run /blueprint:status anytime to see options"
Based on selection:
/blueprint:prd/blueprint:generate-commands/blueprint:rulesQuick Reference (show if user selects "I'm done for now"):
Management commands:
- /blueprint:status - Check version and configuration
- /blueprint:upgrade - Upgrade to latest format version
- /blueprint:prd - Create a Product Requirements Document
- /blueprint:adr - Create an Architecture Decision Record
- /blueprint:prp-create - Create a Product Requirement Prompt
- /blueprint:generate-skills - Generate skills from PRDs
- /blueprint:generate-commands - Create workflow commands
- /blueprint:sync - Check for stale generated content
- /blueprint:promote - Move generated content to custom layer
- /blueprint:rules - Manage modular rules
- /blueprint:claude-md - Update CLAUDE.md
- /blueprint:feature-tracker-status - View feature completion stats
- /blueprint:feature-tracker-sync - Sync tracker with project files