agentleFS
VeeiyVeeiy/vantage-os/skills/discovery-sprint/SKILL.md

discovery-sprint

Skill0 starsChanged 5 months agoMITView on GitHub

Structured 2-3 week sprint to pick or validate a new earnings stream. Use when the operator says "discovery sprint", "what should I launch", "pick a stream", "validate before I build", or wants a disciplined sequence before committing capital. Currently scoped to the hair-product venture validation but reusable for any future stream.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Luis85/agentic-workflow★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No supplier under 1000 MOQ at viable margin

    line 63
  2. Very specific:

    After day 14: written decision in decisions.md

    line 71
  3. Distinctive:

    When the operator invokes:

    line 75
  4. Distinctive:

    Check if a sprint is currently active.

    line 77
  5. Distinctive:

    If no active sprint, ask which venture this is for.

    line 78
  6. Very specific:

    Update ~/Vault/Vantage-OS/hair-product-state.md (or appropriate venture state file) with progress.

    line 80
  7. Distinctive:

    No product before validation: If the operator asks to brainstorm packaging on day 2, redirect to client interviews.

    line 84
  8. Distinctive:

    No marketing planning before product is locked: If the operator asks about Instagram strategy on day 5, redirect.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Discovery Sprint

A 2-3 week sequence to validate or kill a new earnings stream before any meaningful capital or time goes in.

For the operator right now, this is repurposed to validate the white-label consumer product venture before sourcing inventory.

Sprint structure (14 days)

Week 1: Diagnosis (days 1-7)

Goal: understand the problem and the customer, not the product.

  • Day 1-2: Customer problem mapping
  • Talk to a partner: what are the 3-5 most common hair complaints from her salon clients?
  • Talk to 5+ of a partner's clients: what products do they currently buy and why? What product would they pay $30+ for that doesn't exist?
  • Capture verbatim quotes. No paraphrasing.
  • Day 3-4: Market scan
  • Identify 3 problem areas competitors solve well (avoid these for v1)
  • Identify 1-2 problem areas where products are weak, expensive, or absent (target these)
  • Day 5-7: Concept narrowing
  • Narrow to 2 product concepts (NOT more)
  • Each concept gets: target problem, target customer, rough $/unit cost, estimated retail, channel
  • Decide: does this need to be a salon-only product, a retail product, or both?

Week 2: Supplier and economics (days 8-14)

Goal: prove the unit economics work before going further.

  • Day 8-10: White-label supplier shortlist
  • Find 5+ white-label cosmetics manufacturers (US-based preferred for compliance speed)
  • Get MOQ and per-unit cost for each
  • Get sample lead times and minimum customization options (label, fragrance, formula tweaks)
  • Day 11-12: Unit economics
  • Build a simple model: cost per unit, packaging, fulfillment, salon vs DTC margin, breakeven units, time to recoup MOQ
  • Compare against the hair-product-validator agent's model
  • Day 13-14: Go/no-go
  • Ship the validator's go/no-go report
  • Force the decision: order samples (go), wait 30 days for more signal (delay), or kill

Week 3 (only if go): Pre-production (days 15-21)

  • Order samples from top-2 suppliers
  • Begin brand work (hand to hair-product-brand agent)
  • Begin compliance prep (FDA cosmetics labeling, trademark search via hair-product-brand and external legal)

Go criteria (set before starting)

A "go" requires ALL of:

  • ≥3 client interviews surfaced the same unmet need
  • ≥1 supplier with MOQ ≤500 units at landed cost producing ≥50% margin at salon retail
  • the partner is in (already confirmed) AND willing to dedicate checkout space and ~30 min/week to product conversations
  • Estimated breakeven ≤4 months from launch

Kill criteria (set before starting)

Any one of:

  • the partner backs out
  • No supplier under 1000 MOQ at viable margin
  • Client interviews show no consistent unmet need (everyone happy with current products)
  • Required capital for v1 > $3000

Output cadence

  • End of week 1: short report + recommendations
  • End of week 2: full go/no-go with model
  • After day 14: written decision in decisions.md

How to use this skill

When the operator invokes:

  1. Check if a sprint is currently active. If yes, give status: which day, what's been done, what's next.
  2. If no active sprint, ask which venture this is for. Default: hair product.
  3. Walk the operator through TODAY's tasks for the sprint.
  4. Update ~/Vault/Vantage-OS/hair-product-state.md (or appropriate venture state file) with progress.

Anti-patterns to block

  • No product before validation. If the operator asks to brainstorm packaging on day 2, redirect to client interviews.
  • No marketing planning before product is locked. If the operator asks about Instagram strategy on day 5, redirect.
  • No website before supplier is locked. Day 15+ only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.