issue-update

Validate completed issue changes against open backlog and annotate impacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/KMakayee/playbook --skill issue-update-kmakayee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-update
Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/issue-update
Command: npx skills add https://github.com/KMakayee/playbook --skill issue-update-kmakayee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete issue closure by verifying whether a completed issue’s code changes create real, project-level impacts on other open issues.

Core Features & Use Cases

  • Conservative impact analysis: Compares the completed issue’s tracked and untracked changes against other open issues’ planned areas and acceptance criteria.
  • Structured annotation: Adds dated entries to the impacted issues’ Impacts section in tasks/issues.md with a short description of what changed and what to adjust.
  • Status finalization: Marks the completed issue as Done while leaving other issues’ statuses, priorities, and acceptance criteria unchanged.

Quick Start

Run issue-update for issue #123 after its implementation and review to update any impacted open issues in tasks/issues.md.

Frequently Asked Questions about issue-update

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

FAQPage Schema
How do I check if a code fix impacts other open backlog issues?

To check if a code fix impacts other open backlog issues, analyze the git diff of the completed change set against the acceptance criteria of non-Done issues in tasks/issues.md, then annotate affected issues with dated impact entries.

What is backlog impact analysis for completed issue work?

Backlog impact analysis for completed issue work is the process of validating tracked and untracked git changes against planned areas of other open issues to prevent missed cross-issue regressions before finalizing status closure.

How do I annotate affected issues in tasks/issues.md after committing a fix?

To annotate affected issues in tasks/issues.md, add dated entries under the impacted issues' Impacts section with a short description of what changed and what to adjust, leaving their original priorities and acceptance criteria unchanged.

When should I run an issue update for cross-issue regressions?

You should run an issue update for cross-issue regressions during post-implementation maintenance after an issue pipeline commits once, ensuring only the working tree diff represents the completed change set before marking the issue as Done.

Does issue closure modify the status of other non-Done backlog items?

Issue closure does not modify the status of other non-Done backlog items. The process only sets the completed issue status to Done while leaving other issues' statuses, priorities, and acceptance criteria completely unchanged.

Can I use git status and git diff to validate issue completion against open issues?

Yes, you can use git status and git diff to validate issue completion by comparing the working tree diff against the acceptance criteria of other open issues to identify and annotate any required adjustments conservatively.