Work Items Skill
Apply these patterns when working with issues, tickets, or work items from any system (GitHub Issues, Jira, Azure DevOps, Linear, etc.).
LLM Optimization Patterns
File Path Compression
Use glob patterns to compress multiple file paths:
| Before |
After |
routes/dev-routes.bicep, routes/test-routes.bicep, routes/prod-routes.bicep |
routes/{dev,test,prod}-routes.bicep |
src/components/Button.tsx, src/components/Input.tsx |
src/components/{Button,Input}.tsx |
Terse Language Rules
- No articles ("the", "a") unless needed for clarity
- No filler phrases ("In order to", "This will")
- Use arrows for transformations:
external -> internal, HTTP -> HTTPS
- Use equals for settings:
ingress.external = false
Output Structure
Optimize work items into this token-efficient format:
# {ID}: {title}
## Context
{1-2 sentence summary}
## Files
- {file paths with glob patterns}
## Changes
1. {file}: {action}
## Verify
- {non-obvious verification step}
Acceptance Criteria Filtering
Remove obvious/implicit criteria:
- "Deployment succeeds"
- "No downtime"
- "Tests pass"
- "Code reviewed"
- "PR merged"
Keep non-obvious verification:
- Specific HTTP status codes
- Portal/UI status checks
- Security constraints
- Integration behaviors
Task Breakdown Rules
Granularity
- 1 task = 1 logical change that can be committed independently
- Each task: ~5-30 min of work
- Group related file changes if they must be atomic
Sequencing
- Infrastructure/Config first (env vars, config files, dependencies)
- Core changes second (main logic, modules)
- Dependent files third (routes, integrations, consumers)
- Verification last (manual checks, cleanup)
Task Format
## Task {n}: {brief title}
**Files**: {file(s) to modify}
**Do**:
- {specific action}
**Test**:
- {how to verify}
Completeness Criteria
Title
- Descriptive (> 5 words typically)
- Clearly indicates what feature/change is needed
- Avoids vague terms: "fix bug", "update code", "improvements"
Description
- Exists and is not empty
- Explains what needs to be done
- Explains why it's needed (business value/context)
- Provides enough context for a developer to understand scope
Acceptance Criteria
- Present and populated
- Contains specific, testable conditions
- Uses clear language (Given/When/Then or bullet points)
- Defines what "done" looks like
1---2name: work-items-23description: Optimize and analyze work items for LLM-assisted development4when_to_use: |5 Use this skill when the user:6 - Pastes a work item, issue, or ticket from any system7 - Asks about work item readiness or completeness8 - Needs to break down a feature into implementation tasks9 - Wants to optimize content for LLM context windows10metadata:11 source: https://skillmd.com/skills/majiayu000/work-items-212---1314# Work Items Skill1516Apply these patterns when working with issues, tickets, or work items from any system (GitHub Issues, Jira, Azure DevOps, Linear, etc.).1718## LLM Optimization Patterns1920### File Path Compression21Use glob patterns to compress multiple file paths:2223| Before | After |24|--------|-------|25| `routes/dev-routes.bicep`, `routes/test-routes.bicep`, `routes/prod-routes.bicep` | `routes/{dev,test,prod}-routes.bicep` |26| `src/components/Button.tsx`, `src/components/Input.tsx` | `src/components/{Button,Input}.tsx` |2728### Terse Language Rules29- No articles ("the", "a") unless needed for clarity30- No filler phrases ("In order to", "This will")31- Use arrows for transformations: `external -> internal`, `HTTP -> HTTPS`32- Use equals for settings: `ingress.external = false`3334### Output Structure35Optimize work items into this token-efficient format:3637```markdown38# {ID}: {title}3940## Context41{1-2 sentence summary}4243## Files44- {file paths with glob patterns}4546## Changes471. {file}: {action}4849## Verify50- {non-obvious verification step}51```5253### Acceptance Criteria Filtering54**Remove** obvious/implicit criteria:55- "Deployment succeeds"56- "No downtime"57- "Tests pass"58- "Code reviewed"59- "PR merged"6061**Keep** non-obvious verification:62- Specific HTTP status codes63- Portal/UI status checks64- Security constraints65- Integration behaviors6667## Task Breakdown Rules6869### Granularity70- 1 task = 1 logical change that can be committed independently71- Each task: ~5-30 min of work72- Group related file changes if they must be atomic7374### Sequencing751. Infrastructure/Config first (env vars, config files, dependencies)762. Core changes second (main logic, modules)773. Dependent files third (routes, integrations, consumers)784. Verification last (manual checks, cleanup)7980### Task Format81```markdown82## Task {n}: {brief title}8384**Files**: {file(s) to modify}8586**Do**:87- {specific action}8889**Test**:90- {how to verify}91```9293## Completeness Criteria9495### Title96- Descriptive (> 5 words typically)97- Clearly indicates what feature/change is needed98- Avoids vague terms: "fix bug", "update code", "improvements"99100### Description101- Exists and is not empty102- Explains **what** needs to be done103- Explains **why** it's needed (business value/context)104- Provides enough context for a developer to understand scope105106### Acceptance Criteria107- Present and populated108- Contains specific, testable conditions109- Uses clear language (Given/When/Then or bullet points)110- Defines what "done" looks like