kli-planning

Generate phased implementation plans with verification gates from requirements and research.

26|3|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/kleisli-io/kli --skill kli-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kli-planning
Source: https://github.com/kleisli-io/kli/tree/main/plugin/skills/kli-planning
Command: npx skills add https://github.com/kleisli-io/kli --skill kli-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms research and requirements into detailed, phased implementation plans, preventing costly errors that amplify during development.

Core Features & Use Cases

  • Phased Planning: Breaks down large tasks into 3-7 incremental, testable phases.
  • Verification Gates: Defines clear automated and manual success criteria for each phase.
  • Artifact Reuse: Leverages existing research.md files to save time and tokens.
  • Use Case: When starting a new software feature, use this Skill to create a step-by-step plan, ensuring each part is verifiable before moving to implementation.

Quick Start

Use the kli-planning skill to create a detailed implementation plan for the new user authentication module.

Frequently Asked Questions about kli-planning

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

FAQPage Schema
How do I create a phased implementation plan for complex software features?

Define verification gates by setting clear automated and manual success criteria for each phase. This ensures every part of the software development task is verifiable before moving to actual implementation.

What is the best way to break down large software development tasks into testable phases?

The best way to break down large software development tasks is incremental task decomposition into 3-7 phases. This method enforces testability and clear boundaries, transforming requirements into an actionable and verifiable plan.

Do I need existing research files to generate an actionable software development plan?

You need structured input on requirements and research findings to generate an actionable plan. The planning process leverages existing research.md files for artifact reuse, saving time and tokens during task decomposition.

Why does planning errors amplify during software implementation and how to prevent it?

Planning errors amplify during implementation when task decomposition lacks testability and clear boundaries. Prevent this by enforcing incremental design and verification gates, ensuring each phase has defined success criteria before proceeding.