[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734RQBZ4FJ92CF846HW6WB0":3,"skill-same:01M734RQBZ4FJ92CF846HW6WB0":63},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M734RQBZ4FJ92CF846HW6WB0","productize-market-opportunity",null,"Identify, compare, and choose market opportunities for a venture, product, technology, or innovation. Use when a founder, entrepreneur, product team, or innovator is choosing which market to enter, picking a primary customer segment, evaluating whether a technology has better use cases, deciding whether to pivot, comparing growth options, framing a venture for investors, or asking variants of \"which market should I target\", \"is this the right opportunity\", \"where should I focus\", \"should I pivot\", or \"what else could this be used for\". Produces filled-in opportunity canvases for the Market Opportunity Set, Attractiveness Map, Focus Portfolio Map, and Focus Strategy. Default to this skill when the question is where to play rather than how to play.","itseffi\u002Fproductize","itseffi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15998472?v=4","01M734C5RJ7CKRTPB3FX84VZV7","Effi","01M734C5S6B7FW62ZNWYBZ9GG7",3,"MIT","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-market-opportunity\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-market-opportunity\ndescription: >-\n  Identify, compare, and choose market opportunities for a venture, product, technology, or\n  innovation. Use when a founder, entrepreneur, product team, or innovator is choosing which\n  market to enter, picking a primary customer segment, evaluating whether a technology has\n  better use cases, deciding whether to pivot, comparing growth options, framing a venture for\n  investors, or asking variants of \"which market should I target\", \"is this the right\n  opportunity\", \"where should I focus\", \"should I pivot\", or \"what else could this be used\n  for\". Produces filled-in opportunity canvases for the Market Opportunity Set, Attractiveness\n  Map, Focus Portfolio Map, and Focus Strategy. Default to this skill when the question is\n  where to play rather than how to play.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Market Opportunity\n\n## Productize Preamble\n\nBefore producing the artifact, implementation step, or code change, classify the work:\n\n- **User\u002Fpersona**: founder, product leader, AI PM, AI builder, stakeholder, or mixed\u002Funknown.\n- **Product stage**: idea, validation, PMF search, growth, scale, pivot, or unknown.\n- **Artifact mode**: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.\n- **Artifact format**: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.\n- **Evidence standard**: what is known, assumed, missing, and risky.\n- **Decision mode**: recommend, ask for a blocking input, or proceed with explicit assumptions.\n\nOperating rules:\n\n1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.\n2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.\n3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.\n4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.\n5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.\n6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.\n7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.\n8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.\n9. If you must ask a blocking question, use this compact format: `AskUserQuestion: \u003Cone question> Why it matters: \u003Cdecision it changes>`.\n10. Record completion status for durable work as `completed`, `blocked`, `deferred`, or `needs-review` when runtime hooks are available.\n\nArtifact format policy:\n\n- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.\n- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams\u002Ftables\u002Fcomparisons\u002Fscreenshots, the artifact is meant to be shared, or interaction\u002Fexport controls would help the user stay in the loop.\n- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.\n- HTML artifacts must be local-first and portable: one file, embedded CSS\u002FJS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.\n- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy\u002Fexport buttons when they improve review speed. Avoid decorative complexity that hides the decision.\n- For implementation work with ambiguities, use `$implementation-notes` when the user asks for a running notes file, especially `implementation-notes.html` or `implementation-notes.md`.\n\nRuntime hooks, if available:\n\n- Use `productize-workflow start \"\u003Cuser request>\"` at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.\n- Use `productize-workflow complete --id \u003Cid> --status completed|blocked|deferred|needs-review --artifact-type \u003Ctype> --summary \u003Csummary>` before ending durable product work; it records the artifact, saves context, and logs completion status.\n- Use `productize-update-check --strict` at the start of maintenance, setup, release, or generated-output work.\n- Use `productize-config` to read or write user\u002Fteam preferences such as persona, artifact mode, evidence threshold, or update-check policy.\n- Use `productize-session-log` to record important workflow decisions.\n- Use `productize-artifact-log` when a durable artifact is produced.\n- Use `productize-context-restore` before restarting long-running product work from scratch.\n- Use `productize-context-save` after producing a durable strategy, research, spec, or stakeholder artifact.\n- Use `productize-registry-search` or `productize-skill-router` when routing is ambiguous.\n- Use `productize-completion-status` to log whether the workflow completed, blocked, deferred, or needs review.\n\nTelemetry standard:\n\n- Keep telemetry local by default in `.productize\u002F` or `PRODUCTIZE_STATE_DIR`.\n- Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.\n\nCurrent skill metadata:\n\n- **Skill**: `market-opportunity`\n- **Lifecycle**: Strategize\n- **Category**: Venture \u002F 0-1\n- **Primary artifact**: Market Opportunity venture brief with target segment, wedge, assumptions, and validation path\n\nCreate the complete four-part market opportunity artifact set for choosing where a\nventure, technology, product, or innovation should play.\n\nUse neutral terms such as `canvas`, `opportunity artifact`, `strategy surface`, or the\nartifact names below.\n\n## Argument Hint\n\n`\u003Cventure, technology, product, opportunity set, or blank-template request>`\n\n## Usage\n\n```text\n\u002Fmarket-opportunity $ARGUMENTS\n```\n\n## Required Artifacts\n\nFor any complete request, create all four artifacts unless the user explicitly asks for\nonly one:\n\n1. **Opportunity Overview Canvas**: the three-part overview with opportunity set,\n   attractiveness map, and focus portfolio map.\n2. **Opportunity Set Builder**: abilities -> applications -> customers -> market\n   opportunities.\n3. **Attractiveness Evaluator**: potential and challenge ratings for each market\n   opportunity.\n4. **Focus Portfolio Planner**: primary market opportunity, backup options, growth\n   options, and pursue\u002Fkeep\u002Fstore decisions.\n\nLoad `references\u002Fcanonical-canvases.md` before creating blank templates, filled\ntemplates, printable layouts, or tables. It defines the exact fields and structure.\n\nLoad `references\u002Frating-and-decision-rules.md` before rating opportunities,\nclassifying map zones, or recommending primary, backup, and growth options.\n\nLoad `references\u002Foutput-formats.md` when the user asks for Markdown, HTML, PDF,\nslides, visual canvases, or printable templates.\n\n## Workflow\n\n### 1. Establish the Input Mode\n\nDetermine whether the user wants:\n\n- **Blank canvas set**: empty structured artifacts for a team to fill in.\n- **Filled canvas set**: completed artifacts from a venture\u002Fproduct\u002Ftechnology idea.\n- **Opportunity review**: critique or improve an existing opportunity set.\n- **Strategy decision**: choose the primary opportunity and portfolio options.\n- **Printable artifact**: create visual HTML\u002FPDF\u002Fslide-ready canvases.\n\nIf context is missing, ask only for the smallest useful missing piece:\n\n- The venture, product, technology, or core ability.\n- Candidate applications.\n- Candidate customer groups.\n- Existing evidence for demand, market size, economics, implementation, timing, and risks.\n\n### 2. Generate the Market Opportunity Set\n\nIdentify the venture's core abilities or technological elements first. Describe them\nindependent of the envisioned product.\n\nThen generate combinations:\n\n```text\nmarket opportunity = application + customer segment\n```\n\nSegment customers precisely. Avoid broad labels like \"enterprises\" or \"consumers\"\nunless the user has no better information.\n\n### 3. Evaluate Attractiveness\n\nFor each market opportunity, rate:\n\n- **Potential**\n  - Compelling reason to buy.\n  - Market volume.\n  - Economic viability.\n- **Challenge**\n  - Implementation obstacles.\n  - Time to revenue.\n  - External risks.\n\nUse the four-level rating scale:\n\n```text\nLow \u002F Mid \u002F High \u002F Super High\n```\n\nThen place each opportunity on the attractiveness map:\n\n- **Gold Mine**\n- **Quick Win**\n- **Moon Shot**\n- **Questionable**\n\n### 4. Design the Focus Portfolio\n\nChoose one **Primary Market Opportunity** based on attractiveness and strategic fit.\n\nFor other attractive opportunities, assess relatedness to the primary opportunity:\n\n- **Product relatedness**: shared technological competences, required resources,\n  and necessary networks.\n- **Market relatedness**: shared customer values and benefits, sales channels, and\n  word-of-mouth paths.\n\nClassify each option:\n\n- **Growth Option**: attractive and useful for creating additional value.\n- **Backup Option**: attractive and does not share major risks with the primary path.\n- **Storage**: documented but not worth active preservation now.\n\nMake one of three action decisions for each option:\n\n- Pursue now.\n- Keep open.\n- Place in storage.\n\nThe final strategy must keep at least one credible backup option and one credible\ngrowth option open unless the available evidence makes that impossible. If impossible,\nsay what evidence or opportunity generation is missing.\n\n### 5. Tie Strategy to Execution\n\nFor completed strategy outputs, include implications for:\n\n- Product and technology modularity.\n- IP and defensibility.\n- Hiring and capability development.\n- Stakeholder and investor alignment.\n- Brand and market communication.\n- Experiments, assumptions, and learning loops.\n- Business Model Canvas, Value Proposition Canvas, and Lean Startup integration when\n  the user asks for execution planning.\n\n## Output Rules\n\n- Preserve the canonical field names and rating scales from the reference files.\n- Do not collapse the framework into SWOT, generic market sizing, or a feature\n  prioritization matrix.\n- Be explicit about assumptions and evidence gaps.\n- Use tables for editable outputs.\n- For visual outputs, use the same four-artifact structure and neutral artifact titles.\n- Do not copy long passages from source PDFs. Use the exact operational labels and\n  schemas, with original wording for explanations and recommendations.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Market Opportunity\n\n## Productize Preamble\n\nBefore producing the artifact, implementation step, or code change, classify the work:\n\n- **User\u002Fpersona**: founder, product leader, AI PM, AI builder, stakeholder, or mixed\u002Funknown.\n- **Product stage**: idea, validation, PMF search, growth, scale, pivot, or unknown.\n- **Artifact mode**: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.\n- **Artifact format**: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.\n- **Evidence standard**: what is known, assumed, missing, and risky.\n- **Decision mode**: recommend, ask for a blocking input, or proceed with explicit assumptions.\n\nOperating rules:\n\n1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.\n2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.\n3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.\n4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.\n5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.\n6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.\n7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.\n8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.\n9. If you must ask a blocking question, use this compact format: `AskUserQuestion: \u003Cone question> Why it matters: \u003Cdecision it changes>`.\n10. Record completion status for durable work as `completed`, `blocked`, `deferred`, or `needs-review` when runtime hooks are available.\n\nArtifact format policy:\n\n- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.\n- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams\u002Ftables\u002Fcomparisons\u002Fscreenshots, the artifact is meant to be shared, or interaction\u002Fexport controls would help the user stay in the loop.\n- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.\n- HTML artifacts must be local-first and portable: one file, embedded CSS\u002FJS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.\n- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy\u002Fexport buttons when they improve review speed. Avoid decorative complexity that hides the decision.\n- For implementation work with ambiguities, use `$implementation-notes` when the user asks for a running notes file, especially `implementation-notes.html` or `implementation-notes.md`.\n\nRuntime hooks, if available:\n\n- Use `productize-workflow start \"\u003Cuser request>\"` at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.\n- Use `productize-workflow complete --id \u003Cid> --status completed|blocked|deferred|needs-review --artifact-type \u003Ctype> --summary \u003Csummary>` before ending durable product work; it records the artifact, saves context, and logs completion status.\n- Use `productize-update-check --strict` at the start of maintenance, setup, release, or generated-output work.\n- Use `productize-config` to read or write user\u002Fteam preferences such as persona, artifact mode, evidence threshold, or update-check policy.\n- Use `productize-session-log` to record important workflow decisions.\n- Use `productize-artifact-log` when a durable artifact is produced.\n- Use `productize-context-restore` before restarting long-running product work from scratch.\n- Use `productize-context-save` after producing a durable strategy, research, spec, or stakeholder artifact.\n- Use `productize-registry-search` or `productize-skill-router` when routing is ambiguous.\n- Use `productize-completion-status` to log whether the workflow completed, blocked, deferred, or needs review.\n\nTelemetry standard:\n\n- Keep telemetry local by default in `.productize\u002F` or `PRODUCTIZE_STATE_DIR`.\n- Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.\n\nCurrent skill metadata:\n\n- **Skill**: `market-opportunity`\n- **Lifecycle**: Strategize\n- **Category**: Venture \u002F 0-1\n- **Primary artifact**: Market Opportunity venture brief with target segment, wedge, assumptions, and validation path\n\nCreate the complete four-part market opportunity artifact set for choosing where a\nventure, technology, product, or innovation should play.\n\nUse neutral terms such as `canvas`, `opportunity artifact`, `strategy surface`, or the\nartifact names below.\n\n## Argument Hint\n\n`\u003Cventure, technology, product, opportunity set, or blank-template request>`\n\n## Usage\n\n```text\n\u002Fmarket-opportunity $ARGUMENTS\n```\n\n## Required Artifacts\n\nFor any complete request, create all four artifacts unless the user explicitly asks for\nonly one:\n\n1. **Opportunity Overview Canvas**: the three-part overview with opportunity set,\n   attractiveness map, and focus portfolio map.\n2. **Opportunity Set Builder**: abilities -> applications -> customers -> market\n   opportunities.\n3. **Attractiveness Evaluator**: potential and challenge ratings for each market\n   opportunity.\n4. **Focus Portfolio Planner**: primary market opportunity, backup options, growth\n   options, and pursue\u002Fkeep\u002Fstore decisions.\n\nLoad `references\u002Fcanonical-canvases.md` before creating blank templates, filled\ntemplates, printable layouts, or tables. It defines the exact fields and structure.\n\nLoad `references\u002Frating-and-decision-rules.md` before rating opportunities,\nclassifying map zones, or recommending primary, backup, and growth options.\n\nLoad `references\u002Foutput-formats.md` when the user asks for Markdown, HTML, PDF,\nslides, visual canvases, or printable templates.\n\n## Workflow\n\n### 1. Establish the Input Mode\n\nDetermine whether the user wants:\n\n- **Blank canvas set**: empty structured artifacts for a team to fill in.\n- **Filled canvas set**: completed artifacts from a venture\u002Fproduct\u002Ftechnology idea.\n- **Opportunity review**: critique or improve an existing opportunity set.\n- **Strategy decision**: choose the primary opportunity and portfolio options.\n- **Printable artifact**: create visual HTML\u002FPDF\u002Fslide-ready canvases.\n\nIf context is missing, ask only for the smallest useful missing piece:\n\n- The venture, product, technology, or core ability.\n- Candidate applications.\n- Candidate customer groups.\n- Existing evidence for demand, market size, economics, implementation, timing, and risks.\n\n### 2. Generate the Market Opportunity Set\n\nIdentify the venture's core abilities or technological elements first. Describe them\nindependent of the envisioned product.\n\nThen generate combinations:\n\n```text\nmarket opportunity = application + customer segment\n```\n\nSegment customers precisely. Avoid broad labels like \"enterprises\" or \"consumers\"\nunless the user has no better information.\n\n### 3. Evaluate Attractiveness\n\nFor each market opportunity, rate:\n\n- **Potential**\n  - Compelling reason to buy.\n  - Market volume.\n  - Economic viability.\n- **Challenge**\n  - Implementation obstacles.\n  - Time to revenue.\n  - External risks.\n\nUse the four-level rating scale:\n\n```text\nLow \u002F Mid \u002F High \u002F Super High\n```\n\nThen place each opportunity on the attractiveness map:\n\n- **Gold Mine**\n- **Quick Win**\n- **Moon Shot**\n- **Questionable**\n\n### 4. Design the Focus Portfolio\n\nChoose one **Primary Market Opportunity** based on attractiveness and strategic fit.\n\nFor other attractive opportunities, assess relatedness to the primary opportunity:\n\n- **Product relatedness**: shared technological competences, required resources,\n  and necessary networks.\n- **Market relatedness**: shared customer values and benefits, sales channels, and\n  word-of-mouth paths.\n\nClassify each option:\n\n- **Growth Option**: attractive and useful for creating additional value.\n- **Backup Option**: attractive and does not share major risks with the primary path.\n- **Storage**: documented but not worth active preservation now.\n\nMake one of three action decisions for each option:\n\n- Pursue now.\n- Keep open.\n- Place in storage.\n\nThe final strategy must keep at least one credible backup option and one credible\ngrowth option open unless the available evidence makes that impossible. If impossible,\nsay what evidence or opportunity generation is missing.\n\n### 5. Tie Strategy to Execution\n\nFor completed strategy outputs, include implications for:\n\n- Product and technology modularity.\n- IP and defensibility.\n- Hiring and capability development.\n- Stakeholder and investor alignment.\n- Brand and market communication.\n- Experiments, assumptions, and learning loops.\n- Business Model Canvas, Value Proposition Canvas, and Lean Startup integration when\n  the user asks for execution planning.\n\n## Output Rules\n\n- Preserve the canonical field names and rating scales from the reference files.\n- Do not collapse the framework into SWOT, generic market sizing, or a feature\n  prioritization matrix.\n- Be explicit about assumptions and evidence gaps.\n- Use tables for editable outputs.\n- For visual outputs, use the same four-artifact structure and neutral artifact titles.\n- Do not copy long passages from source PDFs. Use the exact operational labels and\n  schemas, with original wording for explanations and recommendations.\n",{"name":5,"description":7},"main","f177680a573a242a81bd0a776f9681f620e6d74c","skills\u002Fproductize-market-opportunity",0,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize","https:\u002F\u002Fgithub.com\u002Fitseffi","2026-08-07 20:07:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add itseffi\u002Fproductize --skill productize-market-opportunity",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-market-opportunity",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-market-opportunity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-market-opportunity\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",335,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-market-opportunity\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcanonical-canvases.md",7510,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-market-opportunity\u002Freferences\u002Fcanonical-canvases.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Foutput-formats.md",3966,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-market-opportunity\u002Freferences\u002Foutput-formats.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Frating-and-decision-rules.md",6675,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-market-opportunity\u002Freferences\u002Frating-and-decision-rules.md",[64,71,78,85,92,99],{"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":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7357QB5M87V95F82E73V2TF","workflow-memory","Maintains workflow-scoped task memory for Productize runs using .productize\u002Ftasks\u002F\u003Cname>\u002Fmemory\u002F files. Use when a task prompt provides workflow memory paths and requires the agent to read, update, compact, and promote durable context across PRD task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-memory\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7357K97HSYEHAQTW5ZKM4CE","review-round","Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Freview-round\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7357F2NZE5NSYM2SJXEGBFZ","productize","Productize root skill for building, shipping, operating, and growing AI products inside a coding harness. Routes work across thesis framing, discovery, research, positioning, finance, decision making, requirements, design, metrics, AI-builder execution, code implementation, verification, stakeholder narratives, growth, launch, operation, and learning workflows. Use when the user wants to build a product from zero, improve an existing product, or needs product work that spans multiple lifecycle stages before code, launch, operation, or growth execution.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7357B48F8MK86EQF135FJQ6","productize-wwas","Why-What-Acceptance. Use when writing backlog items in Why-What-Acceptance format, breaking features into independent valuable work, or adding strategic context to delivery items.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-wwas\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M735783CDA9MQ0SPR9X6QZSE","productize-writing-plans","Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-writing-plans\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M735750V5Q6WRBX1ZFGNRMEB","productize-write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea into a structured document, scoping goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into phases.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-write-spec\u002FSKILL.md",[],[]]