project-init

Initialize ProjectMaster Configuration

When the user runs /project-init, perform the following tasks:

Task 1: Scan Current Directory

Scan the current directory and subdirectories to understand the existing structure:

1. Check for RULE.md files:

   find . -name "RULE.md" -type f
   

   List all RULE.md files found.

2. Check for milestones.yaml:

   find . -name "milestones.yaml" -type f
   

3. Check for project directories: Look for typical project directories:

   • meetings/
   • sprints/ or iterations/ or board/
   • docs/
   • decisions/

4. Identify project structure type:

   • Initialized ProjectMaster project (has RULE.md with ProjectMaster metadata)
   • AkashicRecords project (has RULE.md but no ProjectMaster config)
   • Uninitialized directory (no RULE.md)
   • Multiple projects (multiple RULE.md files in different subdirectories)

Task 2: Report Current State

Present findings to the user:

📋 ProjectMaster Configuration Scan

Current directory: {path}

🔍 Found:
- RULE.md files: {count} ({locations})
- milestones.yaml: {count} ({locations})
- Project directories: {list}

📊 Assessment:
{One of:}
- ✅ ProjectMaster project detected at {path}
- ⚠️ AkashicRecords project detected (no ProjectMaster config)
- ℹ️ No project governance detected
- 📁 Multiple projects detected: {count}

Task 3: Offer Actions

Based on assessment, offer appropriate actions:

If ProjectMaster project detected:

✅ ProjectMaster is initialized for this project.

**Configuration**:
- Methodology: {from RULE.md}
- Team size: {from RULE.md}
- Documentation format: {from RULE.md}

**Health check**:
- RULE.md: ✅ Present
- milestones.yaml: ✅ Present
- README.md: {✅ Present | ⚠️ Missing}
- Directory structure: {✅ Complete | ⚠️ Missing directories}

Would you like to:
1. Validate governance (check README.md indexes)
2. Update RULE.md configuration
3. View project status (/project-status)
4. No action needed