legacy

Outcome Engineering Plugin Marketplace

A Claude Code plugin marketplace for Outcome Engineering — spec-driven development where a durable map of your product drives all implementation.

/bootstrap interviews you about your product, then scaffolds a spec tree — the durable map that drives all implementation.

Philosophy

1. RTFM: Follow state-of-the-art (SOTA) model prompting guidance, such as structured prompts based on XML tags
2. KILO: Keep It Local and Observable — the golden source for all specifications lives locally within the project's Git repository

Quick Start

1. Install the spx CLI

npm install -g @outcomeeng/spx

The spx CLI is the developer tool for spec-driven development. Required by all engineering plugins.

2. Add the marketplace and install plugins

# Add the marketplace
claude plugin marketplace add outcomeeng/claude

# Spec-driven development (requires spx CLI)
claude plugin install spec-tree@outcomeeng

# Language plugins (install per project, require spx CLI)
claude plugin install python@outcomeeng
claude plugin install typescript@outcomeeng

3. Bootstrap your spec tree

> /bootstrap                       # set up a new spec tree

4. Author, implement, commit

> /author outcome for search       # author a new outcome node
> /author PDR for auth policy      # author a product decision
> /author ADR for caching strategy # author an architecture decision
> /apply                         # start the TDD flow
> /commit                          # commit with Conventional Commits

See the full tutorial for the complete workflow — from bootstrapping to handoffs.

Also available (no spx CLI required)

claude plugin install prose@outcomeeng       # writing and reviewing prose
claude plugin install claude@outcomeeng      # meta-skills for plugin development

Updating plugins

claude plugin marketplace update outcomeeng

Plugins

spec-tree

The core of Outcome Engineering. Three phases: spec-tree maintenance, implementation, commit.

/bootstrap in action — interactive product interview and scaffold

Step	Screenshot
Detect product — reads CLAUDE.md, identifies what the product does
Outcome hypothesis — what user behavior change do you expect?
Scope — what are the major concerns?
Shared infrastructure — should anything be an enabler?
Confirm — review the scaffold before creating files
Result — scaffold created with product spec, guides, and nodes