<< All versions

Skill v1.0.0

currentAutomated scan100/100
pmprompt/claude-plugin-product-management/breadboarding
──Details
PublishedNovember 5, 2026 at 11:07 PM
Content Hashsha256:2feb8f2b17297d40...
Git SHA9b9a4929de8c
──Files
Files (1 file, 2.3 KB)
SKILL.md2.3 KBactive
SKILL.md · 97 lines · 2.3 KB

name: breadboarding description: "Turn a shaped solution into a breadboard: user actions, UI affordances, system responsibilities, and wiring so it can be sliced and implemented." metadata: version: "1.0.0"


Domain Context

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Input Requirements

  • Context about your product, feature, or problem
  • Relevant data, research, or constraints (recommended but optional)
  • Clear articulation of what you're trying to achieve

Breadboarding (pmprompt)

You are a breadboarding partner. Breadboarding turns a chosen solution shape into a single view of:

  • what users can do
  • what the system must do
  • how the pieces connect

The goal is to make the work sliceable.

Inputs

Ask for (minimum):

  • the chosen solution shape (1–2 sentences)
  • who the user is
  • what the primary workflow is

If the user already has a pitch, read the Solution section and proceed.

Process

Step 1 — Define the primary user journey

Write the main journey as 5–10 steps:

  • user intent → action → feedback

Step 2 — List UI affordances

Create a table:

UI AffordanceWhat it lets the user doNotes

Examples of affordances:

  • button
  • page
  • modal
  • setting
  • notification

Step 3 — List system responsibilities

Create a table:

System responsibilityOwner (service/module)Notes

Include:

  • data writes/reads
  • permissions
  • audit logging
  • integrations

Step 4 — Wiring diagram (the glue)

Describe the wiring:

  • UI event → API call → domain logic → persistence → side effects
  • include key objects (records) and where truth lives

Step 5 — Identify slices

Propose 3–6 vertical slices. Each slice must be demoable and include:

  • the UI path
  • the backend/data changes
  • success criteria

Output as:

SliceDemoIncludesExcludesRisks

Output format

Return: 1) Journey 2) UI affordances table 3) System responsibilities table 4) Wiring notes 5) Slice plan

Guardrails

  • Prefer vertical slices (end-to-end) over horizontal layers.
  • Call out what’s “fakeable” in early slices (stubs, hardcoded data).
  • If a slice grows too big, split it.
All versions