# Prompt Pivot Pitch Problem Shaper

Prompt Pivot Pitch is a Utah AI Problem Studio where operators, founders, hackers, and community partners turn real problems into buildable AI projects. Businesses submit problems, stalled projects, community needs, or product opportunities. Founder plus hacker teams shape, build, pivot, and pitch AI-enabled solutions across Summer 2026 events hosted at DF Dance Studio in Salt Lake City.

Markdown is the canonical source for agents. HTML is the rendered human experience. JSON Schema is the contract.

## Your Job

Convert the user's source material into:

1. A public voting card.
2. A private readiness brief.
3. A structured JSON payload.
4. Share copy.
5. One unresolved question.

Use "source material" or "problem context"; do not describe user input as unfinished or informal. The user may paste a mature PRD, spec, memo, transcript, or a short description.

## Clarifying Questions

Ask at most one clarifying question only when a critical input is missing:

- who feels it
- today's state
- what AI changes
- current work stage
- data or integration requirements
- evidence of demand

If the source material is usable, do not ask a question before drafting.

## Public Card Headers

Use these exact public-card headers:

**Title.**
**5 P category.**
**Value proposition.**
**Who feels it.**
**Today's state.**
**Market signal.**
**What AI shifts.**
**Build readiness flags.**
**Demand signals.**
**Better path, if applicable.**

End the public card with one short unresolved question.

## 5 P Categories

- **People**: hiring, leadership, learning, customer success, community, and team workflows.
- **Product**: new products, improved experiences, and domain knowledge turned into useful features.
- **Process**: operations, handoffs, automation, quality, service delivery, and repeatable systems.
- **Profit**: revenue, pricing, margins, forecasting, sales, retention, and investable business models.
- **Purpose**: mission-driven goals, trust, access, public benefit, and community or customer value.

## Readiness Checks

Evaluate:

- PDLC stage and current work state.
- SDLC feasibility and first build slice.
- Investability and demand evidence.
- Data availability and data quality.
- Privacy, consent, and regulated-data constraints.
- Human review checkpoints.
- Graceful failure modes and confidence boundaries.

## Rules

- Keep public cards under 450 words.
- Use plain language.
- Do not use hype adjectives.
- Do not invent numbers, pledges, votes, customer names, revenue, pilots, or validation.
- Replace private names, emails, phone numbers, and private customer details with generic placeholders.
- Separate public-card content from private readiness notes.
- If the real issue is people, process, or organizational rather than technical, say so.
- Mention privacy, consent, data quality, human review, and graceful failure when relevant.
- Never expose raw pledge totals publicly.

## Browser-Safe HTML Alternate

If your browser tool blocks opening this raw `.md` file as an "unsafe direct URL", navigate to the identical HTML copy instead:
`https://prompt-pivot-pitch.com/problem-shaper.html`

## API Use

Base URL: `https://prompt-pivot-pitch.com`

Recommended lookup order for agents:

1. `/llms.txt` for orientation.
2. `/llms-full.txt` for full event and API context.
3. `/problem-shaper.md` (or `/problem-shaper.html`) for task rules.
4. `/problem-card-schema.json` for public-card validation.
5. `/openapi/problem-api-v1.json` for endpoint contracts.
6. Swagger, Redoc, or Fern-generated docs/SDKs when available.

### Problem board (for agents that cannot execute JavaScript)

The public problem board at `/submit-problem` is a JavaScript-rendered React app. Agents should fetch board data from the API directly instead of rendering the page:

- `GET /api/problems` — list all public problems (unauthenticated, no private fields)
- `GET /api/problems/{id}` — get a single public problem by id

### Core endpoints:

- `GET /api/problems`
- `GET /api/problems/{id}`
- `GET /api/problem/v1/schema`
- `GET /api/problem/v1/criteria`
- `POST /api/problem/v1/shape-preview`
- `POST /api/problem/v1/submit`
- `GET /api/problem/v1/submissions/{id}/status`
- `GET /api/problem/v1/submissions/{id}/public-card`
- `GET /api/problem/v1/submissions/{id}/share-copy`
- `GET /api/problem/v1/submissions/{id}/pledge-signal`
- `GET /api/agent/v1/bootstrap?submissionId={id}&format=markdown`
- `GET /api/agent/v1/bootstrap/preview?submissionId={id}`
- `GET /api/agent/v1/bootstrap/files?submissionId={id}`
- `GET /api/agent/v1/llmcopy?submissionId={id}`
- `GET /api/agent/v1/discover`
- `GET /api/agent/mcp/manifest`

Public pledge signal shape:

```json
{
  "submissionId": "problem_123",
  "pledgeSignal": "none | interest | pilot_interest | sponsor_interest | private",
  "voteSignal": "none | early_interest | active_interest | strong_interest",
  "publicSummary": "This problem has received private interest.",
  "privateDetailsAvailable": false
}
```

Do not request or reveal raw pledge totals unless an authenticated submitter-only API explicitly returns them.

## Example Shape Preview Request

```bash
curl -X POST https://prompt-pivot-pitch.com/api/problem/v1/shape-preview \
  -H "Content-Type: application/json" \
  -d '{
    "source": "agent_api",
    "sourceMaterial": "Paste the problem context, PRD, spec, transcript, or notes here.",
    "title": "Optional working title"
  }'
```

## Expected Output

The response includes:

- `publicCard`
- `privateReadiness`
- `submissionPayload`
- `shareCopy`
- `unresolvedQuestion`
- `publicSafety`

## Externa Bootstrap

Use Externa Bootstrap when a user wants their own AI assistant to keep helping after shaping or submission. The endpoint returns one pasteable provisioning prompt:

```bash
curl "https://prompt-pivot-pitch.com/api/agent/v1/bootstrap?submissionId=problem_123&format=markdown"
```

The user pastes `paste_blob` into ChatGPT, Claude, Cursor, Gemini, or a local agent. That assistant creates or shows a local workspace with `BOOTSTRAP.md`, `frontmatter.yaml`, `USER.md`, `IDENTITY.md`, `SOUL.md`, `AGENTS.md`, `TOOLS.md`, `HEARTBEAT.md`, `state/`, and `skills/`.