Analyze, optimize, and break down work items for LLM-assisted development

version
1.2.0
GitHub stars
13

Install

/plugin install work-items@claude-code-toolkit

Run it inside Claude Code after adding the marketplace with /plugin marketplace add dariuszparys/claude-code-toolkit.

Contents

Discovered from source

Commands 3

Analyze a work item (GitHub Issue, Jira ticket, Azure DevOps PBI, etc.) for development readiness.

Input

Provide the work item via one of:

Steps

  1. Fetch or parse the work item content
  2. Analyze against the completeness criteria below

Completeness Criteria

Title Analysis

  • Is descriptive (not too short, > 5 words typically)
  • Clearly indicates what feature/change is needed
  • Avoids vague terms like "fix bug", "update code", "improvements"

Description Analysis

  • 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 the scope

Acceptance Criteria Analysis

  • Acceptance criteria / definition of done is present
  • Contains specific, testable conditions
  • Uses clear language (e.g., "Given/When/Then" or bullet points)
  • Defines what "done" looks like

Output Format

Provide a structured analysis:

## Work Item Analysis

### Status: [READY / NEEDS WORK]

**Title**: [Pass/Fail] - [Brief explanation]
**Description**: [Pass/Fail] - [Brief explanation]
**Acceptance Criteria**: [Pass/Fail] - [Brief explanation]

### Recommendations (if NEEDS WORK)
- List specific improvements needed
- Suggest example text where helpful

### Summary
One sentence summarizing the work item readiness.

Related Commands

  • /work-items:optimize — Transform to LLM-optimized format for efficient context usage
  • /work-items:tasks — Generate implementation task breakdown

Transform a work item into a token-efficient format optimized for LLM context windows.

Input

Provide the work item via one of:

Output Structure

# {Work Item ID}: {title}

## Context
{1-2 sentence summary}

## Files
- {file paths with glob patterns}

## Changes
1. {file}: {action}

## Verify
- {non-obvious verification step}

Transformation Rules

1. Title

  • Keep as-is (titles are usually already concise)
  • Output: # {ID}: {title}

2. Description to Context + Files + Changes

Context: Compress background/architecture to 1-2 sentences Files: Extract file paths, compress with glob patterns Changes: Convert scope items to file: action format

3. Acceptance Criteria to Verify

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

4. File Path Compression

BeforeAfter
routes/dev-routes.bicep, routes/test-routes.bicep, routes/prod-routes.biceproutes/{dev,test,prod}-routes.bicep
src/components/Button.tsx, src/components/Input.tsxsrc/components/{Button,Input}.tsx

5. Changes = Actions

Each entry: {file}: {what to change}

Bad: "Update the container app configuration" Good: "container-app.bicep: set ingress.external = false"

6. Terse Language

  • No articles ("the", "a") unless needed for clarity
  • No filler ("In order to", "This will")
  • Use arrows: "external -> internal", "HTTP -> HTTPS"

Example Transformation

Before (~280 tokens)

Description: Change Container Apps ingress from external to internal,
update Front Door origins to use Private Link.

Scope:
- Change Container Apps ingress from external to internal
- Update Front Door origins to use Private Link

Files to modify:
- infra/bicep/resources/container-app.bicep
- infra/bicep/resources/front-door-route.bicep
- infra/bicep/routes/dev-routes.bicep
- infra/bicep/routes/test-routes.bicep
- infra/bicep/routes/prod-routes.bicep

ACs:
- Container Apps ingress is configured as internal
- Front Door origins updated to use Private Link
- Direct access returns 403/404
- Deployment succeeds without downtime

After (~100 tokens)

# 1357: Container Apps Internal Ingress

## Context
Container Apps -> internal ingress. External traffic via Front Door + Private Link.

## Files
- infra/bicep/resources/container-app.bicep
- infra/bicep/resources/front-door-route.bicep
- infra/bicep/routes/{dev,test,prod}-routes.bicep

## Changes
1. container-app.bicep: `ingress.external` = false
2. front-door-route.bicep: origins use Private Link
3. *-routes.bicep: consistent Private Link config

## Verify
- Direct URL -> 403/404
- Front Door URL -> 200
- Private Link status = Approved

Related Commands

  • /work-items:analyze — Check if work item is ready for development first
  • /work-items:tasks — Generate implementation task breakdown from optimized format

Generate a task breakdown from a work item, optimized for sequential Claude Code execution.

Input

Provide the work item via one of:

Task Generation Rules

Task Granularity

  • 1 task = 1 logical change that can be committed independently
  • Each task should take ~5-30 min of Claude Code work
  • Group related file changes if they must be atomic

Task Sequencing

  1. Infrastructure/Config first (env vars, config files, dependencies)
  2. Core changes second (main logic, modules)
  3. Dependent files third (routes, integrations, consumers)
  4. Verification last (manual checks, cleanup)

Include in Each Task

  • Exact file paths
  • Specific property/value changes where known
  • Command or method to test/verify

Exclude from Tasks

  • "Review code" (implicit)
  • "Test deployment" (part of each task's Test section)
  • Generic "update documentation" (be specific or omit)

Output Format

# Tasks for {ID}: {title}

## Summary
{1-line: what we're building, n tasks total}

## Prerequisites
- [ ] {any setup needed before starting}

---

## Task 1: {title}
**Files**: {path}
**Do**:
- {action}
**Test**:
- {verification}

---

## Task 2: {title}
...

Task Format

## Task {n}: {brief title}

**Files**: {file(s) to modify}

**Do**:
- {specific action 1}
- {specific action 2}

**Test**:
- {how to verify this task}

Example Output

# Tasks for 1357: Container Apps Internal Ingress

## Summary
Switch Container Apps to internal ingress with Front Door Private Link. 4 tasks.

## Prerequisites
- [ ] Front Door Premium SKU (required for Private Link)
- [ ] Managed Identity for Private Link approval

---

## Task 1: Configure internal ingress
**Files**: infra/bicep/resources/container-app.bicep
**Do**:
- Set `ingress.external` = `false`
- Ensure `ingress.targetPort` unchanged
**Test**:
- Build succeeds
- `az containerapp show` shows internal ingress

---

## Task 2: Add Private Link to Front Door origin
**Files**: infra/bicep/resources/front-door-route.bicep
**Do**:
- Add `privateLinkLocation` property to origin
- Add `privateLinkResourceId` pointing to Container App
- Set `privateEndpointStatus` to monitor approval
**Test**:
- Deploy to dev, check Portal -> Front Door -> Origins -> Private Link status

---

## Task 3: Update environment routes
**Files**: infra/bicep/routes/{dev,test,prod}-routes.bicep
**Do**:
- Reference updated front-door-route module
- Ensure consistent params across environments
**Test**:
- `az deployment group what-if` for each environment

---

## Task 4: Verify external access blocked
**Files**: (none - verification only)
**Do**:
- Deploy to dev environment
**Test**:
- `curl https://<container-app-url>` -> expect 403/404
- `curl https://<frontdoor-url>` -> expect 200
- Portal: Private Link = "Approved"

Related Commands

  • /work-items:analyze — Check if work item is ready for development first
  • /work-items:optimize — Transform to LLM-optimized format (recommended input for this command)

Sponsors

Details

Marketplace
dariuszparys/claude-code-toolkit
Source
plugins/work-items
Category
Community

More from dariuszparys/claude-code-toolkit

All 6