Guides developers through the Shape Up methodology: frame problems, shape solutions with code analysis, execute builds with TDD and hill charts, and ship features with ADR generation.
Use this skill to execute a shaped Package within a build session. Implements the full building process: orient on the codebase, pick a first piece (core/small/novel), integrate vertically with TDD, discover and map scopes, track progress with hill charts, and scope hammer when capacity runs low. For web projects, verifies with browser automation. Writes handover documents for multi-session continuity. Only use after a Package has Shape Go approval. Use when the user says "/build NNN" or "let's build feature NNN" or "start building NNN".
Use this skill whenever someone has a raw idea, feature request, bug complaint, or vague product concept that needs to be investigated before any solution design begins. This is the FIRST step in the Shape Up pipeline. Frame before you shape. If the user says "we need X", "what about Y", or provides any raw idea, use /frame to lock the problem, identify affected users, quantify business value, and set the time appetite. This answers: "Is this worth investing shaping time in?"
Use this skill to transform a framed problem (with Frame Go approval) into a shaped Package ready for a build commitment. Shaping requires deep codebase analysis — examining actual source code, data models, and architecture to define the technical wiring of the solution. Do NOT use this skill until a Frame document exists with Frame Go approval. Run /frame first if needed. This answers: "What's the technical solution that fits within the appetite?" Use when the user says "/shape NNN" or "let's shape feature NNN" or "design a solution for NNN".
Use this skill to conclude and archive a completed feature after building. Reads the entire feature folder (frame, package, hill chart, scopes, handovers), extracts architectural decisions, produces Architecture Decision Records (ADRs) in docs/decisions/, updates docs/architecture.md with new patterns and principles, renames the feature folder to -shipped, and regenerates the Shape Up project dashboard. This is the final step that turns implementation experience into recorded knowledge for the team. Use when the user says "/ship NNN" or "let's ship feature NNN".
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub tiago-peixoto/claude-shapeup --plugin shapeupBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Four Claude Code skills that teach your AI agent the Shape Up methodology. Fixed time, variable scope, zero hand-waving.
Frame the problem. Shape the solution. Build the code. Ship the knowledge.
Backlogs are where ideas go to die. Shape Up replaces the infinite todo list with a simple bet: pick a time budget, shape the work to fit, build it, ship it. This project gives Claude Code the vocabulary and guardrails to run that process with you — interactively, one feature at a time.
| Skill | What it does | Gate |
|---|---|---|
/shapeup:frame | Turns a vague idea into a locked problem statement with appetite | Frame Go |
/shapeup:shape | Deep codebase analysis → requirements, affordance tables, fit check matrix, Package | Shape Go |
/shapeup:build | TDD via RED/GREEN behavioral tests, hill charts, scope hammering, handovers for multi-session work | Ready to Ship |
/shapeup:ship | Extracts ADRs, updates architecture docs, archives the feature folder | Done |
Each skill is self-contained with its own reference docs — no external dependencies, no magic.
In Claude Code, run:
/plugin marketplace add tiago-peixoto/claude-shapeup
/plugin install shapeup
Type /shapeup:frame and follow the conversation.
.shapeup/
├── 2026-04-20-csv-import-framing/ # Active: being framed
│ └── frame.md
├── 2026-04-18-auth-refresh-shaped/ # Ready: waiting for a build bet
│ ├── frame.md
│ └── package.md
├── 2026-04-15-dashboard-v2-building/ # In progress
│ ├── frame.md
│ ├── package.md
│ ├── hillchart.md
│ ├── scopes/
│ └── handover-01.md
├── 2026-04-10-search-shipped/ # Done: decisions archived
└── index.md # Auto-generated dashboard
Multiple features can run in parallel. Each folder is a date-slug key — YYYY-MM-DD-<slug> —
with a status suffix (-framing, -shaped, -building, -shipped, -discarded). Date-slug
keys are collision-free across teammates: two developers can frame features on separate
branches without colliding on a shared counter. If two teammates pick the same slug on the
same day, the second folder gets a 4-hex disambiguator (2026-04-20-csv-import-bc89-framing).
Inside a -building feature, each scopes/<scope>.md tracks user-noticeable behaviors as
[RED] → [GREEN] (vertical slices the user can observe) rather than technical task
checkboxes. A scope is done when its must-have behaviors are [GREEN]. Legacy [ ]/[x]
scope files are still accepted for one release.
Invoke downstream skills with any of these key forms:
/shapeup:build 2026-04-20-csv-import/shapeup:build csv-import (works when the slug is unique across the project)/shapeup:build 001 (back-compat for features created before date-slug)The plugin installs three hooks:
phase-guard.sh (UserPromptSubmit) — blocks /shape, /build, /ship when gates
haven't been passed. Resolves any accepted key form to the correct feature folder and
verifies Frame Go / Shape Go / build-summary.md exists.ripple-check.sh (PostToolUse) — watches .shapeup/**/*.md edits and nudges the
agent when a change to one document likely affects another. Advisory only.commit-gate.sh (PreToolUse) — intercepts git commit and blocks a scope-completion
commit when the scope files, hill chart, and behavior states disagree. Runs the consistency
audit on the staged .shapeup/ diff so drift can't be committed.Shared libraries under hooks/lib/ back the "trust but verify" pattern that shape/build/ship
and the commit gate use:
resolve-feature.sh — accepts any key form, returns the feature folder path.check-consistency.sh — audits a feature folder for drift between scope behavior
states ([RED]/[GREEN], or legacy checkboxes), hill chart symbols, and the pre-ship
gate. Skills call it before marking a scope done and as the gate into /ship; FAILs must be
resolved, not silenced.commit-gate.sh — the gate library the commit-gate hook runs on the staged
.shapeup/ diff (see Hooks above)..claude-plugin/
├── plugin.json
└── marketplace.json
hooks/
├── hooks.json
├── phase-guard.sh
├── ripple-check.sh
├── commit-gate.sh
└── lib/
├── resolve-feature.sh
├── check-consistency.sh
└── commit-gate.sh
references/ # 9 shared methodology docs (00-glossary … 08-framing)
skills/
├── frame/
│ ├── SKILL.md
│ └── scripts/init-feature.sh
├── shape/
│ ├── SKILL.md
│ └── scripts/validate-package.sh
├── build/
│ ├── SKILL.md
│ └── scripts/update-hillchart.sh
└── ship/
├── SKILL.md
└── scripts/regenerate-index.sh
PRD-driven AI dev team control plane for Claude Code — agents, skills, and a GitHub-first sprint workflow.
AI-native BizDevOps rhythm manager for Claude Code — multi-role collaboration, change impact analysis, quality gates, goal-to-code traceability, and cross-session continuity
Intelligent workflow methodologies: analysis, evidence gathering, structured output, and research-enriched feature review with RICE/WSJF/Kano scoring
Ultra-compressed communication mode. Cuts 65% of output tokens (measured) while keeping full technical accuracy by speaking like a caveman.
Memory compression system for Claude Code - persist context across sessions
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.