[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734D3ZFMFBGTYAAY7Y7B2QF":3,"skill-same:01M734D3ZFMFBGTYAAY7Y7B2QF":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},"01M734D3ZFMFBGTYAAY7Y7B2QF","productize-aarrr-growth-diagnostics",null,"Diagnose product or startup growth using AARRR pirate metrics, CAC, LTV, channel performance, activation, retention, referral, revenue, and growth engine fit. Use for funnel leakage, growth bottlenecks, SaaS conversion, and go-to-market growth analysis.","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-aarrr-growth-diagnostics\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-aarrr-growth-diagnostics\ndescription: >-\n  Diagnose product or startup growth using AARRR pirate metrics, CAC, LTV, channel\n  performance, activation, retention, referral, revenue, and growth engine fit. Use for funnel\n  leakage, growth bottlenecks, SaaS conversion, and go-to-market growth analysis.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# AARRR Growth Diagnostics\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**: `aarrr-growth-diagnostics`\n- **Lifecycle**: Growth\n- **Category**: Growth\n- **Primary artifact**: AARRR growth diagnosis and prioritized growth action plan\n\nUse this skill when the user needs to understand where growth is leaking and which part of the growth system should be fixed first.\n\nDo not use it for broad market selection, brand narrative, or PMF loop decisions unless the immediate task is funnel diagnosis.\n\n## Core Funnel\n\nAARRR means:\n\n1. **Acquisition**: people arrive or become aware enough to visit, install, inquire, or start.\n2. **Activation**: people experience first value or reach the product's \"wow\" moment.\n3. **Retention**: people come back and continue receiving value.\n4. **Referral**: people invite, share, advocate, or create word-of-mouth.\n5. **Revenue**: people pay, expand, renew, or create monetizable value.\n\nSome businesses measure revenue before referral. Preserve the user's funnel order when it is intentional; otherwise use the sequence above.\n\n## Unit Economics\n\nAlways inspect:\n\n- **CAC**: customer acquisition cost. How much the business spends to acquire a customer or unit.\n- **LTV\u002FCLV**: lifetime value. How much revenue or gross profit the customer generates over time.\n- **Payback**: time required to recover CAC.\n- **Channel cost and quality**: volume, cost, conversion, and retained value by channel.\n\n## Growth Engines\n\nClassify the current or intended engine:\n\n- **Sales-led**: human sales motion, qualification, pipeline, account expansion.\n- **Marketing-led**: paid\u002Fowned\u002Fearned channels, content, campaigns, demand generation.\n- **Product-led**: self-serve acquisition, activation, usage, expansion, virality.\n- **Community-led**: community participation, advocacy, identity, peer learning, network effects.\n\n## Workflow\n\n1. **Map the funnel**\n   - Define the exact event for each AARRR stage.\n   - Use counts, rates, and time windows where possible.\n\n2. **Find the bottleneck**\n   - Compare stage conversion, drop-off, time-to-stage, and segment differences.\n   - Identify whether the constraint is traffic quality, onboarding, value delivery, habit, monetization, or advocacy.\n\n3. **Inspect channels**\n   - Evaluate each acquisition channel by volume, cost, conversion, retained users, and revenue quality.\n   - Watch for channels that look efficient at signup but fail at activation or retention.\n\n4. **Check activation**\n   - Define the first-value or \"wow\" moment.\n   - Compare retained versus churned users by activation actions, timing, and sequence.\n\n5. **Check retention**\n   - Use cohort retention when available.\n   - Distinguish product value failure from lifecycle communication, service, pricing, or expectation mismatch.\n\n6. **Check referral**\n   - Use viral growth factor:\n     - X = percent of users who invite others\n     - Y = average number of invites sent\n     - Z = percent of invitees who accept\n     - Viral factor = X * Y * Z\n\n7. **Prioritize interventions**\n   - Recommend fixing upstream only when downstream economics support it.\n   - Do not scale acquisition into weak activation or retention.\n\n## Output\n\nReturn:\n\n- **Growth Model**: current engine and funnel definitions.\n- **AARRR Scorecard**: counts, conversion rates, benchmark\u002Ftarget if known, confidence.\n- **Leakage Diagnosis**: biggest bottleneck and evidence.\n- **Channel Diagnosis**: volume, cost, conversion, quality, and CAC implications.\n- **Unit Economics**: CAC, LTV\u002FCLV, payback, and risks.\n- **Activation\u002FRetention\u002FReferral Findings**: specific issues and opportunities.\n- **Priority Moves**: ranked actions with expected mechanism, metric, owner if known, and time-to-signal.\n- **Instrumentation Gaps**: missing events, cohorts, segments, or attribution.\n\n## Quality Bar\n\n- Do not optimize acquisition before checking activation and retention.\n- Do not treat signups as success unless first value and retention are healthy.\n- Separate vanity metrics from value metrics.\n- Tie recommendations to measurable stage movement.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# AARRR Growth Diagnostics\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**: `aarrr-growth-diagnostics`\n- **Lifecycle**: Growth\n- **Category**: Growth\n- **Primary artifact**: AARRR growth diagnosis and prioritized growth action plan\n\nUse this skill when the user needs to understand where growth is leaking and which part of the growth system should be fixed first.\n\nDo not use it for broad market selection, brand narrative, or PMF loop decisions unless the immediate task is funnel diagnosis.\n\n## Core Funnel\n\nAARRR means:\n\n1. **Acquisition**: people arrive or become aware enough to visit, install, inquire, or start.\n2. **Activation**: people experience first value or reach the product's \"wow\" moment.\n3. **Retention**: people come back and continue receiving value.\n4. **Referral**: people invite, share, advocate, or create word-of-mouth.\n5. **Revenue**: people pay, expand, renew, or create monetizable value.\n\nSome businesses measure revenue before referral. Preserve the user's funnel order when it is intentional; otherwise use the sequence above.\n\n## Unit Economics\n\nAlways inspect:\n\n- **CAC**: customer acquisition cost. How much the business spends to acquire a customer or unit.\n- **LTV\u002FCLV**: lifetime value. How much revenue or gross profit the customer generates over time.\n- **Payback**: time required to recover CAC.\n- **Channel cost and quality**: volume, cost, conversion, and retained value by channel.\n\n## Growth Engines\n\nClassify the current or intended engine:\n\n- **Sales-led**: human sales motion, qualification, pipeline, account expansion.\n- **Marketing-led**: paid\u002Fowned\u002Fearned channels, content, campaigns, demand generation.\n- **Product-led**: self-serve acquisition, activation, usage, expansion, virality.\n- **Community-led**: community participation, advocacy, identity, peer learning, network effects.\n\n## Workflow\n\n1. **Map the funnel**\n   - Define the exact event for each AARRR stage.\n   - Use counts, rates, and time windows where possible.\n\n2. **Find the bottleneck**\n   - Compare stage conversion, drop-off, time-to-stage, and segment differences.\n   - Identify whether the constraint is traffic quality, onboarding, value delivery, habit, monetization, or advocacy.\n\n3. **Inspect channels**\n   - Evaluate each acquisition channel by volume, cost, conversion, retained users, and revenue quality.\n   - Watch for channels that look efficient at signup but fail at activation or retention.\n\n4. **Check activation**\n   - Define the first-value or \"wow\" moment.\n   - Compare retained versus churned users by activation actions, timing, and sequence.\n\n5. **Check retention**\n   - Use cohort retention when available.\n   - Distinguish product value failure from lifecycle communication, service, pricing, or expectation mismatch.\n\n6. **Check referral**\n   - Use viral growth factor:\n     - X = percent of users who invite others\n     - Y = average number of invites sent\n     - Z = percent of invitees who accept\n     - Viral factor = X * Y * Z\n\n7. **Prioritize interventions**\n   - Recommend fixing upstream only when downstream economics support it.\n   - Do not scale acquisition into weak activation or retention.\n\n## Output\n\nReturn:\n\n- **Growth Model**: current engine and funnel definitions.\n- **AARRR Scorecard**: counts, conversion rates, benchmark\u002Ftarget if known, confidence.\n- **Leakage Diagnosis**: biggest bottleneck and evidence.\n- **Channel Diagnosis**: volume, cost, conversion, quality, and CAC implications.\n- **Unit Economics**: CAC, LTV\u002FCLV, payback, and risks.\n- **Activation\u002FRetention\u002FReferral Findings**: specific issues and opportunities.\n- **Priority Moves**: ranked actions with expected mechanism, metric, owner if known, and time-to-signal.\n- **Instrumentation Gaps**: missing events, cohorts, segments, or attribution.\n\n## Quality Bar\n\n- Do not optimize acquisition before checking activation and retention.\n- Do not treat signups as success unless first value and retention are healthy.\n- Separate vanity metrics from value metrics.\n- Tie recommendations to measurable stage movement.\n",{"name":5,"description":7},"main","f177680a573a242a81bd0a776f9681f620e6d74c","skills\u002Fproductize-aarrr-growth-diagnostics",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-aarrr-growth-diagnostics",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-aarrr-growth-diagnostics",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-aarrr-growth-diagnostics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-aarrr-growth-diagnostics\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",351,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-aarrr-growth-diagnostics\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",[],[]]