empire-product

These agents are adapted from upstream open-source projects under the MIT

Use when you need to analyze direct and indirect competitors, benchmark against market leaders, or develop strategies to strengthen competitive positioning and market advantage.

Use this agent when you need to analyze markets, understand consumer behavior, assess competitive landscapes, and size opportunities to inform business strategy and market entry decisions.

Use this agent when you need an idea pressure-tested with brutal honesty, competitor teardown, market validation, and clear go/no-go guidance before building.

Diagnose requirements problems and guide discovery of real needs vs. stated wants. Use before any implementation to distinguish problem from solution, surface hidden constraints, and bound scope to a viable V1. Trigger phrases: "requirements analysis", "what should I build", "clarify requirements", "is this the right problem", "define scope", "what does the user need", "distill requirements", "/empire-product:distill". Findings stay local — never post to GitHub.

Diagnose why names don't work and guide creation of names that do — covers brand names, product names, skill names, character names, place names, and titles. Use when a name feels wrong but no one can say why, when a family of names feels disjointed, when a name is forgettable, or when systematic naming is needed. Trigger phrases: "name this", "this name doesn't feel right", "brand naming", "product naming", "names don't match", "forgettable name", "wrong associations", "mint a name", "/empire-product:mint". Findings stay local — never post to GitHub.

Generate a personal elevator pitch or a repository/project pitch. Use when user asks for "elevator pitch", "pitch this project", "introduce myself", "personal pitch", "how do I pitch myself", "pitch for this repo", "/empire-product:pitch", or wants a "tell me about yourself" answer. Also triggers on: "what's a good way to introduce this", "explain this repo in one line", "describe this project", "intro paragraph", "tagline", "one-liner", "GitHub repo description", "package.json description", "what does this do".

Diagnose thinking failures and audit whether reasoning serves inquiry or defense. Use when reasoning feels stuck or circular, a conclusion feels defended rather than discovered, confidence is high but evidence is thin, analysis grows more elaborate without becoming more accurate, or same approach keeps failing. Trigger phrases: "check my thinking", "am I reasoning well", "why am I stuck", "reasoning feels circular", "probe my logic", "/empire-product:probe". Two modes: self-monitoring (agent audits own process) and user coaching (diagnose user's thinking pattern with questions, not declarations).

Trigger when user says: "competitor analysis", "compare competitors", "/empire-product:recon", "competitor matrix", "competitor research", "feature gap", "scout competitors", "size up competition", "pricing comparison vs competitors", "positioning analysis", "competitive landscape". Maps competitor pricing, features, positioning, and gaps across a chosen dimension set. Produces side-by-side matrix with confidence-tagged data and positioning angle. Different from `/empire-research:compare`, which evaluates tools, libraries, vendors, or architectural choices — NOT competitors. Findings stay local — never posted externally.