loop-implement

Route loop-implement requests to the primary Kanzen implementation workflow.

45|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/hachej/boring-ui --skill loop-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-implement
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skill-library/kanzen/v1/loop-implement
Command: npx skills add https://github.com/hachej/boring-ui --skill loop-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as a compatibility layer to ensure that legacy or shorthand calls to the loop-implement workflow are correctly routed to the primary Kanzen implementation system.

Core Features & Use Cases

  • Workflow Routing: Redirects generic loop-implement requests to the specialized boring-loop-implement handler.
  • Standardization: Ensures consistent execution of Kanzen-based agent workflows across different entry points.
  • Use Case: When a user triggers a loop-implement command, this skill ensures the agent correctly identifies and executes the intended boring-loop-implement logic instead of failing or executing incomplete code.

Quick Start

Invoke the boring-loop-implement skill to execute the actual Kanzen implementation workflow.

Frequently Asked Questions about loop-implement

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

FAQPage Schema
How do I route legacy loop-implement workflow requests to a Kanzen implementation system?

You need a compatibility bridge that redirects legacy loop-implement workflow requests to the primary Kanzen implementation system. This skill intercepts generic loop-implement commands and ensures they reach the correct boring-loop-implement handler for proper execution.

Why does my agent fail when triggering a loop-implement command in the Boring UI framework?

Your agent fails because the generic loop-implement command lacks a compatibility bridge to route it to the primary Kanzen implementation system. Without this routing layer, the agent cannot identify and execute the intended boring-loop-implement logic, resulting in incomplete code.

Do I need the boring-loop-implement skill to use this compatibility bridge?

Yes, the boring-loop-implement skill unit is required as the primary execution target. This compatibility bridge only routes requests to the primary Kanzen implementation system, meaning the actual workflow logic resides entirely within the boring-loop-implement handler.

What is a compatibility layer for agent-centric development workflows?

A compatibility layer for agent-centric development workflows is a routing mechanism that standardizes how generic commands are processed. It ensures that legacy or shorthand calls to a loop-implement workflow are correctly redirected to a specialized implementation system for consistent execution.

Can I use loop-implement to standardize Kanzen workflows across different entry points?

Yes, you can use loop-implement to standardize Kanzen workflows across different entry points. It ensures consistent execution of agent-centric development tasks by redirecting all generic compatibility-based loop-implement requests to the primary boring-loop-implement handler.