Context

Current guidance allows tasks to proliferate without clear Epic/UserStory boundaries. We need explicit criteria in SKILL.md.

Goal

Add concise rules in SKILL.md describing when to open Epic, Feature, UserStory, or Task.

Approach

Define a short decision rubric and examples; keep it brief and aligned with existing backlog discipline.

Acceptance Criteria

SKILL.md includes a clear section with criteria for Epic/Feature/UserStory/Task and examples.

Risks / Dependencies

Overly rigid rules may slow work; keep guidance lightweight.

Worklog

2026-01-16 23:20 [agent=codex] [model=unknown] Created item 2026-01-16 23:21 [agent=codex] [model=gpt-5.2-codex] Added ticket type selection guidance for Epic/Feature/UserStory/Task in SKILL.md. 2026-01-16 23:21 [agent=codex] [model=gpt-5.2-codex] Ticketing guidance added.