AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

before-you-build

Pre-build product and feature risk review for founders, product managers, and AI-assisted builders. Use this skill when the user is about to build a landing page, MVP, SaaS product, internal tool, agent workflow, or major feature and needs to check demand, positioning, monetization, retention, trust, distribution, and adoption risk before implementation starts.

Original source
wshobson
License
MIT
Pinned revision
7e2fb559cf4b824b27f1fec49fe88f7511066d26

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read wshobson--before-you-build at revision 7e2fb559cf4b824b27f1fec49fe88f7511066d26, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 2

references/risk-checklist.md

Risk Checklist

Use these questions when the basic verdict is not obvious.

Demand

  • Who has the painful problem today?
  • What workaround are they using now?
  • What behavior shows urgency: payment, repeated manual work, switching tools, or asking for the same outcome more than once?

Positioning

  • Can the target user say what this is for without hearing the implementation details?
  • Is the promise tied to a concrete outcome rather than a broad category?
  • Does the idea have a clear alternative it must beat?

Monetization

  • Who controls the budget or time savings?
  • Is the value large enough to support the required build and maintenance cost?
  • Would the first useful version create enough value to justify payment, adoption, or internal sponsorship?

Retention

  • What makes the product useful after the first session?
  • Does it create a saved workflow, history, collaboration loop, or recurring decision?
  • Would users remember to come back without reminders?

Trust

  • What data, permissions, integrations, or behavior changes does this require?
  • What proof would make a cautious user comfortable trying it?
  • What failure would make the product feel unsafe or unserious?

Distribution

  • Where can the exact target user be reached repeatedly?
  • What existing channel, community, workflow, or integration can expose the product?
  • Is there a realistic path beyond one launch post?

Feature Adoption

  • What existing user behavior will this feature change?
  • Is the feature tied to an active user pain or just a product idea?
  • Can adoption be measured with one clear event?