Files
wehub-resource-sync bb5c75ce05
Component Security Validation / Security Audit (push) Has been cancelled
Deploy to Cloudflare Pages / deploy (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:38:58 +08:00

1.5 KiB


allowed-tools: Read, Write, Edit, Bash argument-hint: [epic-name] | --name | --description | --owner description: Create new PAC epic following Product as Code specification

Create PAC Epic

Create a new epic following the Product as Code specification with guided workflow: $ARGUMENTS

PAC Configuration Check

  • PAC directory: !ls -la .pac/ 2>/dev/null || echo "No .pac directory found"
  • PAC config: @.pac/pac.config.yaml (if exists)
  • Existing epics: !ls -la .pac/epics/ 2>/dev/null | head -10

Task

Create a new Product as Code epic:

Arguments:

  • Epic name (required if not using --name flag)
  • --name : Epic name
  • --description : Epic description
  • --owner : Epic owner
  • --scope : Scope definition

Epic Creation Process:

  1. Validate PAC configuration exists (suggest /project:pac-configure if missing)
  2. Generate epic ID from name (format: epic-[kebab-case-name])
  3. Create epic YAML file following PAC v0.1.0 specification in .pac/epics/[epic-id].yaml
  4. Include required metadata: id, name, created timestamp, owner
  5. Add spec with description, scope, success criteria, constraints, dependencies
  6. Create epic directory structure: .pac/epics/[epic-id]/
  7. Update PAC index if .pac/index.yaml exists
  8. Create git branch pac/[epic-id] if in git repository

If information is missing, prompt user interactively for epic details.

Next Steps: Use /project:pac-create-ticket --epic [epic-id] to add tickets to this epic.