Pac Create Epic
Create new PAC epic following Product as Code specification
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/commands/project-management/pac-create-epic.md
--- 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 <name>: Epic name - --description <desc>: Epic description - --owner <owner>: Epic owner - --scope <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.
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: 1fef46a6f7ae0c10c2538cbc5398fba8e35ae231f65a1057d41b4f92099cb616. Files are served as downloads and are never executed by this page.