kramme:siw:restart-issues

Name: kramme:siw:restart-issues
Availability: InStock
Author: abildtoft

Delete DONE issues and renumber remaining issues within SIW prefix groups.

2|2|Updated Jan 15, 2026

Search Tags:#restart #issue-tracking #renumbering #siw #prefix-group #workflow-cleanup #file-rename

Ready to run

npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-siw-restart-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kramme:siw:restart-issues
Source: https://github.com/Abildtoft/kramme-cc-workflow/tree/main/skills/kramme%3Asiw%3Arestart-issues
Command: npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-siw-restart-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes all DONE issues and renumbers the remaining issues within each prefix group, keeping your SIW workspace tidy and consistent.

Core Features & Use Cases

Delete DONE issues across all groups.
Renumber active issues within each prefix group (G-, P1-, etc.) and update overview and logs accordingly.
Preserve group boundaries so phase issues remain within their own blocks.

Quick Start

Use the kramme:siw:restart-issues command to clean up completed issues and apply new numbering to active ones.

Frequently Asked Questions about kramme:siw:restart-issues

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

FAQPage Schema

How do I renumber remaining issues after deleting completed ones in SIW?▼

To renumber issues after deleting completed ones, this skill removes all DONE issues and automatically renumbers the remaining active issues within each prefix group, updating the SIW overview and logs accordingly.

What happens to historical DONE references when renumbering issues by prefix group?▼

When renumbering issues by prefix group, historical DONE references are preserved. The skill enforces per-group renumbering boundaries and performs synchronized updates across siw/issues, OPEN_ISSUES_OVERVIEW.md, and LOG.md artifacts.

Do I need to manually confirm scope changes when cleaning up my SIW issue tracker?▼

Yes, user confirmation is required when scope changes are involved during the SIW issue tracker cleanup. This ensures you maintain control over deletions and the renumbering workflow before the artifacts are modified.

Can I renumber phase issues independently within their own prefix blocks?▼

Yes, you can renumber phase issues independently. The skill preserves group boundaries so that phase issues remain within their own blocks, enforcing strict per-group renumbering for prefixes like G- and P1-.

What is the best way to clean up completed issues and synchronize SIW artifacts?▼

The best way to clean up completed issues and synchronize SIW artifacts is to use a workflow cleanup skill that deletes DONE issues, renumbers active ones by group, and applies synchronized updates across your issue files and logs.