project-patterns

# Project Patterns

This skill guides project setup and provides patterns for different types of work.

## Choosing a Preset

| Team Size | Coordination | Recommended Preset |
|-----------|--------------|-------------------|
| Solo | None | Direct |
| 2-5 | Informal | Streamlined |
| 5+ | Formal | Full (or Streamlined) |

**Preset differences:**
- **Direct**: Vision → Task (simplest, solo work)
- **Streamlined**: Vision → Initiative → Task (most common, **default**)
- **Full**: Vision → Strategy → Initiative → Task (multi-team coordination)

When in doubt, use the default Streamlined preset. Add Strategy layer later if needed.

## Greenfield Projects

Starting a new project from scratch.

### When to Use
- New product or system
- Major rewrite (treat as new)
- Proof of concept → production
- New team forming

### The Pattern

**1. Initialize:**
```
initialize_project(project_path="/path/to/project", prefix="PROJ")
```
Choose short (2-8 char, uppercase), memorable, unique prefix.

**2. Define Vision:**
Create vision answering: "Why does this project exist?"
- Objectives: What outcomes?
- Values: Why does it matter?
- Success criteria: How to know we succeeded?

Transition: draft → review → published

**3. Create Initial Initiatives:**
Common greenfield initiatives:
- **Foundation/Setup**: Dev environment, CI/CD, architecture
- **Core Feature**: Main thing this project does
- **Integration**: Connecting to other systems
- **Release/Launch**: Getting to production

Don't create all initiatives upfront. Create enough to start, pull more as backlogs empty.

**4. Decompose and Execute:**
For each initiative: discovery → design → decompose → execute

### Greenfield Tips
- **Start small**: Maximum uncertainty, learn as you go
- **Foundation first**: But don't gold-plate it
- **Expect pivots**: Early initiatives may invalidate later plans
- **ADRs from day one**: Capture decisions while context fresh

## Tech Debt Campaigns

Systematic debt reduction.

### When to Use
- Accu