[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734T1195S2ZFSJE07B1RS7R":3,"skill-same:01M734T1195S2ZFSJE07B1RS7R":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},"01M734T1195S2ZFSJE07B1RS7R","productize-multi-step-workflow-optimization",null,"Multi-step workflow optimization. Use when the user needs a product workflow for design & prototyping related to multi-step workflow optimization. Trigger terms: ux, workflow, friction, funnels, optimization.","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-multi-step-workflow-optimization\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-multi-step-workflow-optimization\ndescription: >-\n  Multi-step workflow optimization. Use when the user needs a product workflow for design &\n  prototyping related to multi-step workflow optimization. Trigger terms: ux, workflow,\n  friction, funnels, optimization.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Multi-step workflow optimization\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**: `multi-step-workflow-optimization`\n- **Lifecycle**: Design\n- **Category**: Design\n- **Primary artifact**: Multi-step workflow optimization UX\u002Fdesign review with findings, constraints, fixes, and acceptance checks\n\nUse this skill to run the Productize prompt contract for **Multi-step workflow optimization**.\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- {{CURRENT_WORKFLOW}}\n- {{USER_ANALYTICS}}\n- {{DROP_OFF_DATA}}\n- {{USER_FEEDBACK}}\n- {{BUSINESS_CONSTRAINTS}}\n\u003C\u002Fprovided_inputs>\n\nGOAL\nProduce a high-quality deliverable for: \"Multi-step workflow optimization\".\nSuccess metric:\n- Produces a full current-state workflow diagnosis with per-step friction and necessity classification.\n- Proposes a lower-friction workflow that improves completion\u002Ftime while preserving required safeguards.\n- Includes a measurable validation plan (A\u002FB or staged rollout) and post-launch iteration logic.\n- Output follows the required structure exactly.\n\nCONSTRAINTS\n- Use only provided inputs; if data is missing, state assumptions explicitly.\n- Analyze the current workflow end-to-end before proposing changes.\n- Provide per-step diagnosis including purpose, required inputs, validation, completion\u002Ftime, errors, friction type, and necessity.\n- Identify top friction points across redundancy, repetition, validation friction, progress clarity, save\u002Fresume, cognitive load, technical friction, and emotional friction.\n- Propose optimizations that reduce steps\u002Ftime\u002Fdrop-off while preserving required legal, security, and quality checkpoints.\n- Keep recommendations specific, testable, and measurable against baseline metrics.\n- Include experimentation and rollout plan with success criteria, rollback conditions, and post-launch monitoring.\n- If exact metrics are unavailable, provide directional estimates and clearly mark them as assumptions.\n\nFORMAT\nReturn exactly this structure:\n\n\u003Cworkflow_optimization>\n\u003Cexecutive_summary>\n**Current State:**\n- Total steps: [X]\n- Average completion rate: [Y%]\n- Average time to complete: [Z minutes]\n- Primary drop-off point: [Step N - why]\n\n**Proposed State:**\n- Total steps: [X - reduced by N]\n- Expected completion rate: [Y + N%]\n- Expected time to complete: [Z - N minutes]\n- Key improvements: [3-5 bullet points]\n\n**Expected Impact:**\n- [Metric]: [Current → Target]\n- [Metric]: [Current → Target]\n- [Business impact]: [e.g., \"10% increase in signups = $X additional revenue\u002Fmonth\"]\n\u003C\u002Fexecutive_summary>\n\n\u003Ccurrent_workflow_analysis>\n**Overall Metrics:**\n- Steps: [Total count]\n- Completion Rate: [X% - what percent of users who start actually finish]\n- Average Time: [Minutes\u002Fseconds]\n- Median Time: [If significantly different from average, indicates confusion for some users]\n- Abandonment Rate: [100 - completion rate]\n\n**Drop-off Analysis:**\n- Step 1: [Name] - [Y% complete this step] - [W% abandon]\n- Step 2: [Name] - [Y% complete] - [W% abandon] ⚠️ [High drop-off? Why?]\n- Step 3: [Name] - [Y% complete] - [W% abandon]\n- [Continue for all steps]\n\n**Top 3 Friction Points:**\n1. [Step\u002FIssue]: [X% abandon] - [Why this is painful]\n2. [Step\u002FIssue]: [Y% abandon] - [Why this is painful]\n3. [Step\u002FIssue]: [Z% abandon] - [Why this is painful]\n\n**Detailed Step Analysis:**\n\nFor each step, provide:\n\n**Step 1: [Name]**\n- **What user does:** [Actions required - e.g., \"Enter name, email, phone number\"]\n- **Why step exists:** [Purpose - e.g., \"Account creation requires contact info\"]\n- **Inputs required:** [List of fields]\n  - [Field]: [Required\u002FOptional] - [Source of data - user memory, lookup, calculation]\n- **Validation:** [What's checked - e.g., \"Email format, phone number format\"]\n- **Completion rate:** [X%] - [Y% drop off at this step]\n- **Average time:** [Z seconds]\n- **Common errors:** [What goes wrong - e.g., \"15% of users enter invalid email format\"]\n- **Friction type:** [Redundant\u002FComplex\u002FUnclear\u002FTedious\u002FUnnecessary]\n- **Problem statement:** [What makes this step difficult or annoying]\n- **Necessity:** ✅ Required (cannot remove) \u002F ⚠️ Required but could be improved \u002F ❌ Unnecessary (can remove or defer)\n\n**Step 2: [Name]**\n[Same detailed structure]\n\n[Continue for all steps]\n\n\u003C\u002Fcurrent_workflow_analysis>\n\n\u003Coptimization_strategies>\n[Describe which of the strategies above you are applying to this workflow, and how.]\n\u003C\u002Foptimization_strategies>\n\n\u003Coptimized_workflow>\n[Describe the new, optimized workflow step-by-step, including which steps were removed, combined, or deferred, and the expected impact on metrics.]\n\u003C\u002Foptimized_workflow>\n\n\u003Cwhat_we_keep>\n[List the critical checkpoints, validations, and safeguards you are intentionally preserving, and why they remain necessary.]\n\u003C\u002Fwhat_we_keep>\n\n\u003Ctesting_plan>\n[Outline the A\u002FB test or rollout approach you will use to validate the improved workflow.]\n\u003C\u002Ftesting_plan>\n\n\u003Cmonitoring_and_iteration>\n[Describe how you will monitor post-launch performance and iterate based on data and feedback.]\n\u003C\u002Fmonitoring_and_iteration>\n\u003C\u002Fworkflow_optimization>\n\nFAILURE\n- Any required section\u002Ftag from `FORMAT` is missing, malformed, or materially incomplete.\n- Current workflow analysis lacks per-step necessity or friction classification.\n- Proposed optimizations remove required safeguards without justification.\n- Testing plan lacks control\u002Fvariant definition or clear decision criteria.\n- Monitoring plan lacks actionable metrics or iteration logic.\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# Multi-step workflow optimization\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**: `multi-step-workflow-optimization`\n- **Lifecycle**: Design\n- **Category**: Design\n- **Primary artifact**: Multi-step workflow optimization UX\u002Fdesign review with findings, constraints, fixes, and acceptance checks\n\nUse this skill to run the Productize prompt contract for **Multi-step workflow optimization**.\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- {{CURRENT_WORKFLOW}}\n- {{USER_ANALYTICS}}\n- {{DROP_OFF_DATA}}\n- {{USER_FEEDBACK}}\n- {{BUSINESS_CONSTRAINTS}}\n\u003C\u002Fprovided_inputs>\n\nGOAL\nProduce a high-quality deliverable for: \"Multi-step workflow optimization\".\nSuccess metric:\n- Produces a full current-state workflow diagnosis with per-step friction and necessity classification.\n- Proposes a lower-friction workflow that improves completion\u002Ftime while preserving required safeguards.\n- Includes a measurable validation plan (A\u002FB or staged rollout) and post-launch iteration logic.\n- Output follows the required structure exactly.\n\nCONSTRAINTS\n- Use only provided inputs; if data is missing, state assumptions explicitly.\n- Analyze the current workflow end-to-end before proposing changes.\n- Provide per-step diagnosis including purpose, required inputs, validation, completion\u002Ftime, errors, friction type, and necessity.\n- Identify top friction points across redundancy, repetition, validation friction, progress clarity, save\u002Fresume, cognitive load, technical friction, and emotional friction.\n- Propose optimizations that reduce steps\u002Ftime\u002Fdrop-off while preserving required legal, security, and quality checkpoints.\n- Keep recommendations specific, testable, and measurable against baseline metrics.\n- Include experimentation and rollout plan with success criteria, rollback conditions, and post-launch monitoring.\n- If exact metrics are unavailable, provide directional estimates and clearly mark them as assumptions.\n\nFORMAT\nReturn exactly this structure:\n\n\u003Cworkflow_optimization>\n\u003Cexecutive_summary>\n**Current State:**\n- Total steps: [X]\n- Average completion rate: [Y%]\n- Average time to complete: [Z minutes]\n- Primary drop-off point: [Step N - why]\n\n**Proposed State:**\n- Total steps: [X - reduced by N]\n- Expected completion rate: [Y + N%]\n- Expected time to complete: [Z - N minutes]\n- Key improvements: [3-5 bullet points]\n\n**Expected Impact:**\n- [Metric]: [Current → Target]\n- [Metric]: [Current → Target]\n- [Business impact]: [e.g., \"10% increase in signups = $X additional revenue\u002Fmonth\"]\n\u003C\u002Fexecutive_summary>\n\n\u003Ccurrent_workflow_analysis>\n**Overall Metrics:**\n- Steps: [Total count]\n- Completion Rate: [X% - what percent of users who start actually finish]\n- Average Time: [Minutes\u002Fseconds]\n- Median Time: [If significantly different from average, indicates confusion for some users]\n- Abandonment Rate: [100 - completion rate]\n\n**Drop-off Analysis:**\n- Step 1: [Name] - [Y% complete this step] - [W% abandon]\n- Step 2: [Name] - [Y% complete] - [W% abandon] ⚠️ [High drop-off? Why?]\n- Step 3: [Name] - [Y% complete] - [W% abandon]\n- [Continue for all steps]\n\n**Top 3 Friction Points:**\n1. [Step\u002FIssue]: [X% abandon] - [Why this is painful]\n2. [Step\u002FIssue]: [Y% abandon] - [Why this is painful]\n3. [Step\u002FIssue]: [Z% abandon] - [Why this is painful]\n\n**Detailed Step Analysis:**\n\nFor each step, provide:\n\n**Step 1: [Name]**\n- **What user does:** [Actions required - e.g., \"Enter name, email, phone number\"]\n- **Why step exists:** [Purpose - e.g., \"Account creation requires contact info\"]\n- **Inputs required:** [List of fields]\n  - [Field]: [Required\u002FOptional] - [Source of data - user memory, lookup, calculation]\n- **Validation:** [What's checked - e.g., \"Email format, phone number format\"]\n- **Completion rate:** [X%] - [Y% drop off at this step]\n- **Average time:** [Z seconds]\n- **Common errors:** [What goes wrong - e.g., \"15% of users enter invalid email format\"]\n- **Friction type:** [Redundant\u002FComplex\u002FUnclear\u002FTedious\u002FUnnecessary]\n- **Problem statement:** [What makes this step difficult or annoying]\n- **Necessity:** ✅ Required (cannot remove) \u002F ⚠️ Required but could be improved \u002F ❌ Unnecessary (can remove or defer)\n\n**Step 2: [Name]**\n[Same detailed structure]\n\n[Continue for all steps]\n\n\u003C\u002Fcurrent_workflow_analysis>\n\n\u003Coptimization_strategies>\n[Describe which of the strategies above you are applying to this workflow, and how.]\n\u003C\u002Foptimization_strategies>\n\n\u003Coptimized_workflow>\n[Describe the new, optimized workflow step-by-step, including which steps were removed, combined, or deferred, and the expected impact on metrics.]\n\u003C\u002Foptimized_workflow>\n\n\u003Cwhat_we_keep>\n[List the critical checkpoints, validations, and safeguards you are intentionally preserving, and why they remain necessary.]\n\u003C\u002Fwhat_we_keep>\n\n\u003Ctesting_plan>\n[Outline the A\u002FB test or rollout approach you will use to validate the improved workflow.]\n\u003C\u002Ftesting_plan>\n\n\u003Cmonitoring_and_iteration>\n[Describe how you will monitor post-launch performance and iterate based on data and feedback.]\n\u003C\u002Fmonitoring_and_iteration>\n\u003C\u002Fworkflow_optimization>\n\nFAILURE\n- Any required section\u002Ftag from `FORMAT` is missing, malformed, or materially incomplete.\n- Current workflow analysis lacks per-step necessity or friction classification.\n- Proposed optimizations remove required safeguards without justification.\n- Testing plan lacks control\u002Fvariant definition or clear decision criteria.\n- Monitoring plan lacks actionable metrics or iteration logic.\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-multi-step-workflow-optimization",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-multi-step-workflow-optimization",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-multi-step-workflow-optimization",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-multi-step-workflow-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-multi-step-workflow-optimization\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",363,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-multi-step-workflow-optimization\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",[],[]]