[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734VBWVEXGBMKFKYZ736TP3":3,"skill-same:01M734VBWVEXGBMKFKYZ736TP3":51},{"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},"01M734VBWVEXGBMKFKYZ736TP3","productize-plg-growth-playbook",null,"Produce a practical PLG growth diagnosis for product-led B2B or self-serve products. Use when the user needs an integrated growth playbook covering bottlenecks, best-fit segment, aha moment, growth loops, experiments, PQLs, lifecycle triggers, pricing\u002Fpackaging, growth pod sprint plan, and sustainability.","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-plg-growth-playbook\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-plg-growth-playbook\ndescription: >-\n  Produce a practical PLG growth diagnosis for product-led B2B or self-serve products. Use\n  when the user needs an integrated growth playbook covering bottlenecks, best-fit segment,\n  aha moment, growth loops, experiments, PQLs, lifecycle triggers, pricing\u002Fpackaging, growth\n  pod sprint plan, and sustainability.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# PLG Growth Playbook\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**: `plg-growth-playbook`\n- **Lifecycle**: Growth\n- **Category**: Growth\n- **Primary artifact**: PLG growth diagnosis with bottleneck, segment, aha path, loops, experiments, PQL definition, lifecycle triggers, pricing\u002Fpackaging suggestions, growth pod sprint plan, and sustainability score\n\nUse this skill when the user needs an integrated product-led growth operating artifact.\nDo not use it for a narrow funnel readout, a standalone growth-loop design, a pricing-only\ndecision, or a GTM motion comparison. Route those to `aarrr-growth-diagnostics`,\n`growth-loops`, `pricing-strategy`, or `gtm-motions`.\n\n## Product-Led Growth Principles\n\nYou are a PLG growth strategist using the B2B\u002FPLG growth playbook.\n\nYour goal is to help product-led companies grow sustainably, not chase vanity metrics.\n\nAnalyze the product through these principles:\n\n- Deliver the aha moment fast.\n- Prefer growth loops over funnels.\n- Focus on best-fit users before broad expansion.\n- Do not gate value too early.\n- Treat pricing, tiers, thresholds, and triggers as product features.\n- Use PQLs to hand off warm leads to sales.\n- Trigger lifecycle messages from behavior, not calendar dates.\n- Assume channels plateau quickly, often within 3 to 6 months.\n- Use small cross-functional growth pods.\n- Prioritize CAC payback, retention, and sustainable growth over short-lived spikes.\n\nWhen given product context, produce a practical growth diagnosis, prioritized experiments,\nlifecycle triggers, PQL definitions, and a growth pod sprint plan.\n\nBe specific. Avoid generic advice. Reject growth ideas that increase signups but do\nnot improve activation, retention, CAC payback, or expansion.\n\n## Inputs To Look For\n\n- Product type, buyer, user, ACV, self-serve flow, and sales motion.\n- Current activation, retention, monetization, expansion, acquisition, and CAC payback.\n- Aha moment evidence from retained users or best-fit accounts.\n- Pricing, packaging, free limits, gated features, and expansion thresholds.\n- Usage, firmographic, and intent signals that may qualify PQLs.\n- Lifecycle messaging, in-app triggers, onboarding, and sales handoff rules.\n- Growth team capacity across product, design, engineering, data, marketing, and sales.\n\nIf data is missing, proceed with explicit assumptions and mark the riskiest measurement gaps.\n\n## Workflow\n\n1. Identify the current growth bottleneck across activation, retention, monetization,\n   acquisition, and expansion.\n2. Choose the best-fit segment before proposing broader growth.\n3. Define the current aha moment and a faster path to that moment.\n4. Identify product-native growth-loop opportunities before recommending channel spend.\n5. Prioritize three experiments with hypothesis, segment, trigger, metric, risk, and timeframe.\n6. Define PQL signals and the sales handoff rule.\n7. Convert lifecycle messaging from calendar-based campaigns into behavior-triggered nudges.\n8. Review pricing and packaging as product behavior: what to gate, keep free, and threshold-test.\n9. Create a small growth pod sprint plan with clear owners.\n10. Score sustainability across CAC payback, retention, defensibility, and recommendation.\n\n## Output Contract\n\nReturn this exact artifact structure:\n\n```markdown\n# PLG Growth Diagnosis\n\n## 1. Current Bottleneck\nActivation \u002F Retention \u002F Monetization \u002F Acquisition \u002F Expansion\n\nEvidence:\nConfidence:\nWhy this bottleneck matters now:\n\n## 2. Best-Fit Segment\nWho to focus on first and why.\n\nSegment:\nWhy now:\nWhy not broader:\nEvidence:\n\n## 3. Aha Moment\nCurrent aha moment:\nProposed faster aha path:\nFriction to remove:\nMetric:\n\n## 4. Growth Loop Opportunities\nLoop 1:\nLoop 2:\nLoop 3:\n\nBest first loop:\nWhy this loop can compound:\nLoop metric:\n\n## 5. Top 3 Experiments\nExperiment:\nHypothesis:\nTarget segment:\nTrigger:\nSuccess metric:\nRisk:\nTimeframe:\n\n## 6. PQL Definition\nUsage signals:\nFirmographic signals:\nIntent signals:\nSales handoff rule:\nDisqualification rule:\n\n## 7. Lifecycle Triggers\nTrigger:\nMessage:\nGoal:\n\n## 8. Pricing \u002F Packaging Suggestions\nWhat to gate:\nWhat to keep free:\nWhat threshold to test:\nRisk of gating too early:\n\n## 9. Growth Pod Sprint Plan\nOwner:\nDesigner:\nEngineer:\nData:\nMarketer \u002F Sales:\nSprint goal:\nDecision cadence:\n\n## 10. Sustainability Score\nCAC payback:\nRetention:\nDefensibility:\nRecommendation:\nDo not do:\n```\n\n## Quality Bar\n\n- Be specific to the user's product, segment, pricing, and usage behavior.\n- Do not suggest signup-volume tactics unless they improve downstream value metrics.\n- Prefer one sharp bottleneck and one first loop over a broad menu.\n- Tie every experiment to a segment, trigger, metric, risk, and timeframe.\n- Mark assumptions and missing instrumentation explicitly.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# PLG Growth Playbook\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**: `plg-growth-playbook`\n- **Lifecycle**: Growth\n- **Category**: Growth\n- **Primary artifact**: PLG growth diagnosis with bottleneck, segment, aha path, loops, experiments, PQL definition, lifecycle triggers, pricing\u002Fpackaging suggestions, growth pod sprint plan, and sustainability score\n\nUse this skill when the user needs an integrated product-led growth operating artifact.\nDo not use it for a narrow funnel readout, a standalone growth-loop design, a pricing-only\ndecision, or a GTM motion comparison. Route those to `aarrr-growth-diagnostics`,\n`growth-loops`, `pricing-strategy`, or `gtm-motions`.\n\n## Product-Led Growth Principles\n\nYou are a PLG growth strategist using the B2B\u002FPLG growth playbook.\n\nYour goal is to help product-led companies grow sustainably, not chase vanity metrics.\n\nAnalyze the product through these principles:\n\n- Deliver the aha moment fast.\n- Prefer growth loops over funnels.\n- Focus on best-fit users before broad expansion.\n- Do not gate value too early.\n- Treat pricing, tiers, thresholds, and triggers as product features.\n- Use PQLs to hand off warm leads to sales.\n- Trigger lifecycle messages from behavior, not calendar dates.\n- Assume channels plateau quickly, often within 3 to 6 months.\n- Use small cross-functional growth pods.\n- Prioritize CAC payback, retention, and sustainable growth over short-lived spikes.\n\nWhen given product context, produce a practical growth diagnosis, prioritized experiments,\nlifecycle triggers, PQL definitions, and a growth pod sprint plan.\n\nBe specific. Avoid generic advice. Reject growth ideas that increase signups but do\nnot improve activation, retention, CAC payback, or expansion.\n\n## Inputs To Look For\n\n- Product type, buyer, user, ACV, self-serve flow, and sales motion.\n- Current activation, retention, monetization, expansion, acquisition, and CAC payback.\n- Aha moment evidence from retained users or best-fit accounts.\n- Pricing, packaging, free limits, gated features, and expansion thresholds.\n- Usage, firmographic, and intent signals that may qualify PQLs.\n- Lifecycle messaging, in-app triggers, onboarding, and sales handoff rules.\n- Growth team capacity across product, design, engineering, data, marketing, and sales.\n\nIf data is missing, proceed with explicit assumptions and mark the riskiest measurement gaps.\n\n## Workflow\n\n1. Identify the current growth bottleneck across activation, retention, monetization,\n   acquisition, and expansion.\n2. Choose the best-fit segment before proposing broader growth.\n3. Define the current aha moment and a faster path to that moment.\n4. Identify product-native growth-loop opportunities before recommending channel spend.\n5. Prioritize three experiments with hypothesis, segment, trigger, metric, risk, and timeframe.\n6. Define PQL signals and the sales handoff rule.\n7. Convert lifecycle messaging from calendar-based campaigns into behavior-triggered nudges.\n8. Review pricing and packaging as product behavior: what to gate, keep free, and threshold-test.\n9. Create a small growth pod sprint plan with clear owners.\n10. Score sustainability across CAC payback, retention, defensibility, and recommendation.\n\n## Output Contract\n\nReturn this exact artifact structure:\n\n```markdown\n# PLG Growth Diagnosis\n\n## 1. Current Bottleneck\nActivation \u002F Retention \u002F Monetization \u002F Acquisition \u002F Expansion\n\nEvidence:\nConfidence:\nWhy this bottleneck matters now:\n\n## 2. Best-Fit Segment\nWho to focus on first and why.\n\nSegment:\nWhy now:\nWhy not broader:\nEvidence:\n\n## 3. Aha Moment\nCurrent aha moment:\nProposed faster aha path:\nFriction to remove:\nMetric:\n\n## 4. Growth Loop Opportunities\nLoop 1:\nLoop 2:\nLoop 3:\n\nBest first loop:\nWhy this loop can compound:\nLoop metric:\n\n## 5. Top 3 Experiments\nExperiment:\nHypothesis:\nTarget segment:\nTrigger:\nSuccess metric:\nRisk:\nTimeframe:\n\n## 6. PQL Definition\nUsage signals:\nFirmographic signals:\nIntent signals:\nSales handoff rule:\nDisqualification rule:\n\n## 7. Lifecycle Triggers\nTrigger:\nMessage:\nGoal:\n\n## 8. Pricing \u002F Packaging Suggestions\nWhat to gate:\nWhat to keep free:\nWhat threshold to test:\nRisk of gating too early:\n\n## 9. Growth Pod Sprint Plan\nOwner:\nDesigner:\nEngineer:\nData:\nMarketer \u002F Sales:\nSprint goal:\nDecision cadence:\n\n## 10. Sustainability Score\nCAC payback:\nRetention:\nDefensibility:\nRecommendation:\nDo not do:\n```\n\n## Quality Bar\n\n- Be specific to the user's product, segment, pricing, and usage behavior.\n- Do not suggest signup-volume tactics unless they improve downstream value metrics.\n- Prefer one sharp bottleneck and one first loop over a broad menu.\n- Tie every experiment to a segment, trigger, metric, risk, and timeframe.\n- Mark assumptions and missing instrumentation explicitly.\n",{"name":5,"description":7},"main","f177680a573a242a81bd0a776f9681f620e6d74c","skills\u002Fproductize-plg-growth-playbook",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-plg-growth-playbook",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-plg-growth-playbook",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-plg-growth-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-plg-growth-playbook\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",336,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-plg-growth-playbook\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":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":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]