Setup Initiative

Goal

Create a new initiative folder with standardized structure and populate with customized templates. This automates the tedious setup process while ensuring consistency across all initiatives.

Process

1. •

   Gather initiative details

   • •Initiative name (use kebab-case: e.g., mobile-app-redesign)
   • •Owner/Product Manager name
   • •Brief description of the initiative goal
   • •Target timeline (optional)
   • •Key stakeholders (optional)
2. •

   Create initiative folder structure

   • •Create initiatives/[initiative-name]/ folder
   • •Copy structure from templates
   • •Preserve all subfolders and README files
3. •

   Customize README.md

   • •Replace [Initiative Name] with the actual initiative name
   • •Replace [Product Manager Name] with the owner's name
   • •Update the goal description
   • •Add timeline and stakeholders if provided
   • •Keep all other template content intact
4. •

   Initialize placeholder files

   • •Create .gitkeep files in empty folders to preserve structure
   • •Ensure all subfolder README files are properly copied

Methods

Method A: Shell script (recommended)

If you have shell access, run:

./scripts/setup-initiative.sh <initiative-name> "<Owner Name>" "<Goal description>"

This creates the full folder structure with all templates.

Method B: Manual creation (for agents without shell access)

Create the following structure manually using file creation tools:

initiatives/[initiative-name]/
├── README.md
├── user-interviews/
│   ├── README.md
│   ├── snapshots/
│   ├── synthesis/
│   └── transcripts/
├── opportunities/
│   └── README.md
├── assumptions/
│   └── README.md
├── solutions/
│   └── README.md
├── design/
│   └── README.md
├── product-analytics/
│   └── README.md
├── prd/
│   └── README.md
└── tasks/
    └── README.md

Use the templates in templates/ as the content for each README.md, replacing placeholders with actual initiative details.

Naming Conventions

• •Initiative Folder: Use kebab-case (e.g., mobile-app-redesign, checkout-optimization)
• •Include Quarter: If relevant, add quarter prefix (e.g., 2024q1-mobile-redesign)
• •Keep Descriptive: Use clear, meaningful names

Integration Points

After creating the initiative structure, remind the user about these workflow integrations:

• •User Research: Use the continuous-discovery skill's "create interview snapshots" workflow in user-interviews/snapshots/
• •Synthesis: Use "synthesize interviews" in user-interviews/synthesis/
• •Opportunities: Use "create opportunities" in opportunities/
• •Assumptions: Use "identify and test assumptions" in assumptions/
• •Solutions: Use "generate solutions" in solutions/
• •Design Briefs: Use the product-documents skill's "create design brief" in design/
• •Figma Make Prompts: Use "generate Figma Make prompt" in design/
• •PRD Creation: Use "create a PRD" in prd/
• •Task Generation: Use the task-management skill's "generate tasks" with the PRD in tasks/
• •Task Processing: Use "process task list" to work through tasks systematically

Validation

After creation, verify:

• • All folders from template are present (including design folder)
• • README.md is properly customized
• • All subfolder README files are present
• • Folder structure matches the template
• • Initiative name follows naming conventions

Success Message

After successful creation, provide:

• •Confirmation of the new initiative folder location
• •Quick start guide for next steps
• •Reminder about available PM skills and integration points

Example

User: "Create a new initiative for mobile app redesign, owned by Sarah Kim"

Agent:
- Creates: initiatives/mobile-app-redesign/
- Customizes README with "Mobile App Redesign" and "Sarah Kim"
- Provides next steps for user research, design brief creation, and PRD creation