kramme:siw:implement-issue

Explore codebases and create technical plans before implementing issues.

2|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-siw-implement-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kramme:siw:implement-issue
Source: https://github.com/Abildtoft/kramme-cc-workflow/tree/main/skills/kramme%3Asiw%3Aimplement-issue
Command: npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-siw-implement-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the structured initiation of a defined local issue by guiding thorough codebase exploration, Git state validation, and formal planning before any coding begins. It helps teams translate issue narratives into actionable technical plans, improving clarity and reducing rework.

Core Features & Use Cases

  • Issue discovery & summary extraction: Reads the issue file from siw/issues, extracting title, status, priority, and acceptance criteria to set alignment.
  • Planning & roadmap creation: Produces a detailed technical plan with tasks and suggested files to modify, based on the acceptance criteria.
  • Contextual documentation & progress tracking: Maintains a working context with progress notes, references to related tasks, and a ready-to-follow execution guide for the team.

Quick Start

Use the skill to start implementing an issue by providing its identifier, for example:

  • /kramme:siw:implement-issue G-001
  • /kramme:siw:implement-issue ISSUE-G-001

Frequently Asked Questions about kramme:siw:implement-issue

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

FAQPage Schema
How do I create a technical plan from issue files before writing code?

To create a technical plan from issue files, this skill reads issues from siw/issues, extracts acceptance criteria, validates git state, and generates a detailed execution roadmap with suggested files to modify before any coding begins.

What is the best way to automate issue triage and codebase exploration?

Automating issue triage and codebase exploration involves discovering issue files, extracting priority and status, and performing exhaustive codebase analysis to document decisions, tasks, and execution readiness.

How do I extract acceptance criteria from a local issue file for implementation?

You extract acceptance criteria by reading the issue narrative from siw/issues, parsing the title, status, and priority, and translating these defined requirements into actionable technical tasks and modification suggestions.

Can I validate git state and track progress during issue planning?

Yes, you can validate git state before initiating implementation, and the skill maintains contextual documentation with progress notes and references to related tasks to ensure continuous execution readiness.

Does this issue management workflow require a specific directory structure?

Yes, this issue management workflow requires issues to be located in the siw/issues directory to properly extract the issue narrative, acceptance criteria, and metadata for technical plan generation.

When should I not use automated planning for issue implementation?

You should avoid automated planning for issue implementation when your project lacks structured issue files in siw/issues, or when your workflow does not require exhaustive codebase exploration and git state validation prior to coding.