Friction (surfaced by @tobiu, 2026-06-03). There is an epic-review skill (entry) + an epic-resolution skill (exit), but no epic-create skill — the creation-side dual of ticket-create. Result: agents bombard epic bodies with pseudo-subs + ACs instead of describing the problem scope + intended solution.
Empirical anchor
My own #12440 + #12442 epics this session baked full AC lists + a sub-decomposition into the epic body, then created the subs separately. That is the antipattern — the body duplicates (and will out-stale) the linked subs.
The rule the skill must codify
- An epic body = problem scope + intended solution (+ the §6.6 graduation Signal Ledger when graduated from a Discussion).
- ACs live in the SUB tickets, not the epic body.
- Subs are linked via
update_issue_relationship (parent-child) and added incrementally at any time.
- The epic body MUST NOT hardcode sub-lists / sub-content — it goes stale as subs are added/changed → FAIL. The live sub-set is the linked relationship, not body prose.
Scope
A new .agents/skills/epic-create/ skill (sibling to ticket-create, epic-review, epic-resolution), authored per the create-skill Progressive-Disclosure discipline (Map/SKILL.md router + references payload; net-byte conscious).
Related
- #11370 — codify optional ADR emission at Ideation Sandbox graduation (adjacent: the Discussion → epic + ADR path).
epic-review / epic-resolution — the existing entry/exit duals this completes.- Surfaced during the #12453 AiConfig-SSOT effort (whose epic, when filed post-graduation, should follow this skill).
Origin: @tobiu-surfaced, session e886ae3e.
Friction (surfaced by @tobiu, 2026-06-03). There is an
epic-reviewskill (entry) + anepic-resolutionskill (exit), but noepic-createskill — the creation-side dual ofticket-create. Result: agents bombard epic bodies with pseudo-subs + ACs instead of describing the problem scope + intended solution.Empirical anchor
My own #12440 + #12442 epics this session baked full AC lists + a sub-decomposition into the epic body, then created the subs separately. That is the antipattern — the body duplicates (and will out-stale) the linked subs.
The rule the skill must codify
update_issue_relationship(parent-child) and added incrementally at any time.Scope
A new
.agents/skills/epic-create/skill (sibling toticket-create,epic-review,epic-resolution), authored per thecreate-skillProgressive-Disclosure discipline (Map/SKILL.md router + references payload; net-byte conscious).Related
epic-review/epic-resolution— the existing entry/exit duals this completes.Origin: @tobiu-surfaced, session
e886ae3e.