Skip to content

CONFIG.example.md

Latest commit

 

History

History
104 lines (73 loc) · 2.11 KB

CONFIG.example.md

File metadata and controls

104 lines (73 loc) · 2.11 KB

Parallel Development Configuration

Copy this file to CONFIG.md in your skill directory and customize for your project.

Note: CONFIG.md should be gitignored for personal use.

Project Settings

# Project prefix for worktree directories
# Worktrees will be created as: ../{PROJECT_PREFIX}-{STORY_ID}
PROJECT_PREFIX="myproject"

# Absolute path to main repository
REPO_PATH="/Users/yourname/Documents/Code/my-project"

# Story ID format (for reference)
# Default: E{epic}-S{story} (e.g., E2-S1, E3-S4)
STORY_FORMAT="E{epic}-S{story}"

Parallel Set Definitions

Define your parallel sets here. Each set contains stories that can be developed simultaneously.

Parallel Set 1

PARALLEL_SET_1=(
  "E2-S1:feature/user-authentication"
  "E2-S2:feature/user-profile"
  "E3-S1:feature/dashboard-layout"
)

Parallel Set 2

PARALLEL_SET_2=(
  "E2-S3:feature/password-reset"
  "E3-S2:feature/dashboard-widgets"
  "E3-S3:feature/notifications"
  "E3-S4:feature/settings-page"
)

Parallel Set 3

PARALLEL_SET_3=(
  "E4-S1:feature/admin-panel"
  "E4-S2:feature/user-management"
  "E5-S1:feature/reporting"
)

Usage

Option 1: Source from Script

Save the bash blocks above to scripts/parallel-dev.config.sh:

#!/bin/bash
PROJECT_PREFIX="myproject"
REPO_PATH="/Users/yourname/Documents/Code/my-project"

PARALLEL_SET_1=(
  "E2-S1:feature/user-authentication"
  "E2-S2:feature/user-profile"
  "E3-S1:feature/dashboard-layout"
)

# ... more sets

The parallel-dev.sh script automatically loads this file.

Option 2: Environment Variables

export PROJECT_PREFIX="myproject"
export REPO_PATH="/path/to/repo"
./scripts/parallel-dev.sh setup 1

Option 3: Edit Script Directly

For quick setup, edit the configuration section directly in parallel-dev.sh.

Tips

  1. Keep sets small - 3-4 stories per set is optimal
  2. Verify module boundaries - Stories in same set should not modify same files
  3. Update after each sprint - Add new sets as development progresses
  4. Use meaningful branch names - They appear in git history