GenAI PM
person2 mentions· Updated Feb 9, 2026

Kieran Klaassen

A creator who demonstrates the Compound Engineering plugin and Claude Code workflow patterns.

Key Highlights

  • Kieran Klaassen is noted for demonstrating a repeatable Claude Code workflow built around planning, coding, assessment, and codification.
  • His Compound Engineering plugin captures learnings in local documentation and feeds them back into future AI coding sessions.
  • The workflow shows how Playwright can be combined with Claude Code to automate browser testing and generate pull request artifacts.
  • For AI Product Managers, his examples illustrate how to make AI-assisted development more consistent, testable, and operational over time.

Kieran Klaassen

Overview

Kieran Klaassen is a creator highlighted for demonstrating a structured workflow around Claude Code, centered on his Compound Engineering plugin. In the newsletter references, he shows how AI coding sessions can be turned into repeatable operating systems using slash commands such as `workflows plan`, `workflows work`, `assess`, and `triage`. The core idea is a planning–coding–assessing–codifying loop that captures learnings locally and feeds them back into future runs.

For AI Product Managers, this matters because Klaassen’s workflow points to a practical pattern for making AI-assisted development more reliable over time. Rather than treating each coding session as isolated, his approach creates a persistent memory layer through local documentation, architecture decisions, and reusable instructions. That makes Claude Code outputs more consistent, testable, and aligned with team conventions—important qualities for PMs managing AI-enabled product delivery.

Key Developments

  • 2026-02-09 — Kieran Klaassen is featured demonstrating how to make Claude Code “better every time you use it” through the Compound Engineering plugin. The workflow uses slash commands like `workflows plan`, `workflows work`, `assess`, and `triage` to create an iterative loop for planning, implementation, evaluation, and codification. The mention also notes that the plugin stores learnings as Markdown in `/docs/architecture-decisions/` and `/docs/solutions/`, updates `claude.md` so rules are injected into future planning prompts, and pairs Claude Code with Opus 4.5 and Playwright to generate end-to-end browser tests and PR artifacts. It further references the alias `CC="claude code --dangerously-skip-permissions"` to suppress permission prompts for unattended sessions.
  • 2026-02-10 — Klaassen is again mentioned for demonstrating the Compound Engineering plugin for Claude Code CLI. The focus remains on the same planning–coding–assessing–codifying loop, emphasizing how iterative insight capture in a local docs directory can continuously improve generated code quality over repeated usage.

Relevance to AI PMs

  • Designing repeatable AI workflows: Klaassen’s approach offers a concrete pattern for turning ad hoc AI coding into a system with explicit stages—planning, execution, assessment, and codification. AI PMs can use this model to standardize how teams interact with coding agents.
  • Creating product memory for AI tools: The use of local docs, architecture decisions, and root instruction files shows how teams can preserve lessons learned and inject them into future agent runs. PMs can apply this idea to improve consistency across features, repos, and releases.
  • Operationalizing autonomous QA and delivery: The use of Playwright, generated browser tests, logs, recordings, and unattended CLI sessions illustrates how agent workflows can support testing and pull request creation. For PMs, this is relevant when evaluating how far AI can be trusted in delivery pipelines and where safeguards are needed.

Related

  • compound-engineering-plugin — Klaassen’s featured plugin, used to structure Claude Code workflows and capture codified learnings.
  • claude-code — The CLI environment where his workflow patterns are demonstrated.
  • peter-yang — Appears alongside Klaassen in the referenced content, indicating a contextual connection in the newsletter feature.
  • playwright — Used in the demonstrated workflow for auto-generated end-to-end browser tests, UI interaction, logging, and video artifacts.
  • compound-engineering — The broader system or framework associated with the plugin and workflow methodology Klaassen demonstrates.

Newsletter Mentions (2)

2026-02-10
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.

2026-02-09
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.

Stay updated on Kieran Klaassen

Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.

Subscribe Free