Shape product work
Reusable planning workflows for product and engineering work. Start from requirements, a proposed solution, evidence, or a focused uncertainty; move through framing, shaping, breadboarding, implementation handoff, drift checking, and reflection as needed; preserve explicit human decisions about direction, appetite, promotion, and scope.
MCP connector Server URL https://planning-skills-mcp-production.up.railway.app/mcpCopy Login None Protocol MCP 2025-11-25 Tools Reads data7 get_ artifact_ contractsget_ artifact_ templateget_ orchestration_ manifestget_ planning_ skillget_ skill_ resourcelist_ planning_ skillsrecommend_ planning_ workflow
Skills 14 in the ChatGPT listing
Breadboard reflection Compare accepted intent with implementation reality, assess realized conformance and effect separately, diagnose failures backward, and prepare explicit correction decisions. breadboarding Map current behavior, candidate shapes, or a selected design into places, affordances, stores, consequences, and wiring when concrete behavior needs clarification. dumplink Turn a selected, bounded project into sequenced vertical task groups with dependencies, risks, appetite-based cuts, acceptance checks, and a bounded handoff. Executable breadboards Turn a selected slice into fixtures, example runs, expected outputs, edge cases, and acceptance tests when it is ready for a buildable behavioral handoff. Feed planning context Prepare a compact context packet when an implementation agent needs the authoritative planning subset, execution contract, non-goals, and verification target for one active task group or slice. Framing doc Create a frame from research, notes, requests, or transcripts when the current problem, desired outcome, boundaries, and evidence need to become explicit. Interface contracts Define plain-language inputs, outputs, branches, errors, and open decisions when a selected slice crosses a meaningful data, service, or system boundary. Kickoff doc Create a builder-facing kickoff document from accepted planning artifacts when a team needs a durable reference organized by shaped product territory. Lead user research Inspect future-facing markets with Eric von Hippel's Lead User Method when teams need evidence-traceable trend, lead-user, and opportunity research. Planning router Inspect product-planning context and choose the smallest next move when no specific move is selected, while preserving fluid entry points and explicit commitment gates. shaping Shape ambiguous product work before implementation by iterating among requirements, solution shapes, fit checks, spikes, and candidate evidence while keeping commitment gates explicit. Sketch reconciliation Reconcile a screenshot, wireframe, mockup, whiteboard, or sketch with existing planning artifacts when visual evidence may change the frame, criteria, scope, or shape. statechart Derive states and transitions from an accepted breadboard when retries, timeouts, approvals, lifecycle stages, or multiple valid actions make behavior difficult to review. wayfinding Coordinate planning across multiple agent sessions as a shared map of dependent decision, evidence, prototype, and prerequisite tickets when one bounded route cannot fit in a single session.