Quick Start

kli extends Claude Code with structured workflows for software engineering. You interact with kli through slash commands in Claude Code — Claude handles the task management, pattern matching, and coordination behind the scenes.

The kli Workflow

A typical kli session follows four phases:

1. Research

Explore a codebase or problem space before making changes:

/kli:research

Claude investigates the codebase, spawns specialized agents (codebase explorers, web researchers), and produces a research.md artifact summarizing findings.

2. Plan

Create a phased implementation plan:

/kli:plan

Claude reads the research artifact, designs an implementation strategy broken into phases, and presents it for your approval. Each phase has explicit success criteria and verification steps.

3. Implement

Execute the plan phase by phase:

/kli:implement

Claude works through each phase using TDD (Red → Green → Refactor), runs automated verification after each phase, and requests your manual approval before proceeding.

4. Reflect

After completing work, capture lessons learned:

/kli:reflect

Claude analyzes the session's observations and outcomes, extracting patterns that improve future workflows.

Other Useful Commands

Command	Purpose
/kli:handoff	Create a handoff document when transferring work to a new session
/kli:resume_handoff	Resume work from a previous handoff
/kli:create-task	Create an event-sourced task for tracking complex work
/kli:validate	Verify implementation against plan criteria

What's Happening Behind the Scenes

When you use kli commands, Claude uses MCP (Model Context Protocol) tools to manage tasks, record observations, and coordinate agents. You don't need to interact with these tools directly — the slash commands handle everything.

For details on what each command does internally, see the Command Reference, Workflow Reference, and Agent Reference sections.