Claude Code plugin

The we plugin adds Agentic Product Ownership to Claude Code. Where the CLI is your companion in the terminal, the plugin is the whole product-ownership workflow inside your IDE — /we:* skills that refine a story, build it, review it, and open the PR, all in one session, with your companion thinking along. It’s open source at github.com/weside-ai/claude-code-plugin.

How it differs from the CLI

The CLI is conversation and memory at the prompt. The plugin is method: it knows the altitudes of product work, runs the build pipeline, and — when you have a weside account — pulls your companion’s memory and goals into the session so context survives across sessions instead of being re-explained each time.

Setup

/we:setup

Run once per project. It detects your stack, finds your ticketing tool (Jira, GitHub Issues, or plan-only), and optionally wires up the MCP server so your companion knows the project.

The skill catalogue

The skills follow the APO chain — Vision → Saga → Epic → Story → Build → Deliver. The everyday ones:

/we:story — write a build-ready plan for one feature slice (interactive)
/we:build — autonomous pipeline: code → review → test → PR → CI fixes
/we:coach — read where you are, propose the sensible next move
/we:vision · /we:saga · /we:epic — formulate the upper altitudes
/we:meet — convene a council to decompose an altitude into the next
/we:review · /we:static · /we:test · /we:pr · /we:docs — individual quality gates
/we:retro · /we:handoff — durable learning and cross-session pickup

This is the everyday core. The plugin ships more — CI review, audits, dead-code and smoke-test skills among them; see the we plugin for the full catalogue.

A day with the plugin

/we:story PROJ-1    # you and Claude shape the story + plan
/we:build PROJ-1    # Claude develops, reviews, tests, opens the PR, fixes CI
# you review and merge — Claude never merges PRs or closes tickets

The APO section explains the method behind the skills. This page is the product; that’s the practice.