Skip to the content.

CLike at a glance

CLike at a glance

CLike turns an idea into a running, documented solution — and keeps evolving it release after release — while AI does the writing and CLike decides what is verified, promoted and delivered. This page walks through the picture area by area, with links to the details.

Inputs

What a project starts from, read by the phases as context (never as instructions):

Details: context-sources.md, commands.md.

Who writes

Details: local-agents.md, integrations/bmad/COMMANDS.md.

Harper lifecycle

IDEA → SPEC → PLAN → ( KIT → EVAL → GATE )* per REQ → FINALIZE

Details: harper-workflow.md, auto-eval.md, git-and-promotion.md.

The next release

/idea --extend evolves a delivered project: the new release (docs/inputs/vN/) is merged into IDEA, SPEC and TECH_CONSTRAINTS, and the PLAN receives new REQs typed ADDED, MODIFIED (naming the checks of a delivered REQ it supersedes) or REMOVED. Delivered REQs stay read-only, the baseline is tagged v<N-1>, and an EXTEND report carries CLike’s own verification. Then the same loop runs on the new REQs.

Details: commands.md (/idea --extend), architecture/ADOPT_AND_IDEA_EXTEND.md.

Governance

Details: auto-eval.md, ../SECURITY.md.

Runtime

Everything runs locally with Podman or Docker:

Details: setup-and-runtime.md, mcp.md, howto-mcp-project.md, howto-mcp-bmad-claude.md.

What you get

CLike is multi-language and stack-agnostic: Python, TypeScript, Java, Go, .NET, infrastructure — the rules are CLike’s, the stack is the project’s.