pkuppens/issue-work-down
skills/issue-workflow/issue-work-down/SKILL.md
Identifies work-down from other issues, existing code, and tests; scopes the issue. Use when drafting or refining an issue to avoid duplicate work and clarify boundaries.
development
Updated May 15, 2026
$ install --global
skillsauthnpx skillsauth add pkuppens/pkuppens issue-work-downInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 5:42 AM57.1s1 file scanned
SKILL.md
- name:
- issue-work-down
- description:
- Identifies work-down from other issues, existing code, and tests; scopes the issue. Use when drafting or refining an issue to avoid duplicate work and clarify boundaries.
Issue Work Down
Decomposes the issue into actionable work items by linking to existing code, tests, and related issues.
When to use
- After purpose alignment and before acceptance criteria
- When an issue spans multiple files or has dependencies on other work
Instructions
- Search related issues —
gh issue list --search "term" --state open; note blocking or overlapping issues. - Search codebase — use
rg, file tree, or IDE search for modules, classes, or files the change touches. - Identify work-down — list concrete items: files to create/modify, tests to add, issues to unblock.
- Scope boundary — state what is in-scope vs deferred (hand off to issue-out-of-scope).
Output format
## Work Down
- **Related issues:** #N (blocks), #M (overlaps — narrow)
- **Files to modify:** `path/to/file.py`, `path/to/test_*.py`
- **New files:** `path/to/new_module.py`
- **Tests:** add/update in `tests/test_*.py`
- **Deferred:** [items for follow-up issues]
Example
For "Add BM25 retrieval to RAG pipeline":
- Related: #12 (refactor retrievers)
- Modify:
backend/retrievers/base.py,backend/retrievers/bm25.py - Tests:
tests/test_bm25_retriever.py
Integration
- Runs after issue-purpose-alignment.
- Feeds issue-acceptance-criteria and issue-estimate.
Related Skills
pkuppens/sync-branch
testing
VerifiedTrustedCommunity
Syncs remote default branch locally (checkout, fetch --prune, pull) and returns to the previous branch when it still exists. Reports stashes and worktrees not yet handled. Use when the user asks to sync main, update default branch, fetch/pull origin, or run /sync-branch.
SKILL.mdUpdated Jun 6, 2026
pkuppens/azure-devops-work-items
tools
VerifiedTrustedCommunity
Creates, queries, updates, and links Azure Boards work items via az boards CLI. Use when filing ADO work items, running WIQL queries, or setting area path, iteration, tags, and assignee.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-repos
tools
VerifiedTrustedCommunity
Creates, reviews, and completes Azure Repos pull requests and branch policies via az repos CLI. Use when opening ADO PRs, setting required reviewers, or configuring build validation policies.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-pipelines
development
VerifiedTrustedCommunity
Guides Azure Pipelines YAML structure, build validation on PRs, and staged deployment with environments and approvals. Use when authoring azure-pipelines.yml or configuring CI/CD on Azure DevOps.
SKILL.mdUpdated May 29, 2026