Skill

collect

Guided problem state collection across all three layers (optimization, market-making, experience)

Install

npx claudepluginhub jobrien127/plugin-marketplace --plugin solution-engine

Tool Access

This skill is limited to using the following tools:

Read Glob Grep Agent AskUserQuestion

Preview

Capture a complete problem state through guided conversation. Probes all three layers: optimization, market-making, and experience. Outputs `problem-state.yaml`.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

/collect

Capture a complete problem state through guided conversation. Probes all three layers: optimization, market-making, and experience. Outputs problem-state.yaml.

Pipeline Position

Requires: nothing (entry point)

Produces: $PROBLEMS_ROOT/$ARGUMENTS/problem-state.yaml

Advances: collect → complete

Instructions

Load ${CLAUDE_PLUGIN_ROOT}/templates/PROBLEM_TEMPLATE.md for the structure to fill.

If $ARGUMENTS is provided, use it as the problem name. Otherwise ask.

Walk the user through each section of the problem-state schema:

Core: problem, domain, actors, archetype
Layer 2 (optimization): objective, measurables, constraints, paradigms, uncertainty
Layer 1 (market-making): cold start, density, growth, network effects, economics
Layer 3 (experience): social model, communication, trust/safety, habits, onboarding
Behavioral: incentive risks, loss aversion, social preferences, temporal patterns
Environmental: weather, seasonality, venue dynamics
Infrastructure: scale, hosting, requirements, compliance

For each section: ask focused questions, detect gaps, suggest defaults where reasonable.

Set maturity markers based on what the user can specify vs. what's unknown.

Write the completed problem-state.yaml.

Update pipeline-state.json: set collect status to complete, current_stage to formalize.

/collect

Capture a complete problem state through guided conversation. Probes all three layers: optimization, market-making, and experience. Outputs problem-state.yaml.

Pipeline Position

Requires: nothing (entry point)
Produces: $PROBLEMS_ROOT/$ARGUMENTS/problem-state.yaml
Advances: collect → complete

Instructions

Load ${CLAUDE_PLUGIN_ROOT}/templates/PROBLEM_TEMPLATE.md for the structure to fill.
If $ARGUMENTS is provided, use it as the problem name. Otherwise ask.
Walk the user through each section of the problem-state schema:
- Core: problem, domain, actors, archetype
- Layer 2 (optimization): objective, measurables, constraints, paradigms, uncertainty
- Layer 1 (market-making): cold start, density, growth, network effects, economics
- Layer 3 (experience): social model, communication, trust/safety, habits, onboarding
- Behavioral: incentive risks, loss aversion, social preferences, temporal patterns
- Environmental: weather, seasonality, venue dynamics
- Infrastructure: scale, hosting, requirements, compliance
For each section: ask focused questions, detect gaps, suggest defaults where reasonable.
Set maturity markers based on what the user can specify vs. what's unknown.
Write the completed problem-state.yaml.
Update pipeline-state.json: set collect status to complete, current_stage to formalize.