[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GPRBESF5SBW9S1AXZNN2M":3,"skill-same:01M70GPRBESF5SBW9S1AXZNN2M":73},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70GPRBESF5SBW9S1AXZNN2M","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fproduct-lens\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"product","lens","product lens","signals","when","vague","feature prioritization","product-brief","sanity","direction","product brief","testing","time","scoring","journey","why","prioritization","brief","audit","review","2026-11-10 10:12:30",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":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fproduct-lens",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill product-lens",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill product-lens",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill product-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fproduct-lens\u002FSKILL.md",true,[],[74,82,90,97,104,111],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":89},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":89},"01M748721J3GKR2WS6K0QWFC35","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\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]