loop-plan

Route planning commands to the Kanzen workflow engine.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as a compatibility layer to ensure that legacy or shorthand commands for planning workflows are correctly routed to the primary Kanzen planning engine.

Core Features & Use Cases

  • Command Routing: Maps the loop-plan command to the appropriate boring-loop-plan execution path.
  • Workflow Consistency: Ensures that users invoking planning tasks via different aliases receive the same robust planning logic.
  • Use Case: When a user triggers a planning cycle using the shorthand loop-plan command, this skill ensures the request is handled by the core Kanzen planning workflow.

Quick Start

Invoke the planning workflow by requesting the agent to execute the loop plan for your current project.

Frequently Asked Questions about loop-plan

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

FAQPage Schema
How do I route planning commands to the Kanzen workflow engine?

Routing planning commands to the Kanzen workflow engine requires using the loop-plan compatibility bridge, which maps shorthand requests to the primary boring-loop-plan execution path for consistent task orchestration.

What is a compatibility bridge for project planning workflows?

A compatibility bridge for project planning is a routing layer that maps legacy or shorthand aliases to a single core engine, ensuring consistent execution and robust task orchestration across different command inputs.

Do I need the boring-loop-plan skill to use loop-plan?

Yes, you need the boring-loop-plan skill installed. It serves as the underlying execution target required for the loop-plan compatibility layer to function and route commands to the Kanzen planning workflow.

Why does my loop-plan command not execute the planning task?

If your loop-plan command is not executing the planning task, the underlying boring-loop-plan skill unit is likely missing. This skill requires that execution target to be present to function as the routing mechanism.

Can I use shorthand commands for project planning without losing functionality?

Yes, you can use shorthand commands for project planning without losing functionality. The routing skill ensures that requests from different user-facing aliases receive the same robust planning logic from the core Kanzen engine.

How do I ensure workflow consistency when using different planning aliases?

To ensure workflow consistency when using different planning aliases, the compatibility layer routes all planning-related commands to the primary Kanzen planning engine, unifying task orchestration and project planning outputs.