skills.rest
pkuppens
pkuppensCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-work-down

Decompose issues into actionable work items linked to code, tests, and related issues.

Updated Jan 5, 2025
Search Tags:#planning#testing#scoping#issue-management#decompose#work-down#code-tracking
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill issue-work-down
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-work-down
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/issue-workflow/issue-work-down
Command: npx skills add https://github.com/pkuppens/pkuppens --skill issue-work-down

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes the issue into actionable work items by linking to existing code, tests, and related issues.

Core Features & Use Cases

  • Link issues to corresponding code and tests to map dependencies and blockers.
  • Clearly delineate scope and tasks for multi-file changes to prevent duplicate work.
  • Use across planning, refinement, and issue-creation to align stakeholders and expectations.

Quick Start

Draft the work-down plan by listing impacted files, tests to modify, and blockers for the issue.

Frequently Asked Questions about issue-work-down

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a complex issue into actionable work items?▼

Issue decomposition splits a complex issue into actionable work items by linking existing code, tests, and related issues to define concrete tasks and clear boundaries for the team.

What is the best way to map dependencies and blockers for multi-file changes?▼

Mapping dependencies for multi-file changes involves linking issues to their corresponding code and tests, which clearly delineates scope and tasks to prevent duplicate work and identify blockers.

When do I need to create a structured work-down plan for issue tracking?▼

A structured work-down plan is needed when an issue spans multiple files or depends on other work, requiring teams to outline scope, list impacted files, and map references for issue tracking.

Can I use issue scoping during planning and refinement to align stakeholders?▼

Issue scoping can be used across planning, refinement, and issue-creation phases to align stakeholders and expectations by outlining scope and producing a structured work-down output.

How do I draft a work-down plan that lists impacted files and tests to modify?▼

Draft a work-down plan by listing all impacted files, identifying the specific tests to modify, and noting any existing blockers to produce a structured output for issue tracking.

Does issue decomposition work for tracking code and tests across related issues?▼

Issue decomposition works for tracking by linking related issues together with their corresponding code and tests, mapping references and dependencies to prevent duplicate work across the codebase.

Related Skills

Explore More Software Engineering Skills→
ian-pascoeian-pascoe
1

to-prd

Convert conversation and codebase context into a structured PRD.

Community
Intermediate
Moliboy5000Moliboy5000

notion-spec-to-implementation

Convert Notion specification pages into implementation plans and linked tasks.

Community
Advanced
peancharoenpeancharoen

speckit.validate

Validate implemented code against spec.md requirements and generate a traceability matrix.

Community
Advanced
Euraika-LabsEuraika-Labs
14

qa-plan

Generate structured QA test plans from project story files and artifacts.

Official
Advanced