원클릭으로
create-epic
Creates a Meridian epic in SQLite after architecture is approved. Use when defining a new product capability before user stories.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Creates a Meridian epic in SQLite after architecture is approved. Use when defining a new product capability before user stories.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Creates a Meridian user story in SQLite after epics and versions exist. Use when adding work to the backlog with concrete acceptance criteria.
Refines a Meridian user story in SQLite for implementation — deepens Approach, architecture refs and tests. Use between /create-us and coding.
Gates implementation of a Meridian user story — verifies ready true, Plan, deps and architecture refs before product code. Use with /implement-us US-XXXX.
Maintainer procedure to add or change Meridian kit artifacts — skill, agent, workflow, routing, and every registry surface. Use when extending the harness, creating /investigate, or onboarding a new slash command.
Closes a Meridian sprint in SQLite after sprint review — fills Retrospective, sets status complete, logs decisions. Use with /complete-sprint vX-SY.
Closes a Meridian user story in SQLite after implementation — fills Record, acceptance, status. Use when marking US done or after /implement-us.
| name | create-epic |
| description | Creates a Meridian epic in SQLite after architecture is approved. Use when defining a new product capability before user stories. |
| allowed-tools | Read, Glob, Grep, Bash, Edit, Write |
v11: epics live in SQLite — never create
docs/epics/*.md.
| File | When to read |
|---|---|
.agent/references/templates/writing-guide.md | Epic prose + golden example |
.agent/references/scrum-meridian-map.md | Epic lifecycle |
references/epic-template.md | Mandatory — body_markdown shape |
docs/03_user_types.md | Validate profiles |
python3 .agent/scripts/meridian_delivery.py list versions
python3 .agent/scripts/meridian_delivery.py create-epic --title "..." --versions "[v11]"
python3 .agent/scripts/meridian_delivery.py update-epic EPIC-15 <<'EOF'
---
id: EPIC-15
title: ...
status: active
versions: [v11]
profiles: [...]
outcome: "..."
---
# EPIC-15 — ...
(body per epic-template.md)
EOF
Never Write docs/epics/. Persist with update-epic on stdin (heredoc) — no scratch files.
| Doc | Required status |
|---|---|
05_architecture.md | approved |
00_scope.md | in scope |
03_user_types.md | approved |
writing-guide.md + epic-template.md.create-epic (prints id) or use next from list epics.update-epic EPIC-XX with markdown on stdin (heredoc).profiles vs 03_user_types.md; versions vs list versions.prepend-decision if boundaries change.Epic created:
ID: EPIC-XX
Outcome:
Versions:
Profiles:
Narrative complete: yes | no
Next: /create-us for slices