Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By bpainter
The Slalom Solution Factory — orchestrates the Frame → Draft → Polish → Ship pipeline for producing solution kits (8 deliverables) from idea to promoted artifact. Cowork-native: walks users through the intake via AskUserQuestion, sequences specialist skills across stages, applies brand and visual toolchain, routes promoted solutions to the right canonical home (10_Practice/Offerings/Solutions for DXP; 40_Library/Solution_Briefs for general).
npx claudepluginhub bpainter/composable-dxp-claude-marketplace --plugin solution-factoryStart a new solution end-to-end (Frame → Draft → Polish → Ship). Default for new chats in the Solution Factory Cowork project.
Run Stage 2 (Draft) — markdown drafting of all 8 deliverables. Calls specialty skills from consulting, marketing, brand, cx, facilitation, design plugins as needed.
Run only Stage 1 (Frame) — the intake walkthrough. Output is a filled 00_Intake_Brief.md in WIP/. AskUserQuestion-driven for discrete fields; conversational for free-text.
Run Stage 3 (Polish) — generate visuals via the canonical toolchain (Napkin / Figma / PowerPoint native / higgsfield / Flaticon), format markdown to PPTX/PDF/HTML, apply brand. Optional Composable DXP microsite.
Run Stage 4 (Ship) — Quality Gates checklist, cross-document consistency check, dual-routed promotion (Composable DXP → 10_Practice; Slalom default → 40_Library), reference stub creation, practice catalog update.
Worker agent that promotes a finished solution from WIP to its canonical home, routing by Brand. For Composable DXP secondary solutions: copies to 10_Practice/Offerings/Solutions/{Tier}/[Solution-Name]-[YYYY-MM]-Slalom/, then delegates to solution-factory-stub-generator for the library reference stub at 40_Library/Solution_Briefs/. For Slalom default solutions: copies to 40_Library/Solution_Briefs/[Solution-Name]-[YYYY-MM]-Slalom/. Generates the hybrid promoted folder README.md with frontmatter + One-Pager content + kit index. Updates the practice catalog where applicable. Returns canonical and stub paths.
Worker agent that creates a new WIP folder for a solution. Called by solution-factory-frame after the Round 1 (solution name + brand) AskUserQuestion is captured. Creates 60_Digital_Manufacturing/Solution_Factory/WIP/[solution-name]/, copies the Intake_Brief.md template into it as 00_Intake_Brief.md, copies the eight deliverable templates from Templates/ as 01_*.md through 08_*.md, and creates the assets/ subfolder structure. Returns the absolute paths so the caller can surface them to the user.
Worker agent that creates the single-file library reference stub for Composable DXP secondary solutions promoted to 10_Practice/Offerings/Solutions/. The stub lives at 40_Library/Solution_Briefs/[Solution-Name]-[YYYY-MM]-Slalom.md and is a small markdown pointer back to the canonical practice path — discoverability surface without duplication. Single source of truth: the canonical practice folder; this is just the pointer.
Stage 2 orchestrator for the Solution Factory — Draft. Sequences the markdown-first drafting of all 8 deliverables (One-Pager, Sales Enablement Kit, Discovery Workshop, First Call Deck, Case Study, Email Templates, Handoff Packet, Marketing Handoff). Calls specialty skills from consulting, marketing, brand, cx, facilitation, and design plugins as needed. Pauses for review at the end of each deliverable (or batches review of the trio One-Pager + Sales Enablement Kit + First Call Deck per user preference). Output: 8 markdown files in WIP/. Also known as: solution drafting, deliverable authoring, draft stage runner.
Stage 1 orchestrator for the Solution Factory — Frame. Walks the user through the intake using AskUserQuestion for discrete decisions and conversational input for free-text fields. Captures the 5 required calls (Reframe / Deb Oler / Buyer State / Posture / Tier) plus the rest of the intake (problem, components, capabilities, industries, buyer personas, listen-fors). Outputs a filled `00_Intake_Brief.md` in `WIP/[solution-name]/`. Calls the `solution-factory-scaffolder` agent to set up the WIP folder structure. Routes to `solution-factory-draft` when the readiness check passes. Also known as: intake walkthrough, solution intake, frame stage runner.
Stage 3 orchestrator for the Solution Factory — Polish. Generates visuals using the canonical toolchain (Napkin, Figma+Mermaid, PowerPoint native, higgsfield with nano banana / chatgpt 2 / Seedance, Flaticon). Formats markdown to output (16:9 PPTX via PowerPoint MCP, 8.5×11 PDF via Word MCP, optional Composable DXP microsite via Vercel). Applies brand (Slalom default vs. Composable DXP secondary). Output: PPTX/PDF/HTML files at the top level of WIP. Also known as: visual + format + brand stage, polish runner.
Stage 4 orchestrator for the Solution Factory — Ship. Runs the Quality Gates checklist (15 unified anti-patterns + ~10 SF-specific gates), runs the cross-document consistency check, then promotes via the dual routing logic (Composable DXP secondary → 10_Practice/Offerings/Solutions/{Tier}/[Name]; Slalom default → 40_Library/Solution_Briefs/[Name]). Creates the library reference stub for DXP solutions. Updates the practice catalog. Calls `solution-factory-promoter` agent for the file-system work. Output: kit at canonical home + (optional) reference stub + WIP archived. Also known as: quality gates + promote, ship runner, solution finalization.
Advice skill for the Solution Factory. Inspects the WIP/ folder at 60_Digital_Manufacturing/Solution_Factory/ and reports on active solutions — which are at which stage (Frame / Draft / Polish / Ship), how complete each is, what's blocking, what's stale. Optionally inspects the canonical promotion targets (10_Practice/Offerings/Solutions/ and 40_Library/Solution_Briefs/) to report on recently shipped solutions. Read-only — does not modify anything. Also known as: WIP status, solution status, solution factory dashboard.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
v9.42.3 — Patch release for cursor-agent smoke checks in untrusted workspaces. Run /octo:setup.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Claude tooling skills for Cowork and Claude Code. Two skills: claude-plugin-creator scaffolds new plugins (folder structure, manifest, .plugin build, Cowork install) with empirically-established validation rules; claude-orchestrator designs the orchestration layer for new Cowork projects (CLAUDE.md routing, multi-phase commands, agent teams). One slash command (/plugin-help).
Seven behavioral-economics specialists grounded in canonical sources — Kahneman's Thinking Fast and Slow, Thaler & Sunstein's Nudge, Ariely's Predictably Irrational, and Wendel's Designing for Behavior Change — plus Slalom's 6-stage Behavioral Design Model. Six ready-to-use templates: Behavioral Profile, Choice Architecture, Nudges/Biases, Intervention Design, Use-Case Scoring, Use-Case Validation.
Eleven innovation specialists grounded in canonical sources — Christensen's Innovator's Dilemma, Dyer/Gregersen/Christensen's Innovator's DNA, Furr & Dyer's Innovator's Method, Doblin's Ten Types, Ramanujam & Tacke's Monetizing Innovation, Innovation Lab Excellence, Kelley's Ten Faces, Catmull's Creativity Inc, Dyer/Furr/Lefrandt's Innovation Capital, Rogers's Driving Digital Strategy, Tushman/Anand's Why Digital Transformations Fail, and Kane et al's Technology Fallacy — plus HBR Must-Reads on Innovation and Design a Better Business. Skills cover strategy, portfolio governance, value engineering across horizons, JTBD discovery, lean validation, ten-types diagnosis, willingness-to-pay monetization, lab design, disruption analysis, creative leadership/political capital, and digital transformation. One agent (innovation-agent) sequences them. Eight slash commands (audit, strategy, portfolio, discover, validate, value-case, charter, disruption-test) provide high-leverage recurring operations. Six templates: Three Horizons canvas, Ambition Matrix, JTBD Interview Guide, Ten Types diagnostic, Value Engineering canvas, Innovation Charter.
Leadership coaching, people-management, hiring, meetings and cadences, goal-setting, transitions, and stoic perspective. Seven specialized skills under one orchestrating agent. The two original skills (executive coach for neurodivergent leaders, people-leader for everyday craft) are joined by skills for hiring, meetings & cadences, onboarding & transitions, goals & OKRs, and stoic perspective. Each skill carries deep reference files distilled from canonical leadership texts — Hire With Your Head, The First 90 Days, Radical Focus, Drive, Good to Great, The Coaching Habit, Never Split the Difference, Meeting Design, The Effective Manager, Managing Humans, The Manager's Path, A Guide to the Good Life, How F*cked Up Is Your Management, Peopleware, Scaling Teams, Performance Appraisal Phrase Book, Exactly What to Say, How We Talk, Radical Candor, and 7 Habits.
Six brand specialists: strategy (positioning, narrative, voice, audience), naming (five-category framework, six-step process), identity-system (logo direction, color, type, photography, iconography), voice-tone (attributes with not-X pairings, tone register matrix, filler-words bans), guidelines-composer (9-chapter deliverable, sized to brand context), and audit (drift detection across identity, voice, surface application, governance). Outputs feed the design plugin and marketing plugin.
The Composable DXP plugin marketplace for Claude. 18 plugins, 182 skills, packaged for Claude Code (CLI), Claude Desktop (Cowork mode), and drag-and-drop install.
Marketplace name: composable-dxp (the value in .claude-plugin/marketplace.json)
Repo: https://github.com/bpainter/composable-dxp-claude-marketplace (public, personal)
# Cowork (Git URL — Cowork requires Git, not local paths)
claude plugin marketplace add https://github.com/bpainter/composable-dxp-claude-marketplace.git
claude plugin install <plugin>@composable-dxp
# Claude Code (also accepts the local path)
claude plugin marketplace add "/Users/bermon.painter/Library/CloudStorage/OneDrive-Slalom/Slalom Second Brain/80_Skills_and_Agents"
claude plugin install <plugin>@composable-dxp
For full install paths (Cowork, Claude Code, drag-and-drop), see INSTALL.md.
80_Skills_and_Agents/
├── README.md # this file (conventions and structure)
├── INSTALL.md # how to install the marketplace and plugins
├── .claude-plugin/
│ └── marketplace.json # marketplace manifest — lists every plugin
├── Memory/ # cross-cutting working memory (CLAUDE.md, people, glossary, etc.)
│ # NOT a plugin — read by Claude every session
├── Plugins/ # built .plugin files (build artifacts)
│ └── <plugin>.plugin
└── <plugin-name>/ # one folder per plugin SOURCE (e.g., obsidian/, claude/)
└── ... (see "Plugin layout" below)
The marketplace itself is a single Claude plugin marketplace. Tools that consume marketplaces (Claude Code CLI, Claude Desktop via Cowork) read .claude-plugin/marketplace.json to discover what's installable.
Memory/ is not a plugin. It's the user's working memory and shared knowledge base, read every session by Claude, and shared across all plugins.
Plugins/ holds built artifacts — the .plugin files (renamed ZIPs) that get dragged into Claude Desktop's Personal Plugins panel for install. The source of each plugin lives in its own folder at the marketplace root (e.g., obsidian/, claude/); the .plugin files in Plugins/ are derived from those sources via the build process described in INSTALL.md.
Every plugin under this marketplace follows this exact shape. Deviations break tooling.
<plugin-name>/ # plugin SOURCE (lives at marketplace root)
├── README.md # plugin overview for humans
├── .claude-plugin/
│ └── plugin.json # plugin manifest for Claude (only `name` is required)
├── references/ # plugin-wide shared references (optional)
│ └── <plugin>-foundations.md
├── skills/ # auto-discovered by Claude
│ ├── <plugin>-<skill-name>/ # one folder per skill
│ │ ├── SKILL.md # required — frontmatter (name, description) + body
│ │ └── references/ # skill-specific deep references (typical, 1–3 files)
│ │ └── <topic>.md
│ └── ... (more skills)
├── agents/ # auto-discovered by Claude (workers)
│ └── <plugin>-<agent-name>.md # single file per agent, Claude Code agent format
└── commands/ # slash commands (optional)
└── <command-name>.md
| Piece | Required? | Purpose |
|---|---|---|
README.md | recommended | Plugin overview, opinion, roadmap, written for humans browsing the repo |
.claude-plugin/plugin.json | required | Manifest Claude reads. Only name is strictly required; version, description, author, keywords, license are optional. Don't include empty optional fields (e.g., "homepage": "") — they fail manifest validation |
references/ | optional | Plugin-wide shared references at the plugin root. From a SKILL.md, cite as ../../references/<file>.md |
skills/ | optional | Skills (one folder per skill, each with a SKILL.md). Auto-discovered by Claude |
skills/<skill>/SKILL.md | required if folder exists | The skill itself — YAML frontmatter (name, description) + body |
skills/<skill>/references/ | optional | Skill-specific deep references (frameworks, checklists, examples). From the SKILL.md, cite as references/<file>.md |
agents/ | optional | Workers that act on user data — Claude Code agent file format (one file per agent) |
commands/ | optional | Slash commands — single Markdown files with description: frontmatter and a body that names the skill or workflow to invoke |
A plugin can have any combination of skills, agents, and commands. Empty folders are fine if you intend to fill them later.