WHAT - Router for creating and refining epics, user stories, tasks, bugs, and incidents using
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add ulises-jeremias/agent-toolkit --skill work-item --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Work Item?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ulises-jeremias-work-item-e6496dcd)More formats (shields.io, HTML) on the badges page.
---
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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
