version: "1.0.1" area: general created: '2026-01-16' decisions: [] external: azure_id: null jira_key: null id: KABSD-TSK-0235 iteration: backlog links: blocked_by: [] blocks: [] relates: [] owner: None parent: null priority: P2 state: Done tags: [] title: Clarify Epic/Feature/UserStory/Task ticketing guidance in SKILL type: Task uid: 019bc764-cc53-71e0-bd52-2d1444d7444a updated: 2026-01-16

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.