[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7354EPD81YJ1SY92TF2KM0W":3,"skill-same:01M7354EPD81YJ1SY92TF2KM0W":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},"01M7354EPD81YJ1SY92TF2KM0W","productize-success-metrics-for-design-decisions",null,"Success metrics for design decisions. Use when the user needs a product workflow for business analysis related to success metrics for design decisions. Trigger terms: pm, success-metrics, business-analysis, design.","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-success-metrics-for-design-decisions\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-success-metrics-for-design-decisions\ndescription: >-\n  Success metrics for design decisions. Use when the user needs a product workflow for\n  business analysis related to success metrics for design decisions. Trigger terms: pm,\n  success-metrics, business-analysis, design.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Success metrics for design decisions\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**: `success-metrics-for-design-decisions`\n- **Lifecycle**: Design\n- **Category**: Analytics\n- **Primary artifact**: Success metrics for design decisions UX\u002Fdesign review with findings, constraints, fixes, and acceptance checks\n\nUse this skill to run the Productize prompt contract for **Success metrics for design decisions**.\n\n## Instructions\n\n1. Treat every `{{PLACEHOLDER}}` in the contract as an input to collect, infer, or mark as missing.\n2. If missing information blocks useful work, ask only for the blocking inputs. If work can proceed, state assumptions explicitly.\n3. Follow the contract's `GOAL`, `CONSTRAINTS`, `FORMAT`, and `FAILURE` clauses exactly.\n4. Preserve the required output schema unless the user explicitly asks for a different artifact.\n5. Keep claims grounded in the provided inputs and disclose gaps.\n\n## Prompt Contract\n\nINPUTS\n\u003Cprovided_inputs>\n- {{DESIGN_GOALS}}\n- {{PRODUCT_CONTEXT}}\n- {{USER_OUTCOMES}}\n\u003C\u002Fprovided_inputs>\n\nGOAL\nTranslate `DESIGN_GOALS`, `PRODUCT_CONTEXT`, and `USER_OUTCOMES` into a measurable success-metrics system for design decisions.\nSuccess metric:\n- Defines success from user, business, and product perspectives.\n- Produces primary\u002Fsecondary\u002Fguardrail\u002Fleading metrics with SMART definitions.\n- Includes instrumentation, baseline\u002Ftarget logic, and decision-ready analysis plan.\n- Follows the required output structure exactly.\n\nCONSTRAINTS\n- Use only provided inputs and clearly state assumptions when information is missing.\n- Do not skip required metric-design steps:\n  1. Define success (user\u002Fbusiness\u002Fproduct).\n  2. Map metric types (behavior, outcome, business, quality, leading).\n  3. Apply SMART criteria to each key metric.\n  4. Define measurement approach (instrumentation, tools, sample\u002Fstat criteria).\n  5. Set baselines and targets (minimum, target, stretch, timeframe).\n  6. Add guardrails for unintended consequences.\n- Keep metrics decision-oriented and linked to design goals (avoid vanity metrics).\n- Explicitly note risks\u002Flimitations where metrics may not capture full reality.\n- Label assumptions clearly when baseline\u002Ftooling\u002Fsample data is incomplete.\n\nFORMAT\nReturn exactly this structure:\n\n\u003Csuccess_metrics_framework>\n\u003Csuccess_definitions>\n**User Success Means:**\n[Describe what improves from user perspective - concrete outcomes]\n\n**Business Success Means:**\n[Describe what improves from business perspective - concrete outcomes]\n\n**Product Success Means:**\n[Describe what improves in the product - concrete outcomes]\n\u003C\u002Fsuccess_definitions>\n\n\u003Cprimary_metrics>\n\u003Cmetric_1>\n**Metric Name:** [Clear, specific metric name]\n\n**What It Measures:** [Exactly what behavior or outcome]\n\n**Why It Matters:** [How it connects to goals]\n\n**Type:** [Behavior\u002FOutcome\u002FBusiness\u002FQuality]\n\n**Measurement Method:**\n- How: [Specific tracking approach]\n- Where: [What system\u002Ftool]\n- Frequency: [How often measured]\n- Sample: [Who\u002Fwhat is included]\n\n**Current Baseline:** [If known, current performance]\n\n**Targets:**\n- Minimum acceptable: [X%\u002Fnumber]\n- Target: [Y%\u002Fnumber]\n- Stretch: [Z%\u002Fnumber]\n- Timeframe: [When to measure]\n\n**Statistical Criteria:**\n- Sample size needed: [N users\u002Fsessions]\n- Significance level: [e.g., 95% confidence]\n- Minimum detectable effect: [smallest meaningful change]\n\n**Risks\u002FLimitations:**\n[What could make this metric misleading? What doesn't it capture?]\n\u003C\u002Fmetric_1>\n\n\u003Cmetric_2>\n[Repeat structure for 3-5 primary metrics]\n\u003C\u002Fmetric_2>\n\u003C\u002Fprimary_metrics>\n\n\u003Csupporting_metrics>\n[List 3-5 secondary metrics that provide additional context:\n- Metric name: [Description, why it's useful]\n- Metric name: [Description, why it's useful]]\n\u003C\u002Fsupporting_metrics>\n\n\u003Cguardrail_metrics>\n[Metrics to ensure you're not causing harm:\n- Metric: [Description]\n- Threshold: [What value would indicate a problem]\n- Why: [What unintended consequence this guards against]]\n\u003C\u002Fguardrail_metrics>\n\n\u003Cleading_indicators>\n[Metrics that predict success before primary metrics show results:\n- Indicator: [Description]\n- Why it predicts success: [Connection to outcomes]\n- When to measure: [Timeline]]\n\u003C\u002Fleading_indicators>\n\n\u003Cmeasurement_plan>\n**Implementation Requirements:**\n- Events to track: [List specific events]\n- Properties to capture: [Data points per event]\n- Tools needed: [Analytics platform, A\u002FB test framework, survey tool, etc.]\n- Team dependencies: [Who needs to implement]\n- Timeline: [When instrumentation will be ready]\n\n**Analysis Plan:**\n- Segments to analyze: [User cohorts, use cases, etc.]\n- Comparison approach: [A\u002FB test, before\u002Fafter, cohort comparison]\n- Reporting cadence: [Daily\u002FWeekly\u002FMonthly]\n- Decision timeline: [When to make go\u002Fno-go decision]\n\n**Baseline Collection:**\n[If redesign, describe how to establish current state before changes]\n\u003C\u002Fmeasurement_plan>\n\n\u003Ctradeoff_framework>\n[How to make decisions when metrics conflict:\n- If [Metric A] improves but [Metric B] declines, prioritize [A\u002FB] because [rationale]\n- Acceptable tradeoffs: [What you're willing to sacrifice for what gain]\n- Unacceptable tradeoffs: [What must never decline]]\n\u003C\u002Ftradeoff_framework>\n\n\u003Cqualitative_validation>\n[How to supplement quantitative metrics:\n- User interviews: [What to ask]\n- Usability testing: [What to observe]\n- Support tickets: [What patterns to look for]\n- Feedback surveys: [What questions to include]]\n\u003C\u002Fqualitative_validation>\n\n\u003Cone_page_dashboard>\n[Describe what a single-page success dashboard should show:\n- Key metric tiles\n- Trend visualization\n- Segment breakdowns\n- Guardrail status\n- Action triggers]\n\u003C\u002Fone_page_dashboard>\n\u003C\u002Fsuccess_metrics_framework>\n\nFAILURE\n- Any required schema section is missing or malformed.\n- Metrics are not SMART or not clearly tied to design goals\u002Foutcomes.\n- Baselines\u002Ftargets\u002Ftimeframes are missing for primary metrics.\n- Guardrail or leading indicators are missing.\n- Measurement plan lacks instrumentation detail or decision cadence.\n- Claims are generic or not grounded in provided inputs.\n- Assumptions are used but not explicitly stated.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Success metrics for design decisions\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**: `success-metrics-for-design-decisions`\n- **Lifecycle**: Design\n- **Category**: Analytics\n- **Primary artifact**: Success metrics for design decisions UX\u002Fdesign review with findings, constraints, fixes, and acceptance checks\n\nUse this skill to run the Productize prompt contract for **Success metrics for design decisions**.\n\n## Instructions\n\n1. Treat every `{{PLACEHOLDER}}` in the contract as an input to collect, infer, or mark as missing.\n2. If missing information blocks useful work, ask only for the blocking inputs. If work can proceed, state assumptions explicitly.\n3. Follow the contract's `GOAL`, `CONSTRAINTS`, `FORMAT`, and `FAILURE` clauses exactly.\n4. Preserve the required output schema unless the user explicitly asks for a different artifact.\n5. Keep claims grounded in the provided inputs and disclose gaps.\n\n## Prompt Contract\n\nINPUTS\n\u003Cprovided_inputs>\n- {{DESIGN_GOALS}}\n- {{PRODUCT_CONTEXT}}\n- {{USER_OUTCOMES}}\n\u003C\u002Fprovided_inputs>\n\nGOAL\nTranslate `DESIGN_GOALS`, `PRODUCT_CONTEXT`, and `USER_OUTCOMES` into a measurable success-metrics system for design decisions.\nSuccess metric:\n- Defines success from user, business, and product perspectives.\n- Produces primary\u002Fsecondary\u002Fguardrail\u002Fleading metrics with SMART definitions.\n- Includes instrumentation, baseline\u002Ftarget logic, and decision-ready analysis plan.\n- Follows the required output structure exactly.\n\nCONSTRAINTS\n- Use only provided inputs and clearly state assumptions when information is missing.\n- Do not skip required metric-design steps:\n  1. Define success (user\u002Fbusiness\u002Fproduct).\n  2. Map metric types (behavior, outcome, business, quality, leading).\n  3. Apply SMART criteria to each key metric.\n  4. Define measurement approach (instrumentation, tools, sample\u002Fstat criteria).\n  5. Set baselines and targets (minimum, target, stretch, timeframe).\n  6. Add guardrails for unintended consequences.\n- Keep metrics decision-oriented and linked to design goals (avoid vanity metrics).\n- Explicitly note risks\u002Flimitations where metrics may not capture full reality.\n- Label assumptions clearly when baseline\u002Ftooling\u002Fsample data is incomplete.\n\nFORMAT\nReturn exactly this structure:\n\n\u003Csuccess_metrics_framework>\n\u003Csuccess_definitions>\n**User Success Means:**\n[Describe what improves from user perspective - concrete outcomes]\n\n**Business Success Means:**\n[Describe what improves from business perspective - concrete outcomes]\n\n**Product Success Means:**\n[Describe what improves in the product - concrete outcomes]\n\u003C\u002Fsuccess_definitions>\n\n\u003Cprimary_metrics>\n\u003Cmetric_1>\n**Metric Name:** [Clear, specific metric name]\n\n**What It Measures:** [Exactly what behavior or outcome]\n\n**Why It Matters:** [How it connects to goals]\n\n**Type:** [Behavior\u002FOutcome\u002FBusiness\u002FQuality]\n\n**Measurement Method:**\n- How: [Specific tracking approach]\n- Where: [What system\u002Ftool]\n- Frequency: [How often measured]\n- Sample: [Who\u002Fwhat is included]\n\n**Current Baseline:** [If known, current performance]\n\n**Targets:**\n- Minimum acceptable: [X%\u002Fnumber]\n- Target: [Y%\u002Fnumber]\n- Stretch: [Z%\u002Fnumber]\n- Timeframe: [When to measure]\n\n**Statistical Criteria:**\n- Sample size needed: [N users\u002Fsessions]\n- Significance level: [e.g., 95% confidence]\n- Minimum detectable effect: [smallest meaningful change]\n\n**Risks\u002FLimitations:**\n[What could make this metric misleading? What doesn't it capture?]\n\u003C\u002Fmetric_1>\n\n\u003Cmetric_2>\n[Repeat structure for 3-5 primary metrics]\n\u003C\u002Fmetric_2>\n\u003C\u002Fprimary_metrics>\n\n\u003Csupporting_metrics>\n[List 3-5 secondary metrics that provide additional context:\n- Metric name: [Description, why it's useful]\n- Metric name: [Description, why it's useful]]\n\u003C\u002Fsupporting_metrics>\n\n\u003Cguardrail_metrics>\n[Metrics to ensure you're not causing harm:\n- Metric: [Description]\n- Threshold: [What value would indicate a problem]\n- Why: [What unintended consequence this guards against]]\n\u003C\u002Fguardrail_metrics>\n\n\u003Cleading_indicators>\n[Metrics that predict success before primary metrics show results:\n- Indicator: [Description]\n- Why it predicts success: [Connection to outcomes]\n- When to measure: [Timeline]]\n\u003C\u002Fleading_indicators>\n\n\u003Cmeasurement_plan>\n**Implementation Requirements:**\n- Events to track: [List specific events]\n- Properties to capture: [Data points per event]\n- Tools needed: [Analytics platform, A\u002FB test framework, survey tool, etc.]\n- Team dependencies: [Who needs to implement]\n- Timeline: [When instrumentation will be ready]\n\n**Analysis Plan:**\n- Segments to analyze: [User cohorts, use cases, etc.]\n- Comparison approach: [A\u002FB test, before\u002Fafter, cohort comparison]\n- Reporting cadence: [Daily\u002FWeekly\u002FMonthly]\n- Decision timeline: [When to make go\u002Fno-go decision]\n\n**Baseline Collection:**\n[If redesign, describe how to establish current state before changes]\n\u003C\u002Fmeasurement_plan>\n\n\u003Ctradeoff_framework>\n[How to make decisions when metrics conflict:\n- If [Metric A] improves but [Metric B] declines, prioritize [A\u002FB] because [rationale]\n- Acceptable tradeoffs: [What you're willing to sacrifice for what gain]\n- Unacceptable tradeoffs: [What must never decline]]\n\u003C\u002Ftradeoff_framework>\n\n\u003Cqualitative_validation>\n[How to supplement quantitative metrics:\n- User interviews: [What to ask]\n- Usability testing: [What to observe]\n- Support tickets: [What patterns to look for]\n- Feedback surveys: [What questions to include]]\n\u003C\u002Fqualitative_validation>\n\n\u003Cone_page_dashboard>\n[Describe what a single-page success dashboard should show:\n- Key metric tiles\n- Trend visualization\n- Segment breakdowns\n- Guardrail status\n- Action triggers]\n\u003C\u002Fone_page_dashboard>\n\u003C\u002Fsuccess_metrics_framework>\n\nFAILURE\n- Any required schema section is missing or malformed.\n- Metrics are not SMART or not clearly tied to design goals\u002Foutcomes.\n- Baselines\u002Ftargets\u002Ftimeframes are missing for primary metrics.\n- Guardrail or leading indicators are missing.\n- Measurement plan lacks instrumentation detail or decision cadence.\n- Claims are generic or not grounded in provided inputs.\n- Assumptions are used but not explicitly stated.\n",{"name":5,"description":7},"main","f177680a573a242a81bd0a776f9681f620e6d74c","skills\u002Fproductize-success-metrics-for-design-decisions",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-success-metrics-for-design-decisions",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-success-metrics-for-design-decisions",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-success-metrics-for-design-decisions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-success-metrics-for-design-decisions\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",372,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-success-metrics-for-design-decisions\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",[],[]]