008993368-yaz

Agent-agnostic skill that recommends what feature a product should build next by combining codebase analysis, product context, competitor gaps, market signals, growth scoring, and implementation feasibility. Use when the user asks what to build next, wants growth opportunities, competitor gap analysis, a growth roadmap, market scouting, feature prioritization, or turning an opportunity into a PRD or GitHub issues. Works in any coding agent.

Use when the user asks what could break / go wrong / fail in a SPECIFIC scenario (e.g. "what if this webhook fires twice", "a user uploads a 2GB file"); OR gives a bounded surface (a diff/PR, one file, an endpoint, or a feature description) and wants the risky scenarios surfaced FOR them ("what should I worry about before shipping this change?"); asks to pressure-test, stress-test, or red-team a path; or wants a pre-launch / pre-ship / pre-deploy check. Works at design time and on existing code. Do NOT use for generic full-codebase reviews, "review my whole repo", or "find bugs everywhere" — that needs a bounded surface (a diff, file, endpoint, or feature), not the whole repo.

Build the Opention Notion clone using loop engineering. Read STATE and ROADMAP first; verify before marking milestones done.