Zensu
Claude Code Plugin · FSL-1.1 · v0.6.6

Zensu for Claude Code

Plugin that turns Claude Code into a Product Lifecycle Manager. Strict TDD, parallel 5-perspective code review, feature tracking — bundled as one install.

Get the plugin View on GitHub
3
agents
zensu-plm · code-reviewer · review-aspect
10
slash skills
bootstrap · implement · tdd · security · ghost +5
9
automatic hooks
plan → TDD → review → auto-fix
60+
MCP tools
features, security, tiers, journeys
How it works

Three layers. One flow.

Plan with zensu-plm. Build with /zensu:tdd in the main thread. Track in the web dashboard. Each layer does one job — they hand off automatically.

Planning

zensu-plm

  • /zensu:bootstrap
  • /zensu:ghost-scan
  • /zensu:implement
Implementation

/zensu:tdd

  • RED → IMPL → GREEN
  • 5× review-aspect
  • code-reviewer
  • auto-fix loop
  • self-review
Tracking

Zensu Platform

  • Feature dashboard
  • Release gates
  • Security posture
  • Tier matrix
  • Docs & wiki
  • Assignments & ownership
Install

One command. Everything wired.

The plugin auto-configures the MCP server, registers agents, and installs hooks. OAuth opens automatically on first use — no API key needed unless you're in CI.

Recommended

Project scope

Per-project install. Hooks fire for this repo only. .zensu/config.json overrides defaults. 

# Inside your repo
claude plugin install zensu --scope project

User scope (global)

Available across every project. Configure once via ~/.zensu/config.json. 

# Anywhere on your machine
claude plugin install zensu --scope user

For CI / headless agents

OAuth isn't available in CI. Register a user-scope MCP entry that forwards your API key — exporting the key alone won't attach it. 

# GitHub Actions, GitLab CI, etc.
claude mcp add zensu --transport http \
  --url https://mcp.zensu.dev/mcp \
  --header "Authorization: Bearer $ZENSU_API_KEY" \
  --scope user
What's inside

Inside the install.

Agents plan. Skills act. Hooks chain the workflow without manual handoff.

3 specialist agents

zensu-plm orchestrates the lifecycle. review-aspect runs the 5 review perspectives in parallel — one each, read-only. code-reviewer consolidates them: conventions, bugs, architecture, tests, security.

10 slash skills

/zensu:bootstrap · /zensu:implement · /zensu:tdd · /zensu:plan-review · /zensu:security-review · /zensu:ghost-scan · /zensu:pulse · /zensu:self-review · /zensu:reset-review-limit · /zensu:zensu-help

9 automatic hooks

Plan-approved → TDD. Implementation → parallel 5-aspect review → in-thread auto-fix loop with a max-rounds guard → self-review. A Stop-hook backstop guarantees the chain; plus session banner, pulse, and a test-run witness log.

60+ MCP tools

Feature CRUD, security analysis, tier matrix, user journeys, roadmaps, ghost scans, bootstrap, wiki, knowledge search, source-file linking.

Privacy-first journal

Pulse logs tool usage and feature context — never code content. 90-day retention, configurable.

Self-hostable

Point Claude Code at your own endpoint with claude mcp add --url … --scope user to keep all data on your infrastructure. Works without a Zensu account at all.

Source-available

FSL-1.1-Apache-2.0. Use it for any Permitted Purpose — internal, commercial, forks, client work — and each release converts to Apache 2.0 after two years. Source on GitHub; no license server, no telemetry beyond the MCP endpoint you configure.

Token economy

Specialized agents. Lean sessions.

Every Zensu agent works in its own context, not yours. zensu-plm carries the 63-tool MCP surface and lifecycle conventions so your session never loads them, then hands back a one-line summary. When the review chain fires, five read-only review-aspect agents spawn in parallel — each loads one checklist (conventions, bugs, architecture, tests, security) and nothing else. Each returns just its findings; the main thread merges them. Many expert perspectives, one merged report, your token budget intact.

Workflows

Three paths through the lifecycle.

Slash commands compose. Hooks chain them. You ship faster because the handoff is automated.

New product

From idea to release

Bootstrap, plan, hand off — five strict steps.

  1. Bootstrap

    Vision → product, features, journeys, security profiles.

    /zensu:bootstrap

  2. Implement

    Load context, plan, hand off.

    /zensu:implement ZEN-001

  3. TDD auto-runs

    Plan-approved hook delegates to the /zensu:tdd skill in the main thread.

    /zensu:tddhook

  4. Review auto-runs

    Implementation done → 5 parallel review-aspect agents, merged by code-reviewer.

    review-aspect ×5code-reviewer

  5. Release gate

    STRIDE threat model + security checks.

    /zensu:security-review
Existing codebase

Adopt incrementally

Ghost-scan, classify, fill gaps without a rewrite.

  1. Ghost-scan

    Discover undocumented features.

    /zensu:ghost-scan

  2. Review candidates

    Batch approve, filter by component.

    ghost_batch_review

  3. Security baseline

    Classify, tag OWASP/compliance.

    /zensu:security-review

  4. Fill test gaps

    TDD over untested features.

    /zensu:tdd
Quick feature

One ticket, full guardrails

TDD plus 5-perspective review on a single feature.

  1. Implement

    Context-aware, no full bootstrap.

    /zensu:implement ZEN-042/zensu:tdd

  2. Auto-review

    Hooks trigger code-reviewer.

    code-reviewerhook
Why this plugin is different

TDD that can't be skipped.

/zensu:tdd runs the full RED → IMPL → GREEN cycle in the main thread — but a PreToolUse FSM gate blocks every Edit, Write, or MultiEdit that doesn't match the declared phase. IMPL can't fire without a prior RED_FAIL marker for the same step, and a Stop-hook backstop guarantees the review chain runs. The cycle is enforced by the harness, not by prompt discipline.

Configurable

Agentic loop. Your control.

Every layer of the autonomous chain — plan-approved → TDD → code review → auto-fix — is opt-out, gated, or capped. Configure once via ~/.zensu/config.json globally, or per-project via $CLAUDE_PROJECT_DIR/.zensu/config.json. The loop runs only as far as you let it.

Install the plugin. Ship the feature.

FSL-1.1-Apache-2.0, source-available. Works without a Zensu account — and auto-links artifacts when connected.

View on GitHub Read the README