AlexandrAI AGENTS.md
agents-md

Gumroad CEO Role Agent Guide

Project-specific AGENTS.md guidance for the Gumroad CEO role, narrowing one launchable AI execution kit, scoring candidates, rejecting distractions, and handing constraints to market analysis.

AGENTS.md

Guidance for coding agents working on the Gumroad CEO role.

Project Overview

The CEO role keeps a product run focused. It chooses one launchable Gumroad AI execution kit from owner direction, roadmap, and seller-owned status signals. It narrows broad ideas into one buyer, one AI-assisted workflow, one practical promise, and one buyer-ready artifact pack.

Source Files

  • agents/ceo.md defines the role.
  • roadmap/product-roadmap.md defines current lanes and next recommended products.
  • skills/taste-driven-product-judgment/SKILL.md defines the keep, cut, and trust gate.
  • agents/market-analyst.md receives the selected buyer, workflow, trigger, and policy constraints.
  • products//meeting.md stores CEO Decision and Rejected Alternatives.

Setup Commands

The CEO has no standalone script. Use seller-owned status and roadmap context before selection:

bashpython3 scripts/gumroad_status.py snapshot --output-dir research

Change Rules For Agents

  • Prefer the next recommended roadmap product unless owner direction or current evidence justifies a change.
  • Keep the buyer broad enough to matter and the purchase moment specific enough to understand quickly.
  • Default premium AI execution kits to USD 29 and normally no lower than USD 20 unless owner direction says otherwise.
  • Require enough substance: substantial guide, useful artifacts, walkthroughs when needed, and at least one reusable tool-like asset when the workflow benefits.
  • Reject guaranteed outcome claims, regulated advice, competitor copying, private data dependence, scraping, SaaS scope, ongoing custom work, and vague productivity bundles.
  • Score buyer urgency, market breadth, workflow specificity, artifact fit, differentiation, policy risk, and finishability.
  • Return go, narrow, or reject with roadmap fit: follow, adjacent, update, or reject.

Meeting Output

Write CEO Decision with chosen product, target buyer, painful workflow, purchase promise, default price, decision, scores, roadmap fit, and reasoning. Add Rejected Alternatives when useful.

Verification

The market analyst should be able to continue without guessing. If the CEO memo does not state buyer, workflow, purchase trigger, and claims to avoid, revise it before planning.

Security Notes

Do not use private customer records, competitor copying, private seller account details, or invented results as selection proof. Treat seller-owned status snapshots as internal planning evidence only.

PR Checklist

  • One product was selected.
  • Distractions were cut.
  • Policy and refund risks are known.
  • Roadmap fit is explicit.
  • Handoff gives market analyst enough constraints.