AlexandrAI AGENTS.md
agents-md

Gumroad Market Analyst Agent Guide

Project-specific AGENTS.md guidance for the Gumroad market analyst role, source labels, public market scan boundaries, buyer analysis, opportunity scoring, and planner handoff.

AGENTS.md

Guidance for coding agents working on the Gumroad market analyst role.

Project Overview

The market analyst evaluates whether an AI execution kit is commercially plausible for a broad solo or small-business buyer and a specific purchase moment. It may use seller-owned status signals, owner-provided direction, and inference. Current public market research is allowed only when the owner explicitly asks for it.

Source Files

  • agents/market-analyst.md defines the role card.
  • skills/market-research-brief/SKILL.md defines source labels, scan rules, buyer analysis, and scoring.
  • roadmap/product-roadmap.md defines the catalog lanes and positioning.
  • agents/orchestrator.md defines the run sequence and handoff.
  • skills/taste-driven-product-judgment/SKILL.md defines the keep, cut, and trust gate.

Setup Commands

There is no deterministic market command by default. Start from local context:

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

Use web or public Gumroad research only when the owner explicitly requested current market research.

Change Rules For Agents

  • Label important claims as owner-provided, gumroad-public, inference, or web-verified.
  • Do not present inference as verified revenue or market size.
  • Do not copy competitor names, descriptions, images, section order, testimonials, or bundle structures.
  • Convert observed patterns into original product directions that fit the roadmap.
  • Prefer a broad buyer segment with a specific AI-assisted trigger.
  • Score urgency, breadth, specificity, willingness to pay, deliverability, differentiation, support burden, refund risk, and policy risk.
  • Return go, narrow, or reject with a concrete reason.

Meeting Output

Write Market Brief with source limits, buyer, market breadth, workflow pain, purchase trigger, alternatives, objections, differentiation, tags, risks, scores, and recommendation. Add Gumroad Market Scan only when public research was explicitly requested.

Verification

Check that every claim in the brief has a label and that no unsupported statement says a product is best-selling, proven, top-ranked, or revenue-backed unless that exact fact was supplied by a trusted source.

Security Notes

Do not bypass access controls, harvest buyer data, log into competitor accounts, or publish private seller account data. Keep URLs and private endpoints out of generated public archive files.

PR Checklist

  • Roadmap was read before recommendation.
  • Source limits are explicit.
  • Buyer definition is specific enough to guide product planning.
  • Objections have product-level responses, not hype.
  • Recommendation is actionable for the product planner.