implement

Execute approved implementation plans as dependency-ordered CI-green vertical slices.

6|2|Updated May 6, 2026
One-click install
npx skills add https://github.com/sek788432/Stock-Back-Test-System --skill implement-sek788432
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/sek788432/Stock-Back-Test-System/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/sek788432/Stock-Back-Test-System --skill implement-sek788432

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large implementation plans often fail because changes are made in bulk, tests are deferred, and broken states accumulate. This Skill enforces disciplined execution of an approved plan by splitting work into small, dependency-ordered vertical slices that each stay green against the repository's checks. ## Core Features & Use Cases - Slice-based execution: Breaks remaining work into the smallest verifiable vertical slices, each with recorded behavior, blockers, test seams, and acceptance gates. - Mandatory sub-skill integration: Requires the tdd skill for behavior changes and the five cpp-* skills (modern style, OOP design, performance, thread safety, static analysis) for any C++-bearing slice. - Gate discipline: Distinguishes merge-blocking, local, planned, and external checks; forbids advancing to a new slice while the current one has a known failing check. - Use Case: Given an approved multi-ticket plan for a C++ Qt application, execute each ticket as a red-green slice, run ./RunTest.sh and ./RunQuality.sh before submission, then hand off to the review skill. ## Quick Start Use the implement skill to execute this approved plan one CI-green vertical slice at a time.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I execute a large implementation plan without breaking the build?▼

Split the plan into dependency-ordered vertical slices and keep each slice green before starting the next. Run the narrowest authoritative tests during iteration and all affected-scope checks before accepting a slice.

What is a CI-green vertical slice in software development?▼

A vertical slice is the smallest change that delivers verifiable behavior end to end. CI-green means every applicable checked-in check passes for that slice, so the repository never accumulates known failures.

Does this workflow require test-driven development?▼

Yes, every behavior-changing or bug-fix slice must use the tdd sub-skill, making the change red before implementing it. Behavior-preserving refactors instead establish green characterization evidence first.

Can I skip C++ code quality checks for a small change?▼

No, any slice touching C++ must apply all five cpp-* skills covering modern style, OOP design, performance, thread safety, and static analysis. You may only record N/A with a reason for concerns the slice does not affect.

What happens when a required check fails mid-plan?▼

Stay on the current slice, diagnose the failure, fix production or test code, and rerun the check. A documented fast-mode pass is only interim evidence and never replaces the full required gate.