Easy PAC Configure

Initialize a Product as Code (PAC) project structure with version-controlled epics, tickets, templates, and configuration files in your git repository.

When to Use This Command

Run this command when...

• You are starting a new project and want to establish a PAC directory structure from scratch
• You need to set up .pac/ folders with proper YAML configuration, epic templates, and ticket templates
• You want to integrate product management artifacts directly into your version-controlled repository
• You are onboarding a team to the PAC v0.1.0 specification and need a compliant initial setup
• You need git hooks and validation scripts that enforce PAC conventions on every commit

Quick Start

Copy
# .claude/commands/easy-pac-configure.yaml
name: Easy PAC Configure
description: Initialize PAC project structure for version-controlled product management
inputs:
  - name: project_name
    description: "Name of the project"
  - name: owner
    description: "Product owner name"
    default: ""

Copy
# Initialize with defaults
claude "easy-pac-configure --project MyApp"

# Minimal structure with an initial epic
claude "easy-pac-configure --minimal --epic-name 'User Authentication' --owner 'Jane Smith'"

Output:
  [init] Creating .pac/ directory structure...
  [config] Generated pac.config.yaml
  [template] Created epic template
  [template] Created ticket template
  [epic] Created initial epic: user-authentication
  [hooks] Installed git validation hooks
  Done. PAC project initialized with 1 epic.

Core Concepts

Concept	Description
PAC Directory	The .pac/ folder at the repository root holds all product management artifacts
Configuration File	pac.config.yaml stores project metadata, owner, defaults, and schema version
Epic Templates	YAML templates in .pac/templates/ define the structure for new epics
Ticket Templates	Standardized ticket YAML with status fields, assignees, and acceptance criteria
Git Integration	Pre-commit hooks validate PAC YAML syntax and required fields before allowing commits

.pac/
  ├── pac.config.yaml        # Project configuration
  ├── templates/
  │   ├── epic.yaml           # Epic template
  │   └── ticket.yaml         # Ticket template
  ├── epics/
  │   └── epic-user-auth/     # First epic
  │       └── epic.yaml
  ├── tickets/                # All tickets
  └── index.yaml              # PAC index file

Configuration

Parameter	Type	Default	Description
project_name	string	required	Name of the product or project
owner	string	""	Product owner displayed in config metadata
minimal	boolean	false	Create only essential directories, skip templates
epic_name	string	""	Name for the initial epic created during setup
version	string	"v0.1.0"	PAC specification version to follow

Best Practices

1. Run before any other PAC command -- This command sets up the prerequisite directory structure. Other PAC commands like pac-create-epic expect .pac/ to exist and will fail without it.
2. Commit the initial structure immediately -- After initialization, commit the entire .pac/ directory so teammates can clone and start creating epics and tickets right away.
3. Set an owner in configuration -- Specifying a product owner in pac.config.yaml establishes accountability and appears in generated reports and epic metadata.
4. Use the minimal flag for small projects -- Skip templates and hooks for prototypes or solo projects where the overhead of validation is unnecessary.
5. Keep PAC artifacts in the same branch as code -- Version-controlling product decisions alongside implementation creates a traceable link between what was planned and what was built.

Common Issues

1. Not inside a git repository -- PAC requires a git repository for hooks and branch integration. Run git init first if the directory is not yet tracked by git.
2. Existing .pac/ directory conflicts -- If a .pac/ folder already exists, the command will warn rather than overwrite. Use --force to reinitialize or manually remove the existing directory.
3. Git hooks not executing -- Hooks installed to .git/hooks/ may not have execute permissions. Run chmod +x .git/hooks/pre-commit if validation is not triggering on commits.