Work Item

Name: Work Item
Author: ulises-jeremias

ASecurity

WHAT - Router for creating and refining epics, user stories, tasks, bugs, and incidents using

19 stars
0 votes
0 copies
0 views
Added September 2, 2026

ai-agentsrails

Works with

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add ulises-jeremias/agent-toolkit --skill work-item --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Work Item?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ulises-jeremias-work-item/badge)](https://www.skillsdirectory.com/skills/ulises-jeremias-work-item)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: work-item
description: WHAT - Router for creating and refining epics, user stories, tasks, bugs, and incidents using
  Best Practices work item hierarchy.
origin:
  type: first-party
---
# Work Item Router (WHAT)

Use this skill when the user asks to create, refine, or evaluate work items.

## Default guardrails

1. Apply **`output-handshake`** before producing final content or writing to a tool.
2. Use the smallest applicable skill:
   - Epic -> `epic`
   - User story -> `user-story`
   - Technical task -> `task`
   - Bug -> `bug`
   - Incident -> `incident`
3. Use **`planning`** when the item needs breakdown, estimation, prioritization, or capacity checks.
4. Use **`clickup-cli`** for ClickUp writes only after user approval.

## Hierarchy

Epic -> Story/Task/Bug -> Subtasks. Not every methodology uses every level; follow the engagement pack and ticket system.

## References

- `references/default-template.md`
- `references/example-routing-dashboard.md` — example routing decision classifying a feature request as user story