Initial commit
This commit is contained in:
Zhongwei Li
661
skills/project-creator/SKILL.md
Normal file
661
skills/project-creator/SKILL.md
Normal file
@@ -0,0 +1,661 @@
|
||||
---
|
||||
name: project-creator
|
||||
description: |
|
||||
Creates new projects in CCGG Business Operations with all required mechanisms automatically implemented.
|
||||
Ensures PARENT SYSTEM INTEGRATION, operations logging, strategic alignment, and cross-project intelligence are properly configured.
|
||||
Handles both simple projects (standard structure) and complex projects (with coordination hubs and dependency tracking).
|
||||
|
||||
Use for: creating new incubator project, adding sub-project to CCGG, initializing project structure, setting up project coordination, ensuring PARENT SYSTEM INTEGRATION implemented, generating CLAUDE.md with all mechanisms, creating Active Projects Index entry.
|
||||
|
||||
Trigger terms: create project, new project, initialize project, set up project, add sub-project, project structure, CCGG project creation.
|
||||
version: 1.0.0
|
||||
created: 2025-10-29
|
||||
author: Daron Vener
|
||||
repository: https://github.com/DaronVee/ccgg-project-creator-skill
|
||||
---
|
||||
|
||||
# Project Creator for CCGG Business Operations
|
||||
|
||||
## Quick Start
|
||||
|
||||
**What this skill does**: Automatically creates new CCGG Business Operations projects with all required mechanisms pre-implemented (PARENT SYSTEM INTEGRATION, Active Projects Index, operations logging, etc.).
|
||||
|
||||
**Use when**: Creating new incubator project, adding sub-project to CCGG, setting up project structure
|
||||
|
||||
**Prevents**: Forgetting critical mechanisms like PARENT SYSTEM INTEGRATION (the problem that triggered this skill's creation)
|
||||
|
||||
---
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
**Trigger Phrases**:
|
||||
- "Create new project in CCGG Business Operations"
|
||||
- "Initialize new incubator project"
|
||||
- "Set up project structure for [project-name]"
|
||||
- "Add new sub-project to CCGG"
|
||||
|
||||
**Project Types Supported**:
|
||||
1. **Simple Projects** (majority): Research, single-purpose tools, straightforward deliverables
|
||||
2. **Complex Projects** (strategic): Multi-project coordination, dependencies, integration requirements
|
||||
|
||||
---
|
||||
|
||||
## Project Creation Workflow
|
||||
|
||||
### Step 1: Gather Project Information
|
||||
|
||||
**Ask Daron These Questions** (in conversational order):
|
||||
|
||||
1. **"What's the project name?"**
|
||||
- Format: hyphen-case (e.g., `member-retention-sequences`)
|
||||
- Max 40 characters
|
||||
- Will be used for folder name and project ID
|
||||
|
||||
2. **"What's the project purpose?"** (1-2 sentences)
|
||||
- Clear problem statement
|
||||
- Expected outcome
|
||||
- Example: "Design email sequences to re-engage churned members and improve retention rate"
|
||||
|
||||
3. **Analyze project description for multi-phase indicators** (SUGGESTION, not question):
|
||||
|
||||
**Claude analyzes** project purpose and deliverables for signals:
|
||||
- Keywords: "validate", "test", "feedback", "iterate", "production rollout", "pilot"
|
||||
- Complex deliverables (3+ major components requiring testing)
|
||||
- Integration with existing systems (needs testing phase)
|
||||
- User mentions "experiment", "trial", or "phase"
|
||||
- Project type: infrastructure, framework, new system (vs simple content creation)
|
||||
|
||||
**If multi-phase indicators detected**, SUGGEST phased approach:
|
||||
```
|
||||
"Based on your project description, I recommend a multi-phase approach:
|
||||
|
||||
Phase 1: [Research & Planning / Setup & Test / MVP]
|
||||
Phase 2: [Build & Test / Validation & Refinement / Production Rollout]
|
||||
Phase 3: [Deploy & Scale / Institutionalize / Maintenance]
|
||||
|
||||
This allows testing and feedback before full rollout. Would you like to use this phased approach?"
|
||||
```
|
||||
|
||||
**User can respond**:
|
||||
- "Yes, use phases" → Generate PHASE_TRACKER.md with suggested phases
|
||||
- "No, single phase" → Skip Phase Tracker
|
||||
- "Let me customize phases" → Ask for phase names/durations
|
||||
|
||||
**If NO multi-phase indicators**, skip suggestion and Phase Tracker
|
||||
|
||||
4. **"Will this project coordinate with or depend on other projects?"**
|
||||
- If YES → Complex project (needs Coordination Hub)
|
||||
- If NO → Simple project (standard structure only)
|
||||
|
||||
5. **ALWAYS: Detect and Capture Dependencies** (NEW - Forcing Function)
|
||||
|
||||
**Claude PROACTIVELY suggests dependencies** based on project description:
|
||||
|
||||
```
|
||||
"Let me help identify dependencies for this project:
|
||||
|
||||
BLOCKING DEPENDENCIES (must complete before starting this):
|
||||
- What existing work must finish before you can start?
|
||||
- What deliverables from other projects do you need?
|
||||
|
||||
DOWNSTREAM DEPENDENCIES (projects waiting for this):
|
||||
- What other projects are waiting for this one?
|
||||
- What will this project enable or unblock?
|
||||
|
||||
RELATED PARALLEL (connected but not blocking):
|
||||
- What other projects share themes/tools with this?
|
||||
|
||||
[Based on your project description, I see potential dependencies:]
|
||||
- [Suggest upstream based on keywords/deliverables mentioned]
|
||||
- [Suggest downstream based on Active Projects needing this work]
|
||||
|
||||
Should I add these to the dependency metadata?"
|
||||
```
|
||||
|
||||
**Capture in YAML format**:
|
||||
```yaml
|
||||
dependencies:
|
||||
blocks: ["project-id-1", "project-id-2"] # Must complete first
|
||||
blocked_by: ["project-id-3"] # Waiting for this
|
||||
related_parallel: ["project-id-4"] # Connected, not blocking
|
||||
```
|
||||
|
||||
**Even if "none"**, still create empty fields (forces conscious decision):
|
||||
```yaml
|
||||
dependencies:
|
||||
blocks: [] # No upstream dependencies
|
||||
blocked_by: [] # No downstream dependencies
|
||||
related_parallel: [] # No related work
|
||||
```
|
||||
|
||||
6. **If Complex: "Which projects does this coordinate with?"**
|
||||
- Upstream dependencies (what this project needs)
|
||||
- Downstream dependencies (what other projects need from this)
|
||||
- Example: "Depends on hormozi-money-models (frameworks), feeds into retention-reengagement (implementation)"
|
||||
- **NOTE**: This is for Coordination Hub documentation (prose), Step 5 captures YAML metadata
|
||||
|
||||
7. **"What are the key deliverables?"** (3-5 items)
|
||||
- Specific outputs this project will produce
|
||||
- Example: "Email sequence templates, DM scripts, retention playbook"
|
||||
|
||||
8. **"Which avatars does this serve?"** (optional, for strategic alignment)
|
||||
- From Target_Avatars_Complete_Profiles.md
|
||||
- If "all avatars" → note that
|
||||
- If specific → list them
|
||||
|
||||
---
|
||||
|
||||
### Step 2: Determine Project Complexity
|
||||
|
||||
**Based on Question 3 answer**:
|
||||
|
||||
**SIMPLE PROJECT** (if NO coordination):
|
||||
- Standard folder structure
|
||||
- CLAUDE.md with PARENT SYSTEM INTEGRATION
|
||||
- README.md
|
||||
- Active Projects Index
|
||||
- operations_log entry
|
||||
|
||||
**COMPLEX PROJECT** (if YES coordination):
|
||||
- All simple project components PLUS:
|
||||
- Coordination Hub/ folder
|
||||
- PROJECT_DEPENDENCIES.md
|
||||
- INTEGRATION_CHECKLIST.md
|
||||
- OUTPUT_LIBRARY.md
|
||||
- Enhanced CLAUDE.md (cross-project knowledge access patterns)
|
||||
- Integration sections in related projects' CLAUDE.md files
|
||||
|
||||
---
|
||||
|
||||
### Step 3: Create Project Structure
|
||||
|
||||
**Location**: `Active Projects/_Incubator/[project-name]/`
|
||||
|
||||
**Manual Creation** (automated script planned for future):
|
||||
1. Create folder: `mkdir "Active Projects/_Incubator/[project-name]"`
|
||||
2. Use Write tool to create CLAUDE.md from `templates/CLAUDE_SIMPLE.md` OR `templates/CLAUDE_COMPLEX.md`
|
||||
3. **If multi-phase project**: Use Write tool to create PHASE_TRACKER.md from `templates/PHASE_TRACKER_TEMPLATE.md`
|
||||
4. Fill all placeholders (marked with `{{VARIABLE}}`)
|
||||
|
||||
This creates:
|
||||
```
|
||||
[project-name]/
|
||||
├── CLAUDE.md # Project guidance (PARENT SYSTEM INTEGRATION included)
|
||||
├── README.md # Quick start + overview
|
||||
├── [folders based on project type]
|
||||
└── Coordination Hub/ # If complex project
|
||||
├── PROJECT_DEPENDENCIES.md
|
||||
├── INTEGRATION_CHECKLIST.md
|
||||
└── OUTPUT_LIBRARY.md
|
||||
```
|
||||
|
||||
**Note**: Full automation script (`create_project.sh`) is planned but not yet implemented. Current workflow uses templates + manual variable replacement.
|
||||
|
||||
---
|
||||
|
||||
### Step 4: Generate CLAUDE.md Content
|
||||
|
||||
**Use Template**:
|
||||
- Simple: `templates/CLAUDE_SIMPLE.md`
|
||||
- Complex: `templates/CLAUDE_COMPLEX.md`
|
||||
|
||||
**Required Sections** (ALL projects):
|
||||
1. **PROJECT IDENTITY** (name, type, status, created date, owner)
|
||||
2. **PROJECT MISSION** (purpose, core focus, expected outcomes)
|
||||
3. **SCOPE & BOUNDARIES** (in scope, out of scope)
|
||||
4. **PARENT SYSTEM INTEGRATION** ⚠️ CRITICAL
|
||||
- Project Memory Index Sync (path, when/how to update)
|
||||
- Operations Logging (format, actions to auto-log, examples)
|
||||
- Strategic Alignment Validation (OOBG check, UV check, Avatar targeting)
|
||||
- Cross-Project Intelligence (search related projects)
|
||||
5. **PROJECT STRUCTURE** (folder organization, key files)
|
||||
6. **EXPECTED DELIVERABLES** (phased if applicable)
|
||||
7. **SUCCESS CRITERIA** (how to measure completion)
|
||||
|
||||
**Additional Sections** (Complex projects):
|
||||
8. **AUTONOMOUS KNOWLEDGE ACCESS** (cross-project references, access commands)
|
||||
9. **COORDINATION WITH OTHER PROJECTS** (dependency chain, integration points)
|
||||
|
||||
**Populate Variables**:
|
||||
- Replace `{{PROJECT_NAME}}` with actual name
|
||||
- Replace `{{PROJECT_PURPOSE}}` with purpose from Step 1
|
||||
- Replace `{{DELIVERABLES}}` with list from Step 1
|
||||
- Replace `{{UPSTREAM_DEPS}}` and `{{DOWNSTREAM_DEPS}}` with projects from Step 1 (if complex)
|
||||
- Replace `{{AVATARS}}` with avatars from Step 1
|
||||
- Add current date in `{{CREATED_DATE}}`
|
||||
- Replace `{{PHASE_TRACKER_SECTION}}` with:
|
||||
- If multi-phase: "**This is a multi-phase project**. See `PHASE_TRACKER.md` for phase timeline, completion criteria, and proactive reminders.\n\n**Current Phase**: [Phase 1 name]\n**Next Milestone**: [Phase 1 completion]\n\n**Manual Check**: Say 'Check phase tracker' anytime for status update."
|
||||
- If single-phase: "**This is a single-phase project**. No phase tracker needed."
|
||||
|
||||
---
|
||||
|
||||
### Step 5: Generate README.md Content
|
||||
|
||||
**Use Template**: `templates/README.md`
|
||||
|
||||
**Required Sections**:
|
||||
1. **Project Title + Overview** (1 paragraph)
|
||||
2. **Quick Start** (how to begin working on this project)
|
||||
3. **Context** (why this project exists, what problem it solves)
|
||||
4. **Key Deliverables** (checklist format)
|
||||
5. **Related Projects** (if complex project)
|
||||
6. **Timeline** (if applicable)
|
||||
7. **Success Criteria**
|
||||
|
||||
**Keep it Concise**: Max 200 lines. README is for quick orientation, CLAUDE.md has details.
|
||||
|
||||
---
|
||||
|
||||
### Step 6: Generate PHASE_TRACKER.md (If Multi-Phase Project)
|
||||
|
||||
**Skip This Step If**: Single-phase project (no phases suggested/accepted in Step 1)
|
||||
|
||||
**If Multi-Phase Project**:
|
||||
|
||||
**Location**: `Active Projects/_Incubator/[project-name]/PHASE_TRACKER.md`
|
||||
|
||||
**Use Template**: `templates/PHASE_TRACKER_TEMPLATE.md`
|
||||
|
||||
**Populate Variables**:
|
||||
- `{{PROJECT_NAME}}`, `{{PROJECT_TITLE}}`, `{{CREATED_DATE}}` - From Step 1
|
||||
- For each phase (1-3):
|
||||
- `{{PHASE_N_NAME}}` - Phase name (e.g., "Setup & Test", "Validation & Refinement")
|
||||
- `{{PHASE_N_GOAL}}` - What this phase accomplishes
|
||||
- `{{PHASE_N_DURATION}}` - Time estimate (e.g., "4 weeks", "1 week")
|
||||
- `{{PHASE_N_TARGET_DATES}}` - Date range (calculate from project start + duration)
|
||||
- `{{PHASE_N_CRITERIA}}` - Completion criteria (suggest based on deliverables)
|
||||
- `{{PHASE_N_DELIVERABLES}}` - Phase-specific deliverables checklist
|
||||
- `{{PHASE_N_REMINDER_LOGIC}}` - How Claude checks weekly
|
||||
- `{{PHASE_N_TRANSITION_TRIGGER}}` - When to prompt next phase
|
||||
- `{{PHASE_N_NEXT_TRIGGER}}` - Date or criteria
|
||||
- `{{PHASE_N_CHECK_LOGIC}}` - How to validate completion
|
||||
- `{{PHASE_N_SUCCESS_INDICATORS}}` - What signals success
|
||||
- `{{PHASE_N_SUCCESS_DEFINITION}}` - Overall phase success
|
||||
- `{{PROJECT_COMPLETION_DEFINITION}}` - What "project complete" means
|
||||
- `{{OVERALL_SUCCESS_DEFINITION}}` - Final success definition
|
||||
- `{{NEXT_CHECK_DATE}}` - Calculate (project start + 1 week)
|
||||
|
||||
**Default Phase Structure** (if user accepts suggestion):
|
||||
|
||||
**Phase 1**: Setup & Test / MVP / Research & Planning (2-4 weeks)
|
||||
- Goal: Create system, test basic functionality, validate approach
|
||||
- Criteria: Core deliverables complete, basic testing done
|
||||
|
||||
**Phase 2**: Validation & Refinement / Production Rollout / Build & Test (1-2 weeks)
|
||||
- Goal: Review Phase 1 results, refine approach, confirm effectiveness
|
||||
- Criteria: Patterns identified, template/system refined, frequency/scope confirmed
|
||||
|
||||
**Phase 3**: Institutionalize / Scale / Deploy (1 week)
|
||||
- Goal: Promote to production, document final workflow, mark production-ready
|
||||
- Criteria: Integrated into root CLAUDE.md, added to registries, sustainable
|
||||
|
||||
**Proactive Reminder Example**:
|
||||
```
|
||||
Phase 1 Reminder Logic:
|
||||
- Weekly: Check if [X weeks] passed OR [N deliverables] complete
|
||||
- Transition: After [criteria met] OR [deadline] → "Ready for Phase 2?"
|
||||
|
||||
Phase 2 Reminder Logic:
|
||||
- After Phase 1 complete → Prompt immediately
|
||||
- After Phase 2 tasks done → "Ready for Phase 3?"
|
||||
|
||||
Phase 3 Reminder Logic:
|
||||
- After Phase 2 complete → Prompt immediately
|
||||
- After Phase 3 tasks done → "Project complete!"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Step 7: Create Active Projects Index Entry
|
||||
|
||||
**Location**: `Project Memory/Active Projects Index/[project-name]-index.md`
|
||||
|
||||
**Use Template**: `templates/PROJECT_INDEX.md`
|
||||
|
||||
**Required Content** (YAML frontmatter + sections):
|
||||
```yaml
|
||||
---
|
||||
project_id: "incubator-[project-name]"
|
||||
title: "[Project Title]"
|
||||
project_type: "incubator-program"
|
||||
status: "incubating"
|
||||
date_created: "YYYY-MM-DD"
|
||||
date_modified: "YYYY-MM-DD"
|
||||
folder_path: "Active Projects/_Incubator/[project-name]"
|
||||
tags: ["tag1", "tag2", "tag3"]
|
||||
strategic_alignment:
|
||||
oobg_relevance: "[How this serves OOBG]"
|
||||
unique_vehicle_fit: "[How this leverages YouTube + CCGG community]"
|
||||
avatar_targets: ["Avatar1", "Avatar2"]
|
||||
|
||||
# NEW: Dependency tracking (from Step 5)
|
||||
dependencies:
|
||||
blocks: [] # Projects that BLOCK this one (must complete first)
|
||||
blocked_by: [] # Projects this one BLOCKS (waiting for this)
|
||||
related_parallel: [] # Connected but not blocking
|
||||
|
||||
dependency_status:
|
||||
is_blocked: false # Auto-calculated from blocks[]
|
||||
blocking_count: 0 # Auto-calculated from blocked_by[]
|
||||
ready_to_start: true # Auto-calculated
|
||||
|
||||
last_sync: "YYYY-MM-DD (Project creation)"
|
||||
---
|
||||
|
||||
## Current Status
|
||||
[Project status description]
|
||||
|
||||
## Key Deliverables
|
||||
[Checklist of deliverables]
|
||||
|
||||
## Last Activity
|
||||
[Most recent work]
|
||||
|
||||
## Quick Access
|
||||
[Links to project folder and key files]
|
||||
```
|
||||
|
||||
**Populate with Data from Step 1**
|
||||
|
||||
---
|
||||
|
||||
### Step 7: Create Coordination Hub (Complex Projects Only)
|
||||
|
||||
**If Simple Project**: Skip this step.
|
||||
|
||||
**If Complex Project**: Create 3 coordination files:
|
||||
|
||||
#### PROJECT_DEPENDENCIES.md
|
||||
**Purpose**: Track what this project needs from/provides to other projects
|
||||
|
||||
**Use Template**: `templates/coordination/PROJECT_DEPENDENCIES.md`
|
||||
|
||||
**Populate**:
|
||||
- Upstream dependencies (projects this depends on)
|
||||
- Downstream dependencies (projects that depend on this)
|
||||
- Integration checkpoints
|
||||
- Blocker tracking section
|
||||
|
||||
#### INTEGRATION_CHECKLIST.md
|
||||
**Purpose**: Ensure all dependencies met before execution/handoff
|
||||
|
||||
**Use Template**: `templates/coordination/INTEGRATION_CHECKLIST.md`
|
||||
|
||||
**Populate**:
|
||||
- Pre-requisites from upstream projects
|
||||
- Execution checklist (this project's phases)
|
||||
- Post-implementation checklist (handoffs to downstream)
|
||||
- Validation criteria
|
||||
|
||||
#### OUTPUT_LIBRARY.md
|
||||
**Purpose**: Catalog deliverables for other projects to reference
|
||||
|
||||
**Use Template**: `templates/coordination/OUTPUT_LIBRARY.md`
|
||||
|
||||
**Populate**:
|
||||
- List expected outputs with status (PENDING/IN PROGRESS/COMPLETE)
|
||||
- Link to files when created
|
||||
- Note which projects consume each output
|
||||
|
||||
---
|
||||
|
||||
### Step 8: Log Project Creation
|
||||
|
||||
**Auto-log to operations_log.txt**:
|
||||
|
||||
```
|
||||
[YYYY-MM-DD HH:MM:SS] - CREATE - [project-name] - New incubator project created. [Simple/Complex] structure. [Key context]. Deliverables: [list]. Dependencies: [if complex].
|
||||
```
|
||||
|
||||
**Example**:
|
||||
```
|
||||
[2025-10-29 14:30:00] - CREATE - member-retention-sequences - New incubator project created. Simple structure. Email sequences to re-engage churned members. Deliverables: 5 email templates, 3 DM scripts, retention playbook.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Step 9: Validate All Mechanisms Implemented
|
||||
|
||||
**Run Checklist** (automated validation):
|
||||
|
||||
```bash
|
||||
bash scripts/validate_project.sh [project-name]
|
||||
```
|
||||
|
||||
**Manual Checklist** (if script unavailable):
|
||||
- [ ] CLAUDE.md exists with PARENT SYSTEM INTEGRATION section
|
||||
- [ ] PARENT SYSTEM INTEGRATION has all 4 sub-sections:
|
||||
- [ ] Project Memory Index Sync
|
||||
- [ ] Operations Logging
|
||||
- [ ] Strategic Alignment Validation
|
||||
- [ ] Cross-Project Intelligence
|
||||
- [ ] CLAUDE.md has MULTI-PHASE PROJECT TRACKER section with appropriate text
|
||||
- [ ] README.md exists with Quick Start section
|
||||
- [ ] Active Projects Index entry created
|
||||
- [ ] operations_log.txt entry added
|
||||
- [ ] Folder structure matches project complexity (simple vs complex)
|
||||
- [ ] If complex: Coordination Hub created with 3 files
|
||||
- [ ] If multi-phase: PHASE_TRACKER.md created and populated
|
||||
- [ ] All template variables replaced (no `{{PLACEHOLDER}}` remaining)
|
||||
|
||||
**If any checks fail**: Fix before proceeding.
|
||||
|
||||
---
|
||||
|
||||
### Step 10: Report Completion
|
||||
|
||||
**Generate Summary Report**:
|
||||
|
||||
```
|
||||
✅ Project Created: [project-name]
|
||||
|
||||
**Location**: Active Projects/_Incubator/[project-name]/
|
||||
**Complexity**: [Simple/Complex]
|
||||
**Multi-Phase**: [Yes (3 phases) / No (single-phase)]
|
||||
**Purpose**: [One-sentence purpose]
|
||||
|
||||
**Files Created**:
|
||||
- CLAUDE.md (with PARENT SYSTEM INTEGRATION ✓)
|
||||
- README.md
|
||||
- [If multi-phase] PHASE_TRACKER.md (Phase 1: [name], Phase 2: [name], Phase 3: [name])
|
||||
- [List other files/folders]
|
||||
|
||||
**Index Entry**: Project Memory/Active Projects Index/[project-name]-index.md ✓
|
||||
**Operations Log**: Logged at [timestamp] ✓
|
||||
|
||||
**Phase Tracker** (if multi-phase):
|
||||
- Current Phase: Phase 1 ([name])
|
||||
- Next Check: [date] (weekly during strategic planning)
|
||||
- Manual Check: Say "Check phase tracker [project-name]" anytime
|
||||
|
||||
**Next Steps**:
|
||||
1. Review CLAUDE.md for project-specific guidance
|
||||
2. [If multi-phase] Review PHASE_TRACKER.md for phase timeline
|
||||
3. Begin work on first deliverable: [first item from Step 1]
|
||||
4. Update index after major progress
|
||||
|
||||
**Quick Access**: [Link to project folder]
|
||||
```
|
||||
|
||||
**Present to Daron** for confirmation before moving on.
|
||||
|
||||
---
|
||||
|
||||
## Templates Reference
|
||||
|
||||
All templates are in `templates/` folder:
|
||||
|
||||
**Core Templates**:
|
||||
- `CLAUDE_SIMPLE.md` - Standard project CLAUDE.md (with PARENT SYSTEM INTEGRATION)
|
||||
- `CLAUDE_COMPLEX.md` - Complex project CLAUDE.md (adds cross-project coordination)
|
||||
- `README.md` - Standard README structure
|
||||
- `PROJECT_INDEX.md` - Active Projects Index entry template
|
||||
|
||||
**Coordination Templates** (complex projects only):
|
||||
- `coordination/PROJECT_DEPENDENCIES.md`
|
||||
- `coordination/INTEGRATION_CHECKLIST.md`
|
||||
- `coordination/OUTPUT_LIBRARY.md`
|
||||
|
||||
**See**: [templates/README.md](templates/README.md) for template usage guide
|
||||
|
||||
---
|
||||
|
||||
## Scripts Reference
|
||||
|
||||
**create_project.sh** - Automates project structure creation
|
||||
```bash
|
||||
bash scripts/create_project.sh [project-name] [simple|complex]
|
||||
```
|
||||
|
||||
**validate_project.sh** - Validates all mechanisms implemented
|
||||
```bash
|
||||
bash scripts/validate_project.sh [project-name]
|
||||
```
|
||||
|
||||
**See**: [scripts/README.md](scripts/README.md) for script documentation
|
||||
|
||||
---
|
||||
|
||||
## Common Scenarios
|
||||
|
||||
### Scenario 1: Simple Research Project
|
||||
**Example**: "Create project to research Dream 100 strategies"
|
||||
|
||||
**Workflow**:
|
||||
1. Name: `dream-100-research`
|
||||
2. Purpose: "Research and document Dream 100 implementation strategies for CCGG traffic growth"
|
||||
3. Coordination: NO (simple project)
|
||||
4. Deliverables: Research document, implementation plan, resource list
|
||||
5. Avatars: All (traffic benefits everyone)
|
||||
6. Create → Simple structure
|
||||
7. Validate → Done
|
||||
|
||||
**Time**: 10-15 minutes
|
||||
|
||||
---
|
||||
|
||||
### Scenario 2: Complex Strategic Project
|
||||
**Example**: "Create project for CCGG offers and pricing strategy"
|
||||
|
||||
**Workflow**:
|
||||
1. Name: `ccgg-offers-pricing`
|
||||
2. Purpose: "Design CCGG pricing structure and offer ladder to maximize revenue per customer"
|
||||
3. Coordination: YES
|
||||
- Depends on: hormozi-money-models (frameworks), claude-code-business-os (offer ladder)
|
||||
- Feeds into: member-onboarding-ascension (upgrade sequences), retention-reengagement (win-back pricing)
|
||||
4. Deliverables: Tier definitions, pricing structure, implementation plan, annual member presentation
|
||||
5. Avatars: All avatars
|
||||
6. Create → Complex structure (with Coordination Hub)
|
||||
7. Populate dependency maps
|
||||
8. Validate → Done
|
||||
|
||||
**Time**: 20-30 minutes
|
||||
|
||||
---
|
||||
|
||||
## Validation Failures & Fixes
|
||||
|
||||
**Problem**: "PARENT SYSTEM INTEGRATION section missing"
|
||||
**Fix**: Add section from `templates/CLAUDE_SIMPLE.md` lines 40-120
|
||||
|
||||
**Problem**: "Template variables not replaced ({{PROJECT_NAME}} still present)"
|
||||
**Fix**: Search for `{{` and replace all placeholders with actual values
|
||||
|
||||
**Problem**: "Operations log entry missing"
|
||||
**Fix**: Add entry manually:
|
||||
```
|
||||
echo "[$(date +%Y-%m-%d\ %H:%M:%S)] - CREATE - [project-name] - [description]" >> "operations_log.txt"
|
||||
```
|
||||
|
||||
**Problem**: "Active Projects Index missing strategic_alignment section"
|
||||
**Fix**: Add to YAML frontmatter:
|
||||
```yaml
|
||||
strategic_alignment:
|
||||
oobg_relevance: "[description]"
|
||||
unique_vehicle_fit: "[description]"
|
||||
avatar_targets: ["avatar1"]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Important Notes
|
||||
|
||||
### On PARENT SYSTEM INTEGRATION
|
||||
⚠️ **CRITICAL**: This section is **REQUIRED** in every project CLAUDE.md. It is the integration point with CCGG Business Operations.
|
||||
|
||||
**Why it matters**:
|
||||
- Enables automatic operations logging
|
||||
- Keeps Project Memory Index in sync
|
||||
- Validates strategic alignment
|
||||
- Enables cross-project intelligence
|
||||
|
||||
**If forgotten**: Project will be orphaned from CCGG Business Operations system.
|
||||
|
||||
### On Complexity Assessment
|
||||
**Default to Simple** unless clear multi-project coordination is needed.
|
||||
|
||||
**Indicators of Complex Project**:
|
||||
- Depends on outputs from 2+ other projects
|
||||
- 2+ other projects depend on this project's outputs
|
||||
- Strategic planning (affects multiple business areas)
|
||||
- Integration/coordination is core to the project
|
||||
|
||||
**Indicators of Simple Project**:
|
||||
- Self-contained work
|
||||
- Standalone deliverables
|
||||
- No handoffs to other projects required
|
||||
- Research or single-purpose tool
|
||||
|
||||
**When in doubt**: Ask Daron, "Will this project need to coordinate with other active projects?"
|
||||
|
||||
---
|
||||
|
||||
## Success Criteria
|
||||
|
||||
**Project creation is successful when**:
|
||||
1. All validation checks pass (Step 9)
|
||||
2. Daron can open the project and immediately understand:
|
||||
- What it does
|
||||
- What mechanisms are available
|
||||
- How to get started
|
||||
3. PARENT SYSTEM INTEGRATION is fully implemented
|
||||
4. Future Claude sessions can find this project via Active Projects Index search
|
||||
|
||||
**Project creation has FAILED if**:
|
||||
- Any mechanism is missing (especially PARENT SYSTEM INTEGRATION)
|
||||
- Template variables not replaced
|
||||
- Daron has to manually add standard components
|
||||
- Operations log entry missing
|
||||
|
||||
---
|
||||
|
||||
## Additional Resources
|
||||
|
||||
**For detailed mechanism specifications**, see:
|
||||
- [references/mechanism_specifications.md](references/mechanism_specifications.md) - Complete templates, variable replacement guide, and mechanism requirements
|
||||
|
||||
**For template usage**, see:
|
||||
- [templates/README.md](templates/README.md) - Template selection guide and variable documentation
|
||||
- [templates/CLAUDE_SIMPLE.md](templates/CLAUDE_SIMPLE.md) - Standard project template
|
||||
- templates/CLAUDE_COMPLEX.md - Complex project template (planned for future - use SIMPLE template + Coordination Hub for now)
|
||||
|
||||
**For validation scripts**, see:
|
||||
- [scripts/README.md](scripts/README.md) - Script documentation and usage examples
|
||||
- [scripts/validate_project.py](scripts/validate_project.py) - Python validation script (recommended)
|
||||
- [scripts/validate_project.sh](scripts/validate_project.sh) - Bash validation script (legacy)
|
||||
|
||||
---
|
||||
|
||||
## Version History
|
||||
|
||||
**v1.0.0** (2025-10-29)
|
||||
- Initial release
|
||||
- Simple and complex project support
|
||||
- Full PARENT SYSTEM INTEGRATION enforcement
|
||||
- Automated validation with Python script
|
||||
- Coordination Hub for complex projects
|
||||
- Progressive disclosure via references/
|
||||
|
||||
---
|
||||
|
||||
**Created with Skills Factory** - Ensures every CCGG Business Operations project is created correctly
|
||||
282
skills/project-creator/references/mechanism_specifications.md
Normal file
282
skills/project-creator/references/mechanism_specifications.md
Normal file
@@ -0,0 +1,282 @@
|
||||
# CCGG Business Operations Mechanism Specifications
|
||||
|
||||
**Purpose**: Detailed specifications for each mechanism that must be implemented in CCGG Business Operations sub-projects.
|
||||
|
||||
**Source of Truth**: `System Documentation/CCGG_MECHANISMS_REGISTRY.md` (in CCGG Business Operations root)
|
||||
|
||||
**Last Synced**: 2025-10-29
|
||||
|
||||
---
|
||||
|
||||
## Mechanism 1: PARENT SYSTEM INTEGRATION Section
|
||||
|
||||
**Status**: REQUIRED (All projects)
|
||||
|
||||
### Required Location
|
||||
CLAUDE.md (typically after SCOPE & BOUNDARIES section)
|
||||
|
||||
### Complete Template
|
||||
|
||||
```markdown
|
||||
## PARENT SYSTEM INTEGRATION
|
||||
|
||||
**This is a sub-project of CCGG Business Operations**
|
||||
|
||||
### Project Memory Index Sync
|
||||
|
||||
**Your Project Index**: `../../../Project Memory/Active Projects Index/{{PROJECT_NAME}}-index.md`
|
||||
|
||||
**When to Update**:
|
||||
- After completing major deliverable
|
||||
- When project status changes
|
||||
- After significant progress (weekly recommended)
|
||||
|
||||
**How to Update**:
|
||||
1. Read your index file
|
||||
2. Update: Current Status, Key Deliverables, Last Activity
|
||||
3. Update date_modified and last_sync timestamps
|
||||
4. Offer to log in operations_log.txt
|
||||
|
||||
### Operations Logging
|
||||
|
||||
**Location**: `../../../operations_log.txt`
|
||||
|
||||
**Format**: `[YYYY-MM-DD HH:MM:SS] - [ACTION] - {{PROJECT_NAME}} - [details]`
|
||||
|
||||
**Actions to Auto-Log** (without asking):
|
||||
- CREATE: New deliverables, documents, implementations
|
||||
- UPDATE: Revisions to key outputs
|
||||
- COMPLETE: Phase completions, deliverable handoffs
|
||||
- SYSTEM_UPGRADE: Infrastructure improvements
|
||||
- SYNC: Project index updates
|
||||
|
||||
**Behavior**: Auto-log major actions WITHOUT prompting user
|
||||
|
||||
### Strategic Alignment Validation
|
||||
|
||||
**Reference**: `../../../AI Growth Engine/Knowledge Base/Strategy_for_CCGG_AI_Leaders_Business.md`
|
||||
|
||||
**Three Validation Checks**:
|
||||
|
||||
1. **OOBG Check**: Does this help coaches/consultants monetize with AI?
|
||||
2. **Unique Vehicle Check**: Does this leverage YouTube + CCGG paid community?
|
||||
3. **Avatar Targeting**: Which specific customer avatars benefit from this?
|
||||
|
||||
**When to Validate**: Project creation, phase transitions, strategic reviews
|
||||
|
||||
### Cross-Project Intelligence
|
||||
|
||||
**Path**: `../../../Project Memory/Active Projects Index/`
|
||||
|
||||
**Behavior**: When asked "what related projects exist?", search Active Projects Index folder for similar work
|
||||
|
||||
**Use Cases**: Find similar work, identify dependencies, discover synergies
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mechanism 2: Active Projects Index Entry
|
||||
|
||||
**Status**: REQUIRED (All projects)
|
||||
|
||||
### File Location
|
||||
`Project Memory/Active Projects Index/{{PROJECT_NAME}}-index.md`
|
||||
|
||||
### Complete Template
|
||||
|
||||
```yaml
|
||||
---
|
||||
project_id: "incubator-{{PROJECT_NAME}}" OR "active-{{PROJECT_NAME}}"
|
||||
title: "{{PROJECT_TITLE}}"
|
||||
project_type: "incubator-program" OR "active-program"
|
||||
status: "incubating" OR "active" OR "paused" OR "completed"
|
||||
date_created: "YYYY-MM-DD"
|
||||
date_modified: "YYYY-MM-DD"
|
||||
folder_path: "Active Projects/_Incubator/{{PROJECT_NAME}}" OR "Active Projects/{{PROJECT_TITLE}}"
|
||||
tags: ["tag1", "tag2", "tag3"]
|
||||
strategic_alignment:
|
||||
oobg_relevance: "How this helps coaches monetize with AI"
|
||||
unique_vehicle_fit: "How this leverages YouTube + CCGG community"
|
||||
avatar_targets: ["avatar1", "avatar2"]
|
||||
last_sync: "YYYY-MM-DD HH:MM:SS (context: initial creation)"
|
||||
---
|
||||
|
||||
## Current Status
|
||||
|
||||
[Current state description - initially "Incubating - exploring viability"]
|
||||
|
||||
## Key Deliverables
|
||||
|
||||
[ ] Deliverable 1
|
||||
[ ] Deliverable 2
|
||||
[ ] Deliverable 3
|
||||
|
||||
## Last Activity
|
||||
|
||||
[Most recent work with date - initially "Created project structure"]
|
||||
|
||||
## Quick Access
|
||||
|
||||
- Full project: [Active Projects/_Incubator/{{PROJECT_NAME}}](../../../Active Projects/_Incubator/{{PROJECT_NAME}})
|
||||
- CLAUDE.md: [CLAUDE.md](../../../Active Projects/_Incubator/{{PROJECT_NAME}}/CLAUDE.md)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mechanism 3: Operations Logging (Centralized)
|
||||
|
||||
**Status**: REQUIRED (All projects log here)
|
||||
|
||||
### File Location
|
||||
`operations_log.txt` (root of CCGG Business Operations)
|
||||
|
||||
### Format
|
||||
```
|
||||
[YYYY-MM-DD HH:MM:SS] - [ACTION] - [project-name] - [details]
|
||||
```
|
||||
|
||||
### Standard Actions
|
||||
- **CREATE**: New projects, deliverables, systems
|
||||
- **UPDATE**: Major revisions
|
||||
- **COMPLETE**: Phase/project completions
|
||||
- **GRADUATE**: Incubator → Active promotion
|
||||
- **ARCHIVE**: Project completion/deprecation
|
||||
- **SYNC**: Index synchronization
|
||||
- **SYSTEM_UPGRADE**: Business OS infrastructure improvements
|
||||
- **DAILY_ROADMAP**: Daily execution roadmap generation
|
||||
- **STRATEGIC_PLANNING**: Strategic planning sessions
|
||||
|
||||
### Behavior
|
||||
Automatic logging (no prompt) for major actions
|
||||
|
||||
---
|
||||
|
||||
## Mechanism 9: Coordination Hub (Complex Projects Only)
|
||||
|
||||
**Status**: OPTIONAL (Only for complex projects with dependencies)
|
||||
|
||||
### When to Use
|
||||
Projects with:
|
||||
- 2+ upstream dependencies (what this project needs from others)
|
||||
- 2+ downstream dependencies (what other projects need from this)
|
||||
- Strategic planning projects requiring integration validation
|
||||
- Coordination/integration projects
|
||||
|
||||
### Required Files
|
||||
|
||||
#### File 1: PROJECT_DEPENDENCIES.md
|
||||
|
||||
```markdown
|
||||
# Project Dependencies - {{PROJECT_TITLE}}
|
||||
|
||||
## Upstream Dependencies (What We Need)
|
||||
|
||||
### From [Project Name]
|
||||
- **Dependency**: [What we need]
|
||||
- **Status**: PENDING | IN PROGRESS | COMPLETE
|
||||
- **Impact if Delayed**: [Description]
|
||||
- **Owner**: [Responsible party]
|
||||
|
||||
## Downstream Dependencies (What Others Need from Us)
|
||||
|
||||
### To [Project Name]
|
||||
- **Deliverable**: [What they need]
|
||||
- **Status**: PENDING | IN PROGRESS | COMPLETE
|
||||
- **Due Date**: YYYY-MM-DD
|
||||
- **Owner**: [Responsible party]
|
||||
|
||||
## Integration Checkpoints
|
||||
|
||||
- [ ] Checkpoint 1 (Date: YYYY-MM-DD)
|
||||
- [ ] Checkpoint 2 (Date: YYYY-MM-DD)
|
||||
|
||||
## Current Blockers
|
||||
|
||||
**None** OR list blockers with mitigation plans
|
||||
```
|
||||
|
||||
#### File 2: INTEGRATION_CHECKLIST.md
|
||||
|
||||
```markdown
|
||||
# Integration Checklist - {{PROJECT_TITLE}}
|
||||
|
||||
## Phase 1: Pre-Requisites (Before We Start)
|
||||
|
||||
- [ ] Dependency from [Project] received
|
||||
- [ ] Dependency from [Project] validated
|
||||
- [ ] All upstream deliverables confirmed
|
||||
|
||||
## Phase 2: Execution (This Project's Work)
|
||||
|
||||
- [ ] Deliverable 1
|
||||
- [ ] Deliverable 2
|
||||
- [ ] Integration test with upstream dependencies
|
||||
|
||||
## Phase 3: Post-Implementation (Handoff to Downstream)
|
||||
|
||||
- [ ] Deliverable to [Project] completed
|
||||
- [ ] Deliverable to [Project] validated
|
||||
- [ ] All downstream consumers notified
|
||||
|
||||
## Validation Criteria
|
||||
|
||||
**Phase 1 → 2**: [Criteria]
|
||||
**Phase 2 → 3**: [Criteria]
|
||||
|
||||
## Risks & Mitigation
|
||||
|
||||
**Risk 1**: [Description]
|
||||
- Mitigation: [Plan]
|
||||
|
||||
**Risk 2**: [Description]
|
||||
- Mitigation: [Plan]
|
||||
```
|
||||
|
||||
#### File 3: OUTPUT_LIBRARY.md
|
||||
|
||||
```markdown
|
||||
# Output Library - {{PROJECT_TITLE}}
|
||||
|
||||
## Deliverables Produced by This Project
|
||||
|
||||
### Output 1: [Name]
|
||||
- **Status**: PENDING | IN PROGRESS | COMPLETE
|
||||
- **File Link**: [path when complete]
|
||||
- **Consumer Projects**: [Project 1], [Project 2]
|
||||
- **Description**: [What this output is]
|
||||
|
||||
### Output 2: [Name]
|
||||
- **Status**: PENDING | IN PROGRESS | COMPLETE
|
||||
- **File Link**: [path when complete]
|
||||
- **Consumer Projects**: [Project 1]
|
||||
- **Description**: [What this output is]
|
||||
|
||||
## How to Use This Library
|
||||
|
||||
Other projects reference this file to track when deliverables are ready for integration.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Variable Replacement Guide
|
||||
|
||||
When creating projects, replace these variables:
|
||||
|
||||
- `{{PROJECT_NAME}}`: Hyphen-case identifier (e.g., "ccgg-offers-pricing")
|
||||
- `{{PROJECT_TITLE}}`: Human-readable title (e.g., "CCGG Offers & Pricing Model")
|
||||
- `{{PROJECT_TYPE}}`: "incubator-program" or "active-program"
|
||||
- `{{PROJECT_PURPOSE}}`: 1-2 sentence purpose
|
||||
- `{{CREATED_DATE}}`: YYYY-MM-DD format
|
||||
- `{{CORE_FOCUS_ITEMS}}`: Bullet list of focus areas
|
||||
- `{{IN_SCOPE_ITEMS}}`: What's included in project
|
||||
- `{{OUT_OF_SCOPE_ITEMS}}`: What's explicitly excluded
|
||||
- `{{OOBG_ALIGNMENT}}`: How this serves OOBG (coaches monetizing AI)
|
||||
- `{{UV_ALIGNMENT}}`: How this leverages Unique Vehicle (YouTube + CCGG)
|
||||
- `{{AVATAR_TARGETING}}`: Which avatars benefit
|
||||
- `{{RELATED_PROJECTS}}`: Links to related projects
|
||||
- `{{FOLDER_STRUCTURE}}`: Project folder tree
|
||||
|
||||
---
|
||||
|
||||
**Maintained By**: CCGG Business Operations system
|
||||
**Version**: v1.0 (synced with CCGG_MECHANISMS_REGISTRY.md)
|
||||
74
skills/project-creator/scripts/README.md
Normal file
74
skills/project-creator/scripts/README.md
Normal file
@@ -0,0 +1,74 @@
|
||||
# Project Creator Scripts
|
||||
|
||||
## validate_project.py
|
||||
|
||||
**RECOMMENDED**: Python validation script (cross-platform, no bash required)
|
||||
|
||||
Validates that a CCGG Business Operations project has all required mechanisms.
|
||||
|
||||
**Usage**:
|
||||
```bash
|
||||
py scripts/validate_project.py <project-name>
|
||||
```
|
||||
|
||||
**What it checks**:
|
||||
- Project folder exists
|
||||
- CLAUDE.md exists with PARENT SYSTEM INTEGRATION section
|
||||
- All 4 sub-sections present (Index Sync, Operations Logging, Strategic Alignment, Cross-Project Intelligence)
|
||||
- README.md exists
|
||||
- Active Projects Index entry exists
|
||||
- operations_log.txt entry exists
|
||||
- No template variables left unreplaced
|
||||
|
||||
**Exit codes**:
|
||||
- 0: Validation passed (or passed with warnings)
|
||||
- 1: Validation failed (errors found)
|
||||
|
||||
**Examples**:
|
||||
```bash
|
||||
py scripts/validate_project.py ccgg-offers-pricing
|
||||
py scripts/validate_project.py magnetic-content-os
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## validate_project.sh
|
||||
|
||||
**LEGACY**: Bash version of validation script (use validate_project.py instead)
|
||||
|
||||
Same functionality as validate_project.py, but requires bash shell (Git Bash or WSL on Windows).
|
||||
|
||||
**Usage**:
|
||||
```bash
|
||||
bash scripts/validate_project.sh <project-name>
|
||||
```
|
||||
|
||||
**Note**: Python version (validate_project.py) is preferred for cross-platform compatibility.
|
||||
|
||||
---
|
||||
|
||||
## create_project.py (Planned - Not Yet Implemented)
|
||||
|
||||
Automated project structure creation script.
|
||||
|
||||
**Planned usage**:
|
||||
```bash
|
||||
py scripts/create_project.py <project-name> --complexity <simple|complex>
|
||||
```
|
||||
|
||||
**Planned functionality**:
|
||||
- Prompt for project details (title, purpose, scope, etc.)
|
||||
- Assess project complexity (simple vs complex)
|
||||
- Create project folder structure
|
||||
- Copy appropriate template files
|
||||
- Replace template variables with user input
|
||||
- Create Active Projects Index entry
|
||||
- Log to operations_log.txt
|
||||
- Run validation
|
||||
- Report project creation summary
|
||||
|
||||
**Status**: Not implemented yet. For now, use manual creation workflow in SKILL.md.
|
||||
|
||||
---
|
||||
|
||||
**Development Note**: Scripts are being migrated from bash to Python for cross-platform compatibility. Python scripts can run on Windows, macOS, and Linux without requiring bash shell.
|
||||
158
skills/project-creator/scripts/validate_project.py
Normal file
158
skills/project-creator/scripts/validate_project.py
Normal file
@@ -0,0 +1,158 @@
|
||||
#!/usr/bin/env python3
|
||||
"""
|
||||
Validates that a CCGG Business Operations project has all required mechanisms
|
||||
|
||||
Usage:
|
||||
python validate_project.py <project-name>
|
||||
|
||||
Examples:
|
||||
python validate_project.py ccgg-offers-pricing
|
||||
python validate_project.py magnetic-content-os
|
||||
"""
|
||||
|
||||
import sys
|
||||
from pathlib import Path
|
||||
|
||||
|
||||
def validate_project(project_name):
|
||||
"""
|
||||
Validate a CCGG Business Operations project has all required mechanisms.
|
||||
|
||||
Args:
|
||||
project_name: Name of the project to validate
|
||||
|
||||
Returns:
|
||||
(errors, warnings) tuple with counts
|
||||
"""
|
||||
project_path = Path("Active Projects/_Incubator") / project_name
|
||||
index_path = Path("Project Memory/Active Projects Index") / f"{project_name}-index.md"
|
||||
|
||||
print(f"[VALIDATING] project: {project_name}")
|
||||
print()
|
||||
|
||||
errors = 0
|
||||
warnings = 0
|
||||
|
||||
# Check 1: Project folder exists
|
||||
if not project_path.exists():
|
||||
print(f"[ERROR] Project folder not found: {project_path}")
|
||||
errors += 1
|
||||
else:
|
||||
print("[OK] Project folder exists")
|
||||
|
||||
# Check 2: CLAUDE.md exists
|
||||
claude_md = project_path / "CLAUDE.md"
|
||||
if not claude_md.exists():
|
||||
print("[ERROR] CLAUDE.md not found")
|
||||
errors += 1
|
||||
else:
|
||||
print("[OK] CLAUDE.md exists")
|
||||
|
||||
# Read CLAUDE.md content
|
||||
content = claude_md.read_text(encoding='utf-8')
|
||||
|
||||
# Check 2a: PARENT SYSTEM INTEGRATION section
|
||||
if "## PARENT SYSTEM INTEGRATION" not in content:
|
||||
print("[ERROR] PARENT SYSTEM INTEGRATION section missing in CLAUDE.md")
|
||||
errors += 1
|
||||
else:
|
||||
print("[OK] PARENT SYSTEM INTEGRATION section present")
|
||||
|
||||
# Check sub-sections
|
||||
if "### Project Memory Index Sync" not in content:
|
||||
print("[WARNING] Project Memory Index Sync sub-section missing")
|
||||
warnings += 1
|
||||
|
||||
if "### Operations Logging" not in content:
|
||||
print("[WARNING] Operations Logging sub-section missing")
|
||||
warnings += 1
|
||||
|
||||
if "### Strategic Alignment Validation" not in content:
|
||||
print("[WARNING] Strategic Alignment Validation sub-section missing")
|
||||
warnings += 1
|
||||
|
||||
if "### Cross-Project Intelligence" not in content:
|
||||
print("[WARNING] Cross-Project Intelligence sub-section missing")
|
||||
warnings += 1
|
||||
|
||||
# Check 2b: Template variables replaced
|
||||
if "{{" in content:
|
||||
print("[WARNING] Template variables not replaced ({{ found)")
|
||||
warnings += 1
|
||||
|
||||
# Check 3: README.md exists
|
||||
readme = project_path / "README.md"
|
||||
if not readme.exists():
|
||||
print("[WARNING] README.md not found")
|
||||
warnings += 1
|
||||
else:
|
||||
print("[OK] README.md exists")
|
||||
|
||||
# Check 4: Active Projects Index exists
|
||||
if not index_path.exists():
|
||||
print(f"[ERROR] Active Projects Index not found: {index_path}")
|
||||
errors += 1
|
||||
else:
|
||||
print("[OK] Active Projects Index exists")
|
||||
|
||||
# Read index content
|
||||
index_content = index_path.read_text(encoding='utf-8')
|
||||
|
||||
# Check YAML frontmatter
|
||||
if not index_content.startswith("---"):
|
||||
print("[WARNING] YAML frontmatter missing in index")
|
||||
warnings += 1
|
||||
|
||||
if "strategic_alignment:" not in index_content:
|
||||
print("[WARNING] strategic_alignment missing in index")
|
||||
warnings += 1
|
||||
|
||||
# Check 5: Operations log entry
|
||||
ops_log = Path("operations_log.txt")
|
||||
if ops_log.exists():
|
||||
ops_content = ops_log.read_text(encoding='utf-8')
|
||||
if project_name not in ops_content:
|
||||
print(f"[WARNING] No operations_log.txt entry found for {project_name}")
|
||||
warnings += 1
|
||||
else:
|
||||
print("[OK] Operations log entry exists")
|
||||
else:
|
||||
print("[WARNING] operations_log.txt not found")
|
||||
warnings += 1
|
||||
|
||||
# Summary
|
||||
print()
|
||||
print("=" * 40)
|
||||
print("Validation Summary")
|
||||
print("=" * 40)
|
||||
print(f"Errors: {errors}")
|
||||
print(f"Warnings: {warnings}")
|
||||
print()
|
||||
|
||||
if errors == 0 and warnings == 0:
|
||||
print("[OK] Project validation PASSED")
|
||||
return 0
|
||||
elif errors == 0:
|
||||
print("[WARNING] Project validation passed with warnings")
|
||||
return 0
|
||||
else:
|
||||
print("[ERROR] Project validation FAILED")
|
||||
return 1
|
||||
|
||||
|
||||
def main():
|
||||
if len(sys.argv) != 2:
|
||||
print("Usage: python validate_project.py <project-name>")
|
||||
print()
|
||||
print("Examples:")
|
||||
print(" python validate_project.py ccgg-offers-pricing")
|
||||
print(" python validate_project.py magnetic-content-os")
|
||||
sys.exit(1)
|
||||
|
||||
project_name = sys.argv[1]
|
||||
exit_code = validate_project(project_name)
|
||||
sys.exit(exit_code)
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
main()
|
||||
123
skills/project-creator/scripts/validate_project.sh
Normal file
123
skills/project-creator/scripts/validate_project.sh
Normal file
@@ -0,0 +1,123 @@
|
||||
#!/bin/bash
|
||||
# Validates that a CCGG Business Operations project has all required mechanisms
|
||||
|
||||
PROJECT_NAME="$1"
|
||||
|
||||
if [ -z "$PROJECT_NAME" ]; then
|
||||
echo "Usage: bash validate_project.sh <project-name>"
|
||||
exit 1
|
||||
fi
|
||||
|
||||
PROJECT_PATH="Active Projects/_Incubator/$PROJECT_NAME"
|
||||
INDEX_PATH="Project Memory/Active Projects Index/${PROJECT_NAME}-index.md"
|
||||
|
||||
echo "🔍 Validating project: $PROJECT_NAME"
|
||||
echo ""
|
||||
|
||||
ERRORS=0
|
||||
WARNINGS=0
|
||||
|
||||
# Check 1: Project folder exists
|
||||
if [ ! -d "$PROJECT_PATH" ]; then
|
||||
echo "❌ ERROR: Project folder not found: $PROJECT_PATH"
|
||||
((ERRORS++))
|
||||
else
|
||||
echo "✅ Project folder exists"
|
||||
fi
|
||||
|
||||
# Check 2: CLAUDE.md exists
|
||||
if [ ! -f "$PROJECT_PATH/CLAUDE.md" ]; then
|
||||
echo "❌ ERROR: CLAUDE.md not found"
|
||||
((ERRORS++))
|
||||
else
|
||||
echo "✅ CLAUDE.md exists"
|
||||
|
||||
# Check 2a: PARENT SYSTEM INTEGRATION section
|
||||
if ! grep -q "## PARENT SYSTEM INTEGRATION" "$PROJECT_PATH/CLAUDE.md"; then
|
||||
echo "❌ ERROR: PARENT SYSTEM INTEGRATION section missing in CLAUDE.md"
|
||||
((ERRORS++))
|
||||
else
|
||||
echo "✅ PARENT SYSTEM INTEGRATION section present"
|
||||
|
||||
# Check sub-sections
|
||||
if ! grep -q "### Project Memory Index Sync" "$PROJECT_PATH/CLAUDE.md"; then
|
||||
echo "⚠️ WARNING: Project Memory Index Sync sub-section missing"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
|
||||
if ! grep -q "### Operations Logging" "$PROJECT_PATH/CLAUDE.md"; then
|
||||
echo "⚠️ WARNING: Operations Logging sub-section missing"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
|
||||
if ! grep -q "### Strategic Alignment Validation" "$PROJECT_PATH/CLAUDE.md"; then
|
||||
echo "⚠️ WARNING: Strategic Alignment Validation sub-section missing"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
|
||||
if ! grep -q "### Cross-Project Intelligence" "$PROJECT_PATH/CLAUDE.md"; then
|
||||
echo "⚠️ WARNING: Cross-Project Intelligence sub-section missing"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
fi
|
||||
|
||||
# Check 2b: Template variables replaced
|
||||
if grep -q "{{" "$PROJECT_PATH/CLAUDE.md"; then
|
||||
echo "⚠️ WARNING: Template variables not replaced ({{ found)"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
fi
|
||||
|
||||
# Check 3: README.md exists
|
||||
if [ ! -f "$PROJECT_PATH/README.md" ]; then
|
||||
echo "⚠️ WARNING: README.md not found"
|
||||
((WARNINGS++))
|
||||
else
|
||||
echo "✅ README.md exists"
|
||||
fi
|
||||
|
||||
# Check 4: Active Projects Index exists
|
||||
if [ ! -f "$INDEX_PATH" ]; then
|
||||
echo "❌ ERROR: Active Projects Index not found: $INDEX_PATH"
|
||||
((ERRORS++))
|
||||
else
|
||||
echo "✅ Active Projects Index exists"
|
||||
|
||||
# Check YAML frontmatter
|
||||
if ! grep -q "^---$" "$INDEX_PATH"; then
|
||||
echo "⚠️ WARNING: YAML frontmatter missing in index"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
|
||||
if ! grep -q "strategic_alignment:" "$INDEX_PATH"; then
|
||||
echo "⚠️ WARNING: strategic_alignment missing in index"
|
||||
((WARNINGS++))
|
||||
fi
|
||||
fi
|
||||
|
||||
# Check 5: Operations log entry
|
||||
if ! grep -q "$PROJECT_NAME" "operations_log.txt"; then
|
||||
echo "⚠️ WARNING: No operations_log.txt entry found for $PROJECT_NAME"
|
||||
((WARNINGS++))
|
||||
else
|
||||
echo "✅ Operations log entry exists"
|
||||
fi
|
||||
|
||||
echo ""
|
||||
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
|
||||
echo "Validation Summary"
|
||||
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
|
||||
echo "Errors: $ERRORS"
|
||||
echo "Warnings: $WARNINGS"
|
||||
echo ""
|
||||
|
||||
if [ $ERRORS -eq 0 ] && [ $WARNINGS -eq 0 ]; then
|
||||
echo "✅ Project validation PASSED"
|
||||
exit 0
|
||||
elif [ $ERRORS -eq 0 ]; then
|
||||
echo "⚠️ Project validation passed with warnings"
|
||||
exit 0
|
||||
else
|
||||
echo "❌ Project validation FAILED"
|
||||
exit 1
|
||||
fi
|
||||
208
skills/project-creator/templates/CLAUDE_COMPLEX.md
Normal file
208
skills/project-creator/templates/CLAUDE_COMPLEX.md
Normal file
@@ -0,0 +1,208 @@
|
||||
# CLAUDE.md - {{PROJECT_NAME}}
|
||||
|
||||
## PROJECT IDENTITY
|
||||
|
||||
**Project Name**: {{PROJECT_TITLE}}
|
||||
**Project Type**: {{PROJECT_TYPE}} (Complex - Multi-Project Coordination)
|
||||
**Status**: Incubating
|
||||
**Created**: {{CREATED_DATE}}
|
||||
**Owner**: Daron Vener
|
||||
|
||||
---
|
||||
|
||||
## PROJECT MISSION
|
||||
|
||||
{{PROJECT_PURPOSE}}
|
||||
|
||||
**Core Focus**:
|
||||
{{CORE_FOCUS_ITEMS}}
|
||||
|
||||
---
|
||||
|
||||
## SCOPE & BOUNDARIES
|
||||
|
||||
### IN SCOPE
|
||||
{{IN_SCOPE_ITEMS}}
|
||||
|
||||
### OUT OF SCOPE
|
||||
{{OUT_OF_SCOPE_ITEMS}}
|
||||
|
||||
---
|
||||
|
||||
## PARENT SYSTEM INTEGRATION
|
||||
|
||||
**This is a sub-project of CCGG Business Operations**
|
||||
|
||||
### Project Memory Index Sync
|
||||
|
||||
**Your Project Index**: `../../../Project Memory/Active Projects Index/{{PROJECT_NAME}}-index.md`
|
||||
|
||||
**When to Update** (PROACTIVELY):
|
||||
- After completing major deliverable
|
||||
- When project status changes (incubating → ready, paused, etc.)
|
||||
- After significant progress (weekly recommended during active work)
|
||||
|
||||
**How to Update**:
|
||||
1. Read `../../../Project Memory/Active Projects Index/{{PROJECT_NAME}}-index.md`
|
||||
2. Update: Current Status, Key Deliverables (mark completed items), Last Activity, date_modified, last_sync
|
||||
3. Offer to log in operations_log.txt
|
||||
|
||||
**Example Updates**:
|
||||
- "Completed deliverable: [specific output]"
|
||||
- "Phase [X] complete: [summary]"
|
||||
- "Status changed: incubating → ready for implementation"
|
||||
|
||||
---
|
||||
|
||||
### Operations Logging
|
||||
|
||||
**Location**: `../../../operations_log.txt`
|
||||
|
||||
**Auto-log** (AUTOMATICALLY, without asking): Major deliverables, milestones, decisions, phase completions, index updates
|
||||
|
||||
**Format**: `[YYYY-MM-DD HH:MM:SS] - [ACTION] - {{PROJECT_NAME}} - [details]`
|
||||
|
||||
**Actions to Auto-Log**:
|
||||
- **CREATE**: New deliverables, documents, implementations
|
||||
- **UPDATE**: Revisions to key outputs
|
||||
- **COMPLETE**: Phase completions, deliverable handoffs
|
||||
- **SYSTEM_UPGRADE**: Infrastructure improvements
|
||||
- **SYNC**: Project index updates
|
||||
|
||||
**Examples**:
|
||||
```
|
||||
[YYYY-MM-DD HH:MM:SS] - COMPLETE - {{PROJECT_NAME}} - [Deliverable name] complete. [Key details].
|
||||
[YYYY-MM-DD HH:MM:SS] - CREATE - {{PROJECT_NAME}} - [New output] created. [Purpose and context].
|
||||
[YYYY-MM-DD HH:MM:SS] - SYNC - {{PROJECT_NAME}} - Project index updated. Status: [current status].
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Strategic Alignment Validation
|
||||
|
||||
Reference `../../../AI Growth Engine/Knowledge Base/Strategy_for_CCGG_AI_Leaders_Business.md`
|
||||
|
||||
**OOBG Check**: Does this help coaches/consultants monetize with AI?
|
||||
{{OOBG_ALIGNMENT}}
|
||||
|
||||
**Unique Vehicle Check**: Does this leverage YouTube + CCGG paid community?
|
||||
{{UV_ALIGNMENT}}
|
||||
|
||||
**Avatar Targeting**: Which specific customer avatars benefit?
|
||||
{{AVATAR_TARGETING}}
|
||||
|
||||
---
|
||||
|
||||
### Cross-Project Intelligence
|
||||
|
||||
Search `../../../Project Memory/Active Projects Index/` for related projects when asked.
|
||||
|
||||
**Related Projects**:
|
||||
{{RELATED_PROJECTS}}
|
||||
|
||||
---
|
||||
|
||||
## AUTONOMOUS KNOWLEDGE ACCESS
|
||||
|
||||
**This is a complex project that coordinates with other active projects.**
|
||||
|
||||
### Cross-Project References
|
||||
|
||||
**Upstream Dependencies** (Projects this project needs):
|
||||
{{UPSTREAM_DEPENDENCIES}}
|
||||
|
||||
**Downstream Dependencies** (Projects that need this project's outputs):
|
||||
{{DOWNSTREAM_DEPENDENCIES}}
|
||||
|
||||
### Access Commands
|
||||
|
||||
**To find related project outputs**:
|
||||
- "Search Active Projects Index for [keyword]"
|
||||
- "Read [project-name]/Coordination Hub/OUTPUT_LIBRARY.md"
|
||||
- "What outputs does [project-name] provide?"
|
||||
|
||||
**To check integration status**:
|
||||
- "Read Coordination Hub/INTEGRATION_CHECKLIST.md"
|
||||
- "Are all upstream dependencies met?"
|
||||
- "Which downstream projects are blocked by this?"
|
||||
|
||||
---
|
||||
|
||||
## COORDINATION WITH OTHER PROJECTS
|
||||
|
||||
### Dependency Chain
|
||||
|
||||
{{DEPENDENCY_CHAIN_DESCRIPTION}}
|
||||
|
||||
### Integration Points
|
||||
|
||||
{{INTEGRATION_POINTS}}
|
||||
|
||||
### Coordination Hub
|
||||
|
||||
**Location**: `Coordination Hub/`
|
||||
|
||||
**Files**:
|
||||
- `PROJECT_DEPENDENCIES.md` - Upstream and downstream dependency tracking
|
||||
- `INTEGRATION_CHECKLIST.md` - Pre-requisites, execution, and post-implementation checklists
|
||||
- `OUTPUT_LIBRARY.md` - Catalog of deliverables for other projects to reference
|
||||
|
||||
**When to Update**:
|
||||
- **PROJECT_DEPENDENCIES.md**: When blockers change, dependencies met/unmet
|
||||
- **INTEGRATION_CHECKLIST.md**: After each phase, when handoffs complete
|
||||
- **OUTPUT_LIBRARY.md**: Whenever new deliverable created or status changes
|
||||
|
||||
---
|
||||
|
||||
## PROJECT STRUCTURE
|
||||
|
||||
```
|
||||
{{PROJECT_NAME}}/
|
||||
├── CLAUDE.md # This file - project guidance
|
||||
├── README.md # Project overview
|
||||
├── Coordination Hub/ # Cross-project coordination
|
||||
│ ├── PROJECT_DEPENDENCIES.md
|
||||
│ ├── INTEGRATION_CHECKLIST.md
|
||||
│ └── OUTPUT_LIBRARY.md
|
||||
{{FOLDER_STRUCTURE}}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## EXPECTED DELIVERABLES
|
||||
|
||||
{{DELIVERABLES_LIST}}
|
||||
|
||||
---
|
||||
|
||||
## MULTI-PHASE PROJECT TRACKER
|
||||
|
||||
{{PHASE_TRACKER_SECTION}}
|
||||
|
||||
---
|
||||
|
||||
## SUCCESS CRITERIA
|
||||
|
||||
### Project Success
|
||||
{{PROJECT_SUCCESS_CRITERIA}}
|
||||
|
||||
### Integration Success
|
||||
{{INTEGRATION_SUCCESS_CRITERIA}}
|
||||
|
||||
### Business Impact (Post-Implementation)
|
||||
{{BUSINESS_IMPACT_CRITERIA}}
|
||||
|
||||
---
|
||||
|
||||
## IMPORTANT REMINDERS
|
||||
|
||||
1. **Update Project Memory Index** after major deliverables
|
||||
2. **Log significant progress** to operations_log.txt
|
||||
3. **Validate strategic alignment** periodically (OOBG, UV, Avatars)
|
||||
4. **Check upstream dependencies** before starting phases (read Coordination Hub)
|
||||
5. **Update OUTPUT_LIBRARY.md** when deliverables complete (downstream projects need visibility)
|
||||
6. **Coordinate handoffs** to downstream projects (notify via operations_log.txt)
|
||||
|
||||
---
|
||||
|
||||
**Your mission**: {{MISSION_STATEMENT}}
|
||||
147
skills/project-creator/templates/CLAUDE_SIMPLE.md
Normal file
147
skills/project-creator/templates/CLAUDE_SIMPLE.md
Normal file
@@ -0,0 +1,147 @@
|
||||
# CLAUDE.md - {{PROJECT_NAME}}
|
||||
|
||||
## PROJECT IDENTITY
|
||||
|
||||
**Project Name**: {{PROJECT_TITLE}}
|
||||
**Project Type**: {{PROJECT_TYPE}}
|
||||
**Status**: Incubating
|
||||
**Created**: {{CREATED_DATE}}
|
||||
**Owner**: Daron Vener
|
||||
|
||||
---
|
||||
|
||||
## PROJECT MISSION
|
||||
|
||||
{{PROJECT_PURPOSE}}
|
||||
|
||||
**Core Focus**:
|
||||
{{CORE_FOCUS_ITEMS}}
|
||||
|
||||
---
|
||||
|
||||
## SCOPE & BOUNDARIES
|
||||
|
||||
### IN SCOPE
|
||||
{{IN_SCOPE_ITEMS}}
|
||||
|
||||
### OUT OF SCOPE
|
||||
{{OUT_OF_SCOPE_ITEMS}}
|
||||
|
||||
---
|
||||
|
||||
## PARENT SYSTEM INTEGRATION
|
||||
|
||||
**This is a sub-project of CCGG Business Operations**
|
||||
|
||||
### Project Memory Index Sync
|
||||
|
||||
**Your Project Index**: `../../../Project Memory/Active Projects Index/{{PROJECT_NAME}}-index.md`
|
||||
|
||||
**When to Update** (PROACTIVELY):
|
||||
- After completing major deliverable
|
||||
- When project status changes (incubating → ready, paused, etc.)
|
||||
- After significant progress (weekly recommended during active work)
|
||||
|
||||
**How to Update**:
|
||||
1. Read `../../../Project Memory/Active Projects Index/{{PROJECT_NAME}}-index.md`
|
||||
2. Update: Current Status, Key Deliverables (mark completed items), Last Activity, date_modified, last_sync
|
||||
3. Offer to log in operations_log.txt
|
||||
|
||||
**Example Updates**:
|
||||
- "Completed deliverable: [specific output]"
|
||||
- "Phase [X] complete: [summary]"
|
||||
- "Status changed: incubating → ready for implementation"
|
||||
|
||||
---
|
||||
|
||||
### Operations Logging
|
||||
|
||||
**Location**: `../../../operations_log.txt`
|
||||
|
||||
**Auto-log** (AUTOMATICALLY, without asking): Major deliverables, milestones, decisions, phase completions, index updates
|
||||
|
||||
**Format**: `[YYYY-MM-DD HH:MM:SS] - [ACTION] - {{PROJECT_NAME}} - [details]`
|
||||
|
||||
**Actions to Auto-Log**:
|
||||
- **CREATE**: New deliverables, documents, implementations
|
||||
- **UPDATE**: Revisions to key outputs
|
||||
- **COMPLETE**: Phase completions, deliverable handoffs
|
||||
- **SYSTEM_UPGRADE**: Infrastructure improvements
|
||||
- **SYNC**: Project index updates
|
||||
|
||||
**Examples**:
|
||||
```
|
||||
[YYYY-MM-DD HH:MM:SS] - COMPLETE - {{PROJECT_NAME}} - [Deliverable name] complete. [Key details].
|
||||
[YYYY-MM-DD HH:MM:SS] - CREATE - {{PROJECT_NAME}} - [New output] created. [Purpose and context].
|
||||
[YYYY-MM-DD HH:MM:SS] - SYNC - {{PROJECT_NAME}} - Project index updated. Status: [current status].
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Strategic Alignment Validation
|
||||
|
||||
Reference `../../../AI Growth Engine/Knowledge Base/Strategy_for_CCGG_AI_Leaders_Business.md`
|
||||
|
||||
**OOBG Check**: Does this help coaches/consultants monetize with AI?
|
||||
{{OOBG_ALIGNMENT}}
|
||||
|
||||
**Unique Vehicle Check**: Does this leverage YouTube + CCGG paid community?
|
||||
{{UV_ALIGNMENT}}
|
||||
|
||||
**Avatar Targeting**: Which specific customer avatars benefit?
|
||||
{{AVATAR_TARGETING}}
|
||||
|
||||
---
|
||||
|
||||
### Cross-Project Intelligence
|
||||
|
||||
Search `../../../Project Memory/Active Projects Index/` for related projects when asked.
|
||||
|
||||
**Related Projects**:
|
||||
{{RELATED_PROJECTS}}
|
||||
|
||||
---
|
||||
|
||||
## PROJECT STRUCTURE
|
||||
|
||||
```
|
||||
{{PROJECT_NAME}}/
|
||||
├── CLAUDE.md # This file - project guidance
|
||||
├── README.md # Project overview
|
||||
{{FOLDER_STRUCTURE}}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## EXPECTED DELIVERABLES
|
||||
|
||||
{{DELIVERABLES_LIST}}
|
||||
|
||||
---
|
||||
|
||||
## MULTI-PHASE PROJECT TRACKER
|
||||
|
||||
{{PHASE_TRACKER_SECTION}}
|
||||
|
||||
---
|
||||
|
||||
## SUCCESS CRITERIA
|
||||
|
||||
### Project Success
|
||||
{{PROJECT_SUCCESS_CRITERIA}}
|
||||
|
||||
### Business Impact (Post-Implementation)
|
||||
{{BUSINESS_IMPACT_CRITERIA}}
|
||||
|
||||
---
|
||||
|
||||
## IMPORTANT REMINDERS
|
||||
|
||||
1. **Update Project Memory Index** after major deliverables
|
||||
2. **Log significant progress** to operations_log.txt
|
||||
3. **Validate strategic alignment** periodically (OOBG, UV, Avatars)
|
||||
4. **Reference related projects** for context and integration
|
||||
|
||||
---
|
||||
|
||||
**Your mission**: {{MISSION_STATEMENT}}
|
||||
149
skills/project-creator/templates/PHASE_TRACKER_TEMPLATE.md
Normal file
149
skills/project-creator/templates/PHASE_TRACKER_TEMPLATE.md
Normal file
@@ -0,0 +1,149 @@
|
||||
# Multi-Phase Project Tracker: {{PROJECT_TITLE}}
|
||||
|
||||
**Project**: {{PROJECT_TITLE}}
|
||||
**Status**: Phase 1 ({{PHASE_1_NAME}})
|
||||
**Created**: {{CREATED_DATE}}
|
||||
**Last Checked**: {{CREATED_DATE}}
|
||||
|
||||
---
|
||||
|
||||
## Phase Timeline
|
||||
|
||||
### Phase 1: {{PHASE_1_NAME}} (Target: {{PHASE_1_TARGET_DATES}})
|
||||
**Status**: ✅ IN PROGRESS (started {{CREATED_DATE}})
|
||||
|
||||
**Goal**: {{PHASE_1_GOAL}}
|
||||
|
||||
**Duration**: {{PHASE_1_DURATION}}
|
||||
|
||||
**Completion Criteria**:
|
||||
{{PHASE_1_CRITERIA}}
|
||||
|
||||
**Deliverables**:
|
||||
{{PHASE_1_DELIVERABLES}}
|
||||
|
||||
**Proactive Reminder Logic**:
|
||||
- **Weekly**: {{PHASE_1_REMINDER_LOGIC}}
|
||||
- **Phase Transition**: {{PHASE_1_TRANSITION_TRIGGER}}
|
||||
|
||||
**Next Phase Trigger**: {{PHASE_1_NEXT_TRIGGER}}
|
||||
|
||||
---
|
||||
|
||||
### Phase 2: {{PHASE_2_NAME}} (Target: {{PHASE_2_TARGET_DATES}})
|
||||
**Status**: ⏳ PENDING (starts after Phase 1 complete)
|
||||
|
||||
**Goal**: {{PHASE_2_GOAL}}
|
||||
|
||||
**Duration**: {{PHASE_2_DURATION}}
|
||||
|
||||
**Trigger**: {{PHASE_2_TRIGGER}}
|
||||
|
||||
**Completion Criteria**:
|
||||
{{PHASE_2_CRITERIA}}
|
||||
|
||||
**Tasks**:
|
||||
{{PHASE_2_TASKS}}
|
||||
|
||||
**Proactive Reminder**:
|
||||
{{PHASE_2_REMINDER}}
|
||||
|
||||
**Next Phase Trigger**: {{PHASE_2_NEXT_TRIGGER}}
|
||||
|
||||
---
|
||||
|
||||
### Phase 3: {{PHASE_3_NAME}} (Target: {{PHASE_3_TARGET_DATES}})
|
||||
**Status**: ⏳ PENDING (starts after Phase 2 complete)
|
||||
|
||||
**Goal**: {{PHASE_3_GOAL}}
|
||||
|
||||
**Duration**: {{PHASE_3_DURATION}}
|
||||
|
||||
**Trigger**: {{PHASE_3_TRIGGER}}
|
||||
|
||||
**Completion Criteria**:
|
||||
{{PHASE_3_CRITERIA}}
|
||||
|
||||
**Tasks**:
|
||||
{{PHASE_3_TASKS}}
|
||||
|
||||
**Proactive Reminder**:
|
||||
{{PHASE_3_REMINDER}}
|
||||
|
||||
**Project Complete**: {{PROJECT_COMPLETION_DEFINITION}}
|
||||
|
||||
---
|
||||
|
||||
## Proactive Reminder Logic (How Claude Tracks This)
|
||||
|
||||
### Weekly Check (During Strategic Planning OR Friday Roadmap)
|
||||
1. **Read** `PHASE_TRACKER.md` → Check current phase status
|
||||
2. **Calculate** days since phase start (today - phase start date)
|
||||
3. **Check** completion criteria:
|
||||
- Phase 1: {{PHASE_1_CHECK_LOGIC}}
|
||||
- Phase 2: {{PHASE_2_CHECK_LOGIC}}
|
||||
- Phase 3: {{PHASE_3_CHECK_LOGIC}}
|
||||
4. **Prompt** phase transition if criteria met OR deadline passed
|
||||
|
||||
### Example Prompts
|
||||
**Phase 1 Complete**:
|
||||
```
|
||||
"Phase 1 {{PHASE_1_NAME}} complete:
|
||||
- {{PHASE_1_SUCCESS_INDICATORS}}
|
||||
|
||||
Ready to start Phase 2 ({{PHASE_2_NAME}})?"
|
||||
```
|
||||
|
||||
**Phase 2 Complete**:
|
||||
```
|
||||
"Phase 2 {{PHASE_2_NAME}} complete:
|
||||
- {{PHASE_2_SUCCESS_INDICATORS}}
|
||||
|
||||
Ready to move to Phase 3 ({{PHASE_3_NAME}})?"
|
||||
```
|
||||
|
||||
### Manual Check (Anytime)
|
||||
- User says: **"Check phase tracker"** OR **"Check phase tracker {{PROJECT_NAME}}"** → Claude reads PHASE_TRACKER.md, reports current status, prompts next phase if ready
|
||||
|
||||
---
|
||||
|
||||
## Success Criteria (Overall Project)
|
||||
|
||||
### Phase 1 Success
|
||||
{{PHASE_1_SUCCESS_DEFINITION}}
|
||||
|
||||
### Phase 2 Success
|
||||
{{PHASE_2_SUCCESS_DEFINITION}}
|
||||
|
||||
### Phase 3 Success
|
||||
{{PHASE_3_SUCCESS_DEFINITION}}
|
||||
|
||||
**PROJECT COMPLETE**: {{OVERALL_SUCCESS_DEFINITION}}
|
||||
|
||||
---
|
||||
|
||||
## Reusable Pattern for Future Multi-Phase Projects
|
||||
|
||||
This Phase Tracker pattern can be applied to ANY multi-phase project:
|
||||
|
||||
**Step 1**: Create `PHASE_TRACKER.md` at project start
|
||||
- List all phases, goals, duration, completion criteria
|
||||
- Set target dates (realistic timelines)
|
||||
|
||||
**Step 2**: Add proactive reminders to root CLAUDE.md
|
||||
- Weekly check during strategic planning
|
||||
- Prompt phase transitions when criteria met
|
||||
|
||||
**Step 3**: Manual check available anytime
|
||||
- User: "Check phase tracker" → Claude reports status
|
||||
|
||||
**Benefits**:
|
||||
- Never forget Phase 2/3 (automatic transition prompts)
|
||||
- Clear completion criteria (no guessing "am I done with Phase 1?")
|
||||
- Documented timeline (realistic expectations)
|
||||
- Reusable pattern (apply to any future project)
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: {{CREATED_DATE}}
|
||||
**Next Check**: {{NEXT_CHECK_DATE}}
|
||||
58
skills/project-creator/templates/PROJECT_INDEX.md
Normal file
58
skills/project-creator/templates/PROJECT_INDEX.md
Normal file
@@ -0,0 +1,58 @@
|
||||
---
|
||||
project_id: "incubator-{{PROJECT_NAME}}"
|
||||
title: "{{PROJECT_TITLE}}"
|
||||
project_type: "incubator-program"
|
||||
status: "incubating"
|
||||
date_created: "{{DATE_CREATED}}"
|
||||
date_modified: "{{DATE_CREATED}}"
|
||||
folder_path: "Active Projects/_Incubator/{{PROJECT_NAME}}"
|
||||
tags: [{{TAGS}}]
|
||||
strategic_alignment:
|
||||
oobg_relevance: "{{OOBG_RELEVANCE}}"
|
||||
unique_vehicle_fit: "{{UV_FIT}}"
|
||||
avatar_targets: [{{AVATARS}}]
|
||||
|
||||
# Dependency tracking (FORCING FUNCTION - always populate, even if empty)
|
||||
dependencies:
|
||||
blocks: {{BLOCKS}} # Projects that BLOCK this one (must complete first)
|
||||
blocked_by: {{BLOCKED_BY}} # Projects this one BLOCKS (waiting for this)
|
||||
related_parallel: {{RELATED}} # Connected but not blocking
|
||||
|
||||
dependency_status:
|
||||
is_blocked: {{IS_BLOCKED}} # Auto-calculated from blocks[]
|
||||
blocking_count: {{BLOCKING_COUNT}} # Auto-calculated from blocked_by[]
|
||||
ready_to_start: {{READY}} # Auto-calculated
|
||||
|
||||
last_sync: "{{DATE_CREATED}} (Project creation)"
|
||||
---
|
||||
|
||||
## Current Status
|
||||
|
||||
**{{STATUS_DESCRIPTION}}**
|
||||
|
||||
{{CONTEXT}}
|
||||
|
||||
## PARENT SYSTEM INTEGRATION
|
||||
|
||||
**Auto-synced**: {{DATE_CREATED}}
|
||||
|
||||
**Dependencies**:
|
||||
- Upstream: {{UPSTREAM_PROSE}}
|
||||
- Downstream: {{DOWNSTREAM_PROSE}}
|
||||
|
||||
**Integration Notes**: {{INTEGRATION_NOTES}}
|
||||
|
||||
## Key Deliverables
|
||||
|
||||
{{DELIVERABLES_CHECKLIST}}
|
||||
|
||||
## Last Activity
|
||||
|
||||
**Created**: {{DATE_CREATED}} (Initial project setup)
|
||||
**Last Modified**: {{DATE_CREATED}}
|
||||
|
||||
## Quick Access
|
||||
|
||||
**Full Project**: [Active Projects/_Incubator/{{PROJECT_NAME}}](../../Active Projects/_Incubator/{{PROJECT_NAME}}/)
|
||||
- [README.md](../../Active Projects/_Incubator/{{PROJECT_NAME}}/README.md)
|
||||
- [CLAUDE.md](../../Active Projects/_Incubator/{{PROJECT_NAME}}/CLAUDE.md)
|
||||
71
skills/project-creator/templates/README.md
Normal file
71
skills/project-creator/templates/README.md
Normal file
@@ -0,0 +1,71 @@
|
||||
# Project Creator Templates
|
||||
|
||||
This folder contains templates used by the project-creator skill to generate CCGG Business Operations projects.
|
||||
|
||||
## Templates
|
||||
|
||||
### CLAUDE_SIMPLE.md
|
||||
Standard project CLAUDE.md template with PARENT SYSTEM INTEGRATION.
|
||||
|
||||
**When to use**: Projects that don't coordinate with other projects (most projects).
|
||||
|
||||
**Variables to replace**:
|
||||
- `{{PROJECT_NAME}}` - Hyphen-case project name
|
||||
- `{{PROJECT_TITLE}}` - Human-readable title
|
||||
- `{{PROJECT_TYPE}}` - Type (incubator-program, active-program, etc.)
|
||||
- `{{CREATED_DATE}}` - YYYY-MM-DD format
|
||||
- `{{PROJECT_PURPOSE}}` - 1-2 sentence purpose
|
||||
- `{{CORE_FOCUS_ITEMS}}` - Bullet list of focus areas
|
||||
- `{{IN_SCOPE_ITEMS}}` - What's included
|
||||
- `{{OUT_OF_SCOPE_ITEMS}}` - What's not included
|
||||
- `{{OOBG_ALIGNMENT}}` - How this serves OOBG
|
||||
- `{{UV_ALIGNMENT}}` - How this leverages Unique Vehicle
|
||||
- `{{AVATAR_TARGETING}}` - Which avatars benefit
|
||||
- `{{RELATED_PROJECTS}}` - Links to related projects
|
||||
- `{{FOLDER_STRUCTURE}}` - Project folder tree
|
||||
- `{{DELIVERABLES_LIST}}` - Phased deliverables list
|
||||
- `{{PROJECT_SUCCESS_CRITERIA}}` - How to measure success
|
||||
- `{{BUSINESS_IMPACT_CRITERIA}}` - Post-implementation impact
|
||||
- `{{MISSION_STATEMENT}}` - One-sentence mission
|
||||
|
||||
### CLAUDE_COMPLEX.md
|
||||
Complex project template with Coordination Hub support.
|
||||
|
||||
**When to use**: Projects that coordinate with 2+ other projects.
|
||||
|
||||
**Additional variables**:
|
||||
- `{{UPSTREAM_DEPENDENCIES}}` - Projects this depends on (with status, blockers)
|
||||
- `{{DOWNSTREAM_DEPENDENCIES}}` - Projects that depend on this
|
||||
- `{{DEPENDENCY_CHAIN_DESCRIPTION}}` - How dependencies flow
|
||||
- `{{INTEGRATION_POINTS}}` - Where projects connect
|
||||
- `{{INTEGRATION_SUCCESS_CRITERIA}}` - How to measure coordination success
|
||||
|
||||
### PHASE_TRACKER_TEMPLATE.md
|
||||
Multi-phase project tracker template.
|
||||
|
||||
**When to use**: Projects with 2+ phases (test → validate, MVP → production, etc.)
|
||||
|
||||
**Variables to replace**:
|
||||
- `{{PROJECT_NAME}}` - Hyphen-case project name
|
||||
- `{{PROJECT_TITLE}}` - Human-readable title
|
||||
- `{{CREATED_DATE}}` - YYYY-MM-DD format
|
||||
- `{{PHASE_1_NAME}}` - Phase 1 name (e.g., "Setup & Test")
|
||||
- `{{PHASE_1_GOAL}}` - What Phase 1 accomplishes
|
||||
- `{{PHASE_1_DURATION}}` - Time estimate (e.g., "4 weeks")
|
||||
- `{{PHASE_1_TARGET_DATES}}` - Date range (e.g., "Nov 7 - Dec 7, 2025")
|
||||
- `{{PHASE_1_CRITERIA}}` - Completion criteria checklist
|
||||
- `{{PHASE_1_DELIVERABLES}}` - Deliverables checklist
|
||||
- `{{PHASE_1_REMINDER_LOGIC}}` - How Claude reminds weekly
|
||||
- `{{PHASE_1_TRANSITION_TRIGGER}}` - When to prompt Phase 2
|
||||
- `{{PHASE_1_NEXT_TRIGGER}}` - Date or criteria for Phase 2
|
||||
- (Repeat for Phase 2 and Phase 3)
|
||||
- `{{PHASE_1_CHECK_LOGIC}}` - How to check if Phase 1 complete
|
||||
- `{{PHASE_1_SUCCESS_INDICATORS}}` - What signals success
|
||||
- `{{PHASE_1_SUCCESS_DEFINITION}}` - Overall Phase 1 success criteria
|
||||
- `{{PROJECT_COMPLETION_DEFINITION}}` - What "project complete" means
|
||||
- `{{OVERALL_SUCCESS_DEFINITION}}` - Final success definition
|
||||
- `{{NEXT_CHECK_DATE}}` - Next scheduled check
|
||||
|
||||
---
|
||||
|
||||
**Note**: Phase Tracker is OPTIONAL. Only use for multi-phase projects requiring validation/testing before full rollout.
|
||||
Reference in New Issue
Block a user