Kieran Klaassen
A creator who demonstrates the Compound Engineering plugin and Claude Code workflow patterns.
Key Highlights
- Kieran Klaassen is known here for demonstrating a Compound Engineering workflow built around Claude Code CLI.
- His approach uses a planning–coding–assessing–codifying loop to improve AI-generated code over repeated sessions.
- The workflow stores learnings in local documentation and updates root instructions so future prompts inherit prior insights.
- Newsletter coverage also highlights automated Playwright end-to-end testing and unattended execution patterns.
Kieran Klaassen
Overview
Kieran Klaassen is presented in the newsletter as a creator demonstrating advanced workflow patterns for Claude Code, centered on his Compound Engineering plugin. His system shows how AI-assisted software development can become more reliable over time by combining planning, coding, assessment, and codification into a repeatable loop. Rather than treating each AI coding session as isolated, Klaassen’s approach captures what worked into local documentation so future runs inherit those learnings.For AI Product Managers, this matters because it turns AI coding from a one-off productivity trick into an operational system. Klaassen’s workflow illustrates how teams can structure prompts, testing, documentation, and feedback loops so generated output improves across iterations. The examples highlighted in the newsletter also show how these patterns support unattended execution, persistent project memory, and automated browser testing—capabilities that are increasingly relevant for PMs managing AI-enabled product development.
Key Developments
- 2026-02-09 — Kieran Klaassen is featured demonstrating the full "How to Make Claude Code Better Every Time You Use It" system alongside Peter Yang. The workflow uses the Compound Engineering plugin for Claude Code CLI with slash commands such as `workflows plan`, `workflows work`, `assess`, and `triage` to run a planning–coding–assessing–codifying loop. The mention also notes that codified learnings are written as Markdown into `/docs/architecture-decisions/` and `/docs/solutions/`, while the root `claude.md` is updated so future planning prompts inherit those rules. Additional details include use of Opus 4.5 and Playwright for end-to-end browser test generation, screen recordings attached to pull requests, and an alias configuration that suppresses interactive permission prompts for unattended sessions.
- 2026-02-10 — Klaassen is mentioned again for demonstrating the Compound Engineering plugin for Claude Code CLI, emphasizing the same iterative loop of planning, coding, assessing, and codifying. The focus remains on capturing insights in a local docs directory so generated code quality improves over time.
Relevance to AI PMs
- Designing repeatable AI delivery systems: Klaassen’s workflow is a practical example of how to turn AI coding into a structured process with explicit stages for planning, execution, review, and knowledge capture.
- Building persistent project memory: The pattern of storing lessons in docs folders and updating `claude.md` shows PMs how to create reusable context that improves future AI outputs without depending on tribal knowledge.
- Operationalizing quality assurance: The use of Playwright-generated end-to-end tests, console inspection, and video artifacts demonstrates how AI workflows can include validation and auditability, not just code generation.
Related
- compound-engineering-plugin — The core plugin Klaassen demonstrates; it enables the structured Claude Code workflow and codification loop.
- claude-code — The execution environment where Klaassen’s slash-command workflow runs.
- peter-yang — Featured alongside Klaassen in the newsletter mention discussing the full system.
- playwright — Used in the demonstrated workflow for automated browser-based end-to-end testing and artifact generation.
- compound-engineering — The broader framework or methodology associated with the plugin and workflow patterns Klaassen showcases.
Newsletter Mentions (2)
“Kieran Klaassen demonstrates his Compound Engineering plugin for Claude Code CLI, using slash commands like workflows plan, workflows work, assess, and triage to run a planning–coding–assessing–codifying loop that captures insights in a local docs directory and iteratively improves generated code.”
#6 ▶️ How to Make Claude Code Better Every Time You Use It (Full System) | Kieran Klaassen Peter Yang Kieran Klaassen demonstrates his Compound Engineering plugin for Claude Code CLI, using slash commands like workflows plan, workflows work, assess, and triage to run a planning–coding–assessing–codifying loop that captures insights in a local docs directory and iteratively improves generated code.
“How to Make Claude Code Better Every Time You Use It (Full System) | Kieran Klaassen Peter Yang Kieran Klaassen demonstrates his Compound Engineering plugin for Claude Code CLI, using slash commands like workflows plan, workflows work, assess, and triage to run a planning–coding–assessing–codifying loop that captures insights in a local docs directory and iteratively improves generated code.”
#4 ▶️ How to Make Claude Code Better Every Time You Use It (Full System) | Kieran Klaassen Peter Yang Kieran Klaassen demonstrates his Compound Engineering plugin for Claude Code CLI, using slash commands like workflows plan, workflows work, assess, and triage to run a planning–coding–assessing–codifying loop that captures insights in a local docs directory and iteratively improves generated code. The compound-engineering-plugin appends codified learnings as Markdown under /docs/architecture-decisions/ and /docs/solutions/ , and updates the root claude.md so those rules are injected into every new workflows plan prompt. With Opus 4.5 and Playwright, Claude Code auto-generates end-to-end browser tests—logging into Gmail to exercise email signature and draft flows, clicking UI elements, inspecting console logs, and screen-recording a video artifact attached to the pull request. By defining alias CC="claude code --dangerously-skip-permissions" , all interactive permission prompts are suppressed, enabling fully unattended AI-driven sessions for commands like plan, work, assess, and PR creation.
Related
Anthropic's coding-focused agentic tool for building and automating software workflows. In this newsletter it is discussed as being integrated with Vercel AI Gateway and as a Chrome extension for browser automation.
A writer/observer mentioned for a post about how vibe coding is reshaping developer workflows. Relevant to AI PMs for workflow and interface trends.
A practice of capturing learnings from prompts and agent interactions to steadily improve system behavior over time. For PMs, it is a feedback-loop mindset for iterative AI product improvement.
Stay updated on Kieran Klaassen
Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.
Subscribe Free