Pac Configure
Initialize Product as Code (PAC) project structure with templates and configuration
npx claude-code-templates@latest --command project-management/pac-configure Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
Partial analysis: some checks could not run on this component.
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Configure PAC Project
Initialize Product as Code (PAC) project structure: $ARGUMENTS
Current Project State
- Git status: !
git status --porcelain | wc -luncommitted 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:
- Project Analysis - Validate git repository and analyze existing PAC structure
- Directory Creation - Create
.pac/structure with epics, tickets, and templates - Configuration Files - Generate
pac.config.yamlwith project metadata and defaults - Template Creation - Create epic and ticket templates following PAC v0.1.0 specification
- Initial Content - Create first epic and ticket based on user input
- 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.