kramme:structured-implementation-workflow

Plan, track, and implement work items using SIW's three-document workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of planning, tracking, and implementing work items without external services by using SIW's three-document workflow.

Core Features & Use Cases

  • Three-Document System: Main spec, open issues overview, and a temporary log to coordinate decisions and progress.
  • Lifecycle Coverage: Init, issue definition, planning, execution, and completion with a single source of truth.
  • Use Case: When coordinating a multi-week feature with dependencies, use SIW to keep specs, issues, and decisions synchronized across phases.

Quick Start

Start by running the SIW init and define-issue commands to set up your spec and first blockers.

Frequently Asked Questions about kramme:structured-implementation-workflow

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

FAQPage Schema
How do I track work items and project progress without external issue-tracking services?

A three-document workflow tracks work items locally using a main spec, open issues overview, and temporary log. It synchronizes decisions, specs, and progress across complex project phases without requiring external issue-tracking services.

What is the best way to plan and implement complex features with multiple dependencies?

Planning complex features with dependencies requires a structured implementation workflow covering initialization, issue definition, execution, and review. It enforces synchronized recording of decisions, progress, and spec updates to maintain a single source of truth.

How do I set up a local documentation workflow for project planning and tracking?

Set up local documentation for project planning by running initialization and define-issue commands to generate your spec and first blockers. This creates the required markdown files to coordinate decisions, track open issues, and record execution logs.

Can I synchronize spec updates and issue tracking across multiple project phases?

You synchronize spec updates and issue tracking across phases by maintaining a central spec document, an open issues overview, and a temporary log. This structure ensures decisions, progress, and spec changes remain aligned throughout the project lifecycle.

Does a markdown-based workflow work for multi-week project coordination?

Markdown-based workflows work for multi-week project coordination by using a three-document system to keep specs, issues, and decisions synchronized. It handles complex tasks and dependencies across extended timelines without relying on external services.