[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EC8720P823ZSPVY8VDA408":3,"skill-same:01M7EC8720P823ZSPVY8VDA408":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7EC8720P823ZSPVY8VDA408","product-lens",null,"Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go\u002Fno-go recommendation, a founder review scoring product-market-fit signals, a user journey audit measuring time-to-value, and ICE feature prioritization. Use when pressure-testing product direction, choosing between features, sanity-checking a launch, or converting a vague idea into a product brief.","syedmehedihussain\u002Fcherry","syedmehedihussain","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183754033?v=4","01M7EC34EA312J2XV37SD5C840","Syed Mehedi Hussain","01M7EC34EZR59ARY7C75C41EKJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fidea\u002Fskills\u002Fproduct-lens\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fidea\u002Fskills\u002Fproduct-lens\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: product-lens\ndescription: Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go\u002Fno-go recommendation, a founder review scoring product-market-fit signals, a user journey audit measuring time-to-value, and ICE feature prioritization. Use when pressure-testing product direction, choosing between features, sanity-checking a launch, or converting a vague idea into a product brief.\nmetadata:\n  origin: ECC\n---\n\n# Product Lens — Think Before You Build\n\nThis lane owns product diagnosis, not implementation-ready specification writing.\n\nIf the user needs a durable PRD-to-SRS or capability-contract artifact, hand off to `product-capability`.\n\n## When to Use\n\n- Before starting any feature — validate the \"why\"\n- Weekly product review — are we building the right thing?\n- When stuck choosing between features\n- Before a launch — sanity check the user journey\n- When converting a vague idea into a product brief before engineering planning starts\n\n## How It Works\n\n### Mode 1: Product Diagnostic\n\nLike YC office hours but automated. Asks the hard questions:\n\n```\n1. Who is this for? (specific person, not \"developers\")\n2. What's the pain? (quantify: how often, how bad, what do they do today?)\n3. Why now? (what changed that makes this possible\u002Fnecessary?)\n4. What's the 10-star version? (if money\u002Ftime were unlimited)\n5. What's the MVP? (smallest thing that proves the thesis)\n6. What's the anti-goal? (what are you explicitly NOT building?)\n7. How do you know it's working? (metric, not vibes)\n```\n\nOutput: a `PRODUCT-BRIEF.md` with answers, risks, and a go\u002Fno-go recommendation.\n\nIf the result is \"yes, build this,\" the next lane is `product-capability`, not more founder-theater.\n\n### Mode 2: Founder Review\n\nReviews your current project through a founder lens:\n\n```\n1. Read README, CLAUDE.md, package.json, recent commits\n2. Infer: what is this trying to be?\n3. Score: product-market fit signals (0-10)\n   - Usage growth trajectory\n   - Retention indicators (repeat contributors, return users)\n   - Revenue signals (pricing page, billing code, Stripe integration)\n   - Competitive moat (what's hard to copy?)\n4. Identify: the one thing that would 10x this\n5. Flag: things you're building that don't matter\n```\n\n### Mode 3: User Journey Audit\n\nMaps the actual user experience:\n\n```\n1. Clone\u002Finstall the product as a new user\n2. Document every friction point (confusing steps, errors, missing docs)\n3. Time each step\n4. Compare to competitor onboarding\n5. Score: time-to-value (how long until the user gets their first win?)\n6. Recommend: top 3 fixes for onboarding\n```\n\n### Mode 4: Feature Prioritization\n\nWhen you have 10 ideas and need to pick 2:\n\n```\n1. List all candidate features\n2. Score each on: impact (1-5) × confidence (1-5) ÷ effort (1-5)\n3. Rank by ICE score\n4. Apply constraints: runway, team size, dependencies\n5. Output: prioritized roadmap with rationale\n```\n\n## Output\n\nAll modes output actionable docs, not essays. Every recommendation has a specific next step.\n\n## Integration\n\nPair with:\n- `\u002Fbrowser-qa` to verify the user journey audit findings\n- `\u002Fdesign-system audit` for visual polish assessment\n- `\u002Fcanary-watch` for post-launch monitoring\n- `product-capability` when the product brief needs to become an implementation-ready capability plan\n","# Product Lens — Think Before You Build\n\nThis lane owns product diagnosis, not implementation-ready specification writing.\n\nIf the user needs a durable PRD-to-SRS or capability-contract artifact, hand off to `product-capability`.\n\n## When to Use\n\n- Before starting any feature — validate the \"why\"\n- Weekly product review — are we building the right thing?\n- When stuck choosing between features\n- Before a launch — sanity check the user journey\n- When converting a vague idea into a product brief before engineering planning starts\n\n## How It Works\n\n### Mode 1: Product Diagnostic\n\nLike YC office hours but automated. Asks the hard questions:\n\n```\n1. Who is this for? (specific person, not \"developers\")\n2. What's the pain? (quantify: how often, how bad, what do they do today?)\n3. Why now? (what changed that makes this possible\u002Fnecessary?)\n4. What's the 10-star version? (if money\u002Ftime were unlimited)\n5. What's the MVP? (smallest thing that proves the thesis)\n6. What's the anti-goal? (what are you explicitly NOT building?)\n7. How do you know it's working? (metric, not vibes)\n```\n\nOutput: a `PRODUCT-BRIEF.md` with answers, risks, and a go\u002Fno-go recommendation.\n\nIf the result is \"yes, build this,\" the next lane is `product-capability`, not more founder-theater.\n\n### Mode 2: Founder Review\n\nReviews your current project through a founder lens:\n\n```\n1. Read README, CLAUDE.md, package.json, recent commits\n2. Infer: what is this trying to be?\n3. Score: product-market fit signals (0-10)\n   - Usage growth trajectory\n   - Retention indicators (repeat contributors, return users)\n   - Revenue signals (pricing page, billing code, Stripe integration)\n   - Competitive moat (what's hard to copy?)\n4. Identify: the one thing that would 10x this\n5. Flag: things you're building that don't matter\n```\n\n### Mode 3: User Journey Audit\n\nMaps the actual user experience:\n\n```\n1. Clone\u002Finstall the product as a new user\n2. Document every friction point (confusing steps, errors, missing docs)\n3. Time each step\n4. Compare to competitor onboarding\n5. Score: time-to-value (how long until the user gets their first win?)\n6. Recommend: top 3 fixes for onboarding\n```\n\n### Mode 4: Feature Prioritization\n\nWhen you have 10 ideas and need to pick 2:\n\n```\n1. List all candidate features\n2. Score each on: impact (1-5) × confidence (1-5) ÷ effort (1-5)\n3. Rank by ICE score\n4. Apply constraints: runway, team size, dependencies\n5. Output: prioritized roadmap with rationale\n```\n\n## Output\n\nAll modes output actionable docs, not essays. Every recommendation has a specific next step.\n\n## Integration\n\nPair with:\n- `\u002Fbrowser-qa` to verify the user journey audit findings\n- `\u002Fdesign-system audit` for visual polish assessment\n- `\u002Fcanary-watch` for post-launch monitoring\n- `product-capability` when the product brief needs to become an implementation-ready capability plan\n",{"name":5,"metadata":25,"description":7},{"origin":26},"ECC","main","adb38ff1e06b1bb57c84131717dd3d9c01292a8b","packages\u002Fdaemon\u002Fstages\u002Fidea\u002Fskills\u002Fproduct-lens",0,"https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry","https:\u002F\u002Fsyedmehedihussain.github.io\u002Fcherry\u002F","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain","https:\u002F\u002Fsyedmehedihussain.codes\u002F","What should I say?","2026-11-10 02:42:31",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add syedmehedihussain\u002Fcherry --skill product-lens",{"tool":43,"command":44},"bunx","bunx skills add syedmehedihussain\u002Fcherry --skill product-lens",{"tool":46,"command":47},"pnpm","pnpm dlx skills add syedmehedihussain\u002Fcherry --skill product-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fidea\u002Fskills\u002Fproduct-lens\u002FSKILL.md",true,[51],{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE","许可证",1071,[56,64,72,80,88,96],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":20},"01M7ECBMEN6N02N2NGHMYTJTY1","verification-loop","Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fverification-loop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":20},"01M7ECBFBZ3GJEWJJHKRPCYX8J","e2e-testing","Playwright E2E testing patterns, Page Object Model, configuration, CI\u002FCD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fe2e-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fe2e-testing\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":20},"01M7ECB8WD04GN1SF0J7XM0252","browser-qa","Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP \u002F DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fbrowser-qa\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fbrowser-qa\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M7ECB2QHYKHYT9EJV089FVT4","ai-regression-testing","Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fai-regression-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fai-regression-testing\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":20},"01M7ECAXS1W69TNH9MV1J1WHM2","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fstory-lifecycle\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fstory-lifecycle\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":20},"01M7ECAQVHTTS6M1T62XYAP9NP","intent-driven-development","Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security\u002Fdata\u002Fmigration\u002Fintegration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fintent-driven-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fintent-driven-development\u002FSKILL.md",[],[]]