x-epic-create
Create a focused Epic artifact from an existing Feature markdown, preserving sourceFeature lineage and inherited RNFs without generating stories or implementation map.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- x-epic-create
- model
- sonnet
- description
- Create a focused Epic artifact from an existing Feature markdown, preserving sourceFeature lineage and inherited RNFs without generating stories or implementation map.
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob, Skill
- argument-hint
- --from-feature <feature-file|feature-id> [--capability-file <path>] [--product-file <path>] [--epic-id <NNNN>] [--output-dir <path>] [--dry-run]
- context-budget
- light
- user-invocable
- true
- requires-capabilities
- []
03 SKILL.md 正文
Output Policy
- Language: Portuguese (pt-BR) for all content. English for code identifiers and established technical terms.
- Tone: Technical, Direct, and Concise.
- Efficiency: Remove fillers and avoid re-explaining repository conventions.
Skill: x-epic-create
Purpose
Generate a single Epic markdown artifact from an existing Feature artifact. This focused skill is the Product-First complement to x-create-feature: it materializes only the Feature → Epic step, preserving Source Feature, inheriting RNFs from the Product / Capability / Feature chain, and intentionally omitting sections 2, 4, and 8 of the generic epic template because that context is already owned upstream in the chain.
EPIC-0077 semantic reintroduction:
x-epic-createwas hard-cut in EPIC-0065 when the generic public epic generator moved behindx-internal-create-epic. It is reintroduced here with a narrower responsibility: Feature-derived epic generation only. It is not a legacy alias.
When to Use
- You already have a Feature artifact and need the derived Epic only
- You want Product-First traceability without generating stories/map in the same step
- You need a lightweight wrapper around
x-internal-create-epicfor Feature → Epic
Prerequisites
Read before starting:
.claude/templates/_TEMPLATE-EPIC.md.claude/skills/planning-standards-kp/SKILL.md— mandatory RA9 source of truth.claude/skills/x-internal-create-epic/SKILL.md
If the feature source cannot be resolved, stop with a validation error.
Workflow
- Resolve
--from-feature:- if it is a file path, use it directly;
- otherwise, resolve it by feature id under
ai/**.
- Resolve optional
--capability-fileand--product-fileto enrich RNF inheritance. - Validate epic id (
4 digits, default0001). - Create
ai/epics/epic-<ID>-<slug>/epic-<ID>.md. - Populate:
Source FeatureSource Feature Link## 0.6 Inherited RNFs## 1,## 3,## 5,## 6,## 7,## 9
- Do not render sections
## 2,## 4,## 8for Feature-derived epics.
Parameters
| Parameter | Required | Description |
|---|---|---|
--from-feature <feature-file|feature-id> |
Yes | Feature markdown source |
--capability-file <path> |
No | Capability markdown used to enrich inherited RNFs |
--product-file <path> |
No | Product markdown used to extend inherited RNFs |
--epic-id <NNNN> |
No | Epic identifier (default 0001) |
--output-dir <path> |
No | Base output dir (default ai/epics) |
--dry-run |
No | Validate inputs without writing files |
Integration Notes
x-create-featureremains the full orchestrator for Feature → Epic + Stories + Map.x-epic-createis the focused public wrapper for Feature → Epic only.- The generation logic may delegate to
x-internal-create-epicwhen orchestrated by another planning skill.
04 同仓库更多 Skills
x-parallel-eval
Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.
parallelism-heuristics
Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard / regen / soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.
x-watch-pr-ci
Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.
x-validate-docs
Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.
x-update-system-architecture
Incrementally updates docs/architecture/system.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.
x-update-architecture
Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.