Use this skill BEFORE changing what any agent in this plugin does — editing any skills/*/SKILL.md prompt, a references/* doc, or a behavioral contract. It drives the change strictly test-first with the isolated behavioral harness and an ablation negative-control, then commits cleanly with a single version bump. Invoke whenever you are implementing a new agent behavior or modifying an existing one in this repo, so prompt edits never ship on vibes.
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 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".
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".