implement

Name: implement
Availability: InStock
Author: vibercoder79

Convert Linear user stories into committed code via an 8-step gated workflow.

8|9|Updated Mar 9, 2026

Search Tags:#acceptance criteria #git commit #linear issues #gated implementation #spec gate #governance validation #post-implementation testing

Ready to run

npx skills add https://github.com/vibercoder79/KI-Masterclass-Koerting- --skill implement-vibercoder79

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/vibercoder79/KI-Masterclass-Koerting-/tree/main/implement
Command: npx skills add https://github.com/vibercoder79/KI-Masterclass-Koerting- --skill implement-vibercoder79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the gap between “a ticket exists” and “real code shipped,” by forcing a complete, non-skippable workflow that validates dependencies, governance artifacts, specs, and acceptance criteria before committing.

Core Features & Use Cases

8-step issue-to-code protocol: Turns a Linear story into implemented changes with planning, documentation updates, commit, and result reporting.
Hard Spec-File Gate (governance firewall): Stops implementation unless the required specs/CLAW-XXX.md spec exists (machine-enforced via the spec-gate.sh hook).
Post-implement validation: Runs code-quality checks, verifies acceptance criteria with evidence, performs architecture quick-checks, includes smoke testing, and documents security findings before marking the issue Done.

Quick Start

Run /implement to translate the current Linear “In Progress” issue into validated, committed code following the 8-step protocol.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I turn Linear issues into committed code automatically?▼

To turn Linear issues into committed code, this Skill orchestrates a gated 8-step implementation workflow that validates dependencies, governance artifacts, and acceptance criteria before executing a git commit.

What is a spec gate in software implementation?▼

A spec gate is a machine-enforced hook that stops implementation unless the required spec file exists, ensuring governance validation and required documentation are present before code changes begin.

How do I enforce acceptance criteria validation before marking a Linear issue Done?▼

You can enforce acceptance criteria validation by running a post-implementation protocol that verifies criteria with evidence, performs smoke testing, and logs security findings before marking the Linear issue Done.

Does this implementation workflow require manual code quality checks?▼

This implementation workflow does not require manual code quality checks, as it automatically runs post-implement validation including architecture quick-checks and smoke testing to ensure code quality.

What happens if the required specs are missing during issue implementation?▼

If the required specs are missing during issue implementation, the hard spec-file gate blocks the workflow entirely, preventing any code changes until the necessary governance artifacts are created.

Can I use this workflow for backlog-driven software changes in Linear?▼

Yes, you can use this workflow for backlog-driven software changes in Linear, as it specifically applies to scenarios where dependencies, context, and governance artifacts must be validated before committing.