Skip to main content
command

pac-configure — Claude Code command: scaffold a PAC project

Sets up a Product as Code structure: .pac/ directory, config, epic and ticket templates. Useful when product work lives in the same repo as code.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command project-management/pac-configure
Open on GitHub

What pac-configure does

The command scaffolds Product as Code inside your repository. It starts by checking the project: counts uncommitted changes, looks for an existing .pac/ directory, and finds any epics under .pac/epics/. Then it creates the directories for epics, tickets and templates and writes pac.config.yaml with project metadata and defaults.

After that come epic and ticket templates following the PAC v0.1.0 specification, a first epic and ticket built from your arguments, plus git hooks and validation scripts. Arguments: --minimal for the basic structure, --epic-name for the initial epic name, --owner for the product owner.

A git repository is required, since validation of the repo is the first step. Ongoing product work then goes through /project:pac-create-epic and /project:pac-create-ticket.

What it helps with

  • scaffold a .pac/ directory in the repo
  • generate pac.config.yaml with project metadata
  • create epic and ticket templates per PAC v0.1.0
  • seed the first epic and ticket from command arguments
  • wire up git hooks and validation scripts

Example prompts for the agent

  • /project:pac-configure my-app
  • /project:pac-configure --minimal
  • /project:pac-configure --epic-name "Onboarding" --owner "Alex"

How to install pac-configure

1claude-code-templates

npx claude-code-templates@latest --command project-management/pac-configure

2Manually: put the files in place

.claude/commands/pac-configure.md

Call it with /pac-configure. For all projects use ~/.claude/commands/

Questions about pac-configure

How do I install pac-configure in Claude?

Run npx claude-code-templates@latest --command project-management/pac-configure, then confirm the file landed at .claude/commands/pac-configure.md.

What does pac-configure do?

It initializes a Product as Code structure: the .pac/ directory with epics, tickets and templates, a pac.config.yaml config, a first epic and ticket, git hooks and validation scripts.

What arguments does the command take?

--minimal for the basic structure, --epic-name for the initial epic name, and --owner for the product owner. With no arguments it creates the default structure.

Source text

pac-configure.md · MIT
---
allowed-tools: Read, Write, Edit, Bash
argument-hint: "[project-name] | --minimal | --epic-name | --owner"
description: Initialize Product as Code (PAC) project structure with templates and configuration
---

# Configure PAC Project

Initialize Product as Code (PAC) project structure: **$ARGUMENTS**

## Current Project State

- Git status: !`git status --porcelain | wc -l` uncommitted changes
- PAC structure: !`ls -la .pac/ 2>/dev/null | head -5 || echo "No PAC directory"`
- Existing epics: !`find .pac/epics/ -name "*.yaml" 2>/dev/null | wc -l`

## Task

Configure and initialize PAC project structure for version-controlled product management:

**Setup Process**:
1. **Project Analysis** - Validate git repository and analyze existing PAC structure
2. **Directory Creation** - Create `.pac/` structure with epics, tickets, and templates
3. **Configuration Files** - Generate `pac.config.yaml` with project metadata and defaults
4. **Template Creation** - Create epic and ticket templates following PAC v0.1.0 specification
5. **Initial Content** - Create first epic and ticket based on user input
6. **Integration Setup** - Configure git hooks and validation scripts

**Arguments**: Use --minimal for basic structure, --epic-name for initial epic, --owner for product owner.

**Next Steps**: Use `/project:pac-create-epic` and `/project:pac-create-ticket` to manage product development.

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set205

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor