profitable-build-spec

Files (1)

• SKILL.md

SKILL.md (first lines)

# Profitable Build Spec Skill

Input:

```text
$ARGUMENTS
```

## Mission

Define the smallest build that can prove buyer value.

## Required output

Create a build specification with:

1. **Offer being supported**.
2. **Buyer-facing demo path**.
3. **Must build** — only the essential pieces.
4. **Must not build** — features to defer.
5. **Manual steps allowed** — concierge, spreadsheet, human review, one-off setup.
6. **Fake-door steps allowed** — landing page, waitlist, mock dashboard, clickable prototype.
7. **Data required** — real, synthetic, scraped, customer-provided, public.
8. **Success criteria** — buyer-visible acceptance criteria.
9. **Verification criteria** — how to prove each criterion.
10. **Failure modes** — likely failure points.
11. **Implementation plan** — staged tasks with dependencies.
12. **Timebox** — maximum build time before reassessment.

## Rule

The goal is not a complete product. The goal is a sellable proof of value.

## Durable output

If working in a repo, create or update:

```text
docs/profit/build-spec.md
```

From az9713/idea-to-capital, MIT.

More from az9713/idea-to-capital