[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7353FEZTNYWNANKY123G1K4":3,"skill-same:01M7353FEZTNYWNANKY123G1K4":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},"01M7353FEZTNYWNANKY123G1K4","productize-strategy-to-execution-bridge-for-ux-decisions",null,"Strategy-to-execution bridge for UX decisions. Use when the user needs a product workflow for product strategy related to strategy-to-execution bridge for ux decisions. Trigger terms: ux, product-strategy, execution, roadmapping.","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-strategy-to-execution-bridge-for-ux-decisions\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-strategy-to-execution-bridge-for-ux-decisions\ndescription: >-\n  Strategy-to-execution bridge for UX decisions. Use when the user needs a product workflow\n  for product strategy related to strategy-to-execution bridge for ux decisions. Trigger\n  terms: ux, product-strategy, execution, roadmapping.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Strategy-to-execution bridge for UX 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**: `strategy-to-execution-bridge-for-ux-decisions`\n- **Lifecycle**: Strategize\n- **Category**: Strategy\n- **Primary artifact**: Strategy-to-execution bridge for UX decisions strategy memo with choices, tradeoffs, risks, and recommended next move\n\nUse this skill to run the Productize prompt contract for **Strategy-to-execution bridge for UX 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- {{VISION_STRATEGY}}\n- {{CURRENT_QUARTER_OBJECTIVES}}\n- {{DESIGN_TEAM_CAPACITY}}\n- {{EXISTING_DESIGN_SYSTEM}}\n- {{TECHNICAL_CONSTRAINTS}}\n\u003C\u002Fprovided_inputs>\n\nGOAL\nProduce a high-quality deliverable for: \"Strategy-to-execution bridge for UX decisions\".\nSuccess metric:\n- Translates vision and objectives into concrete UX principles, patterns, and execution plans.\n- Produces a quarter-by-quarter roadmap with dependencies, risks, and success criteria.\n- Provides decision frameworks that connect daily design choices to strategy.\n- Output follows the required structure exactly.\n\nCONSTRAINTS\n- Use only provided inputs; if information is missing, state assumptions explicitly.\n- Extract 3–5 strategic themes and map them to UX goals, patterns, and decision principles.\n- Build a quarterly execution plan with dependencies, success criteria, and capacity fit.\n- Identify gaps, blockers, and research needs that prevent execution.\n- Provide a multi-phase roadmap, validation plan, and feedback loops.\n\nFORMAT\nReturn exactly this structure:\n\n\u003Cstrategy_to_execution_bridge>\n\u003Cvision_analysis>\n## Strategic Themes\n\n[List 3–5 core strategic themes extracted from vision, with brief explanation of each]\n\n**Theme 1: [Name]**\n- Description: [What this theme means strategically]\n- UX implications: [How this affects user experience]\n- Key phrases from vision: \"[Quote relevant language]\"\n\n**Theme 2: [Name]**\n[Same structure]\n\n## User Experience Goals\n\n[Specific UX outcomes mentioned or strongly implied by vision]\n\n1. **[Goal name]:** [Description and rationale]\n   - Success looks like: [Observable outcome]\n   - Measurement: [How to track progress]\n\n2. **[Goal name]:** [Description]  \n   [Continue for each goal]\n\n## Market Positioning\n\n**Target positioning:** [Premium\u002Faccessible, technical\u002Fintuitive, comprehensive\u002Ffocused, etc.]  \n**Competitive differentiation:** [How vision positions against competitors]  \n**Customer segment priority:** [Which personas or segments are prioritized]  \n**Brand personality:** [Tone, voice, aesthetic implied]\n\n## Vision Gaps and Ambiguities\n\n[Areas where vision is too vague for execution]\n\n- **Ambiguity:** \"[Vague term or conflicting signal]\"\n  - **Why this matters:** [Impact on design decisions]\n  - **Question to resolve:** [Specific question stakeholders must answer]\n  - **Temporary assumption:** [What to assume if answer isn't available]\n\n[Continue for each ambiguity]\n\n\u003C\u002Fvision_analysis>\n\n\u003Cux_translation>\n## Design Principles\n\n[4–6 principles that operationalize the vision – avoid generic platitudes]\n\n**Principle 1: [Specific, actionable principle]**\n- **What it means:** [Operational definition]\n- **How to apply:** [Decision heuristic or guideline]\n- **Example:** [Concrete example of principle in action]\n- **Anti-pattern:** [What to avoid that violates this principle]\n\n**Principle 2: [Name]**  \n[Same structure]\n\n## Required UX Patterns\n\n[Specific interaction patterns needed to realize strategic themes]\n\n**Strategic Theme:** [Theme name]\n\n**Required Patterns:**\n1. **[Pattern name]** – [Brief description]\n   - Use cases: [Where this pattern appears]\n   - Component needs: [Design system elements required]\n   - Examples: [Reference products or specific instances]\n\n2. **[Pattern name]** – [Description]  \n   [Continue]\n\n[Repeat for each strategic theme]\n\n## Information Architecture Implications\n\n[How vision affects IA and content structure]\n\n**Navigation strategy:** [Top-level navigation approach implied by vision – task-based, feature-based, role-based, etc.]  \n**Content hierarchy:** [What information is primary vs. secondary]  \n**Discoverability approach:** [How users find features – guided onboarding, search-first, exploration, etc.]  \n**Conceptual model:** [How vision wants users to think about the product]\n\n**IA changes needed:**\n- [Specific IA shifts required to align with vision]\n- [Continue]\n\n## Visual and Interaction Design Direction\n\n**Aesthetic:** [Visual style implied – minimal, expressive, data-dense, spacious, etc.]  \n**Interaction patterns:** [Gestural, form-based, conversational, drag-and-drop, etc.]  \n**Motion and animation:** [Role of animation – functional only, delightful, prominent, minimal]  \n**Density and spacing:** [Information density – compact, generous, adaptive]  \n**Color strategy:** [Use of color – vibrant, muted, semantic only, brand-forward]\n\n## Component and Pattern Inventory\n\n[Comprehensive list of design system components needed for vision]\n\n**Existing components sufficient for vision:**\n- [Component name] – [How it supports vision]\n- [Continue]\n\n**Existing components needing enhancement:**\n- [Component name] – [What enhancement is needed and why]\n- [Continue]\n\n**New components required:**\n- [Component name] – [Purpose and rationale]\n  - Priority: [Critical \u002F High \u002F Medium \u002F Low]\n  - Dependencies: [What must exist first]\n  - Effort estimate: [Design days \u002F complexity]\n- [Continue]\n\n\u003C\u002Fux_translation>\n\n\u003Cquarterly_execution_plan>\n## Q1 Scope: Actionable This Quarter\n\n[Vision elements that can be designed and delivered this quarter]\n\n### Initiative 1: [Name]\n\n**Strategic theme:** [Which theme this advances]  \n**Design deliverables:**\n- [Specific deliverable] – [Completion date]\n- [Continue]\n\n**Design effort:** [X days research, Y days design, Z iteration cycles]  \n**Dependencies:**\n- Design: [Dependencies within design team]\n- Research: [User research needs]\n- Engineering: [Technical dependencies]\n- Product: [Product decisions needed]\n- External: [Third-party or other team dependencies]\n\n**Success criteria:**\n- Design quality: [Standards to meet]\n- User outcomes: [Behavioral or satisfaction metrics]\n- Business metrics: [Adoption, conversion, revenue, etc.]\n- Learning goals: [Assumptions validated or de-risked]\n\n**Risks and mitigations:**\n- **Risk:** [Potential issue]\n  - **Likelihood:** [High\u002FMedium\u002FLow]\n  - **Impact:** [High\u002FMedium\u002FLow]\n  - **Mitigation:** [How to reduce risk]\n\n[Continue for each Q1 initiative]\n\n## Foundational Work Required\n\n[Prerequisite work needed before vision elements can be executed]\n\n### Foundation 1: [Name]\n\n**What it enables:** [Which vision elements depend on this]  \n**Why it's foundational:** [Explanation of dependency]  \n**Deliverables:**\n- [Specific output]\n- [Continue]\n\n**Timeline:** [When this must be complete and why]  \n**Effort:** [Resource estimate]\n\n[Continue for each foundational item]\n\n## Deferred to Q2+\n\n[Vision elements not actionable this quarter]\n\n### Deferred Initiative: [Name]\n\n**Strategic theme:** [Which theme this advances]  \n**Why deferred:** [Blocker – capacity, dependencies, uncertainty, etc.]  \n**What's needed to activate:**\n- [Prerequisite] – [Who\u002Fwhat\u002Fwhen]\n- [Continue]\n\n**Tentative timeline:** [When this could begin]\n\n[Continue for each deferred item]\n\n## Capacity Analysis\n\n**Total design capacity:** [X designer-days available this quarter]  \n**Allocated capacity:**\n- Q1 initiatives: [Y designer-days] ([Z]% of capacity)\n- Foundational work: [Y designer-days] ([Z]%)\n- Maintenance and support: [Y designer-days] ([Z]%)\n- Buffer for unknowns: [Y designer-days] ([Z]%)\n\n**Capacity status:** [Over-committed \u002F Fully allocated \u002F Under-utilized]\n\n**Recommendations:**\n- [If over-committed: what to descope or defer]\n- [If under-utilized: what to pull forward or invest in]\n- [Prioritization rationale]\n\n\u003C\u002Fquarterly_execution_plan>\n\n\u003Cdecision_frameworks>\n## Daily Design Decision Criteria\n\n[Questions to ask when making design choices to ensure vision alignment]\n\n### When Choosing Between Design Alternatives\n\n1. **Vision alignment check:** Which option better advances strategic themes [list themes]?\n   - Option A: [How it aligns or conflicts]\n   - Option B: [How it aligns or conflicts]\n   - Winner: [Which to choose and why]\n\n2. **Scalability evaluation:** Which option extends to future use cases implied by vision?\n   - Consider: [Upcoming features or use cases]\n   - Test: [Can this pattern handle those scenarios?]\n\n3. **Consistency assessment:** Which option reinforces established patterns vs. introducing divergence?\n   - If new pattern is needed: [Justify with strategic rationale]\n   - If consistency conflicts with vision: [Escalate or document tradeoff]\n\n4. **User value prioritization:** Which option prioritizes user needs over internal convenience?\n   - Red flag: [Designs optimized for engineering simplicity or business politics over UX]\n\n5. **Technical feasibility reality check:** Is this implementable within constraints?\n   - If not: [Adjust design or advocate for constraint removal]\n   - If workaround needed: [Ensure workaround doesn't degrade UX]\n\n### When Vision and Immediate Needs Conflict\n\n**Favor vision if:**\n- Immediate need is temporary or can be solved another way\n- Vision direction is high-confidence and well-validated\n- Technical debt from immediate solution is significant\n\n**Favor immediate need if:**\n- Blocker for users or business (not just internal inconvenience)\n- Vision direction is uncertain or likely to change\n- Can be implemented without major technical debt\n\n**Seek creative middle ground:**\n- Phased rollout (simple now, vision-aligned later)\n- Feature flags (ship both, test and learn)\n- Modular design (immediate solution doesn't preclude vision path)\n\n**Escalate when:**\n- Tradeoff has significant strategic implications\n- Decision affects multiple teams or long-term architecture\n- Stakeholder alignment is needed\n\n### Pattern Establishment vs. Deferral\n\n**Standardize now if:**\n- Pattern will be used in 3+ places imminently\n- Consistency is critical for usability (e.g., error handling, form validation)\n- Foundation for other patterns (e.g., base components)\n\n**Defer standardization if:**\n- Single-use or rare use case\n- Vision direction unclear and pattern may change\n- Pattern is experimental and needs validation first\n\n**Create flexible pattern if:**\n- Vision direction uncertain but action needed now\n- Multiple future variations likely\n- Learning required before locking in specific implementation\n\n### Scope Management\n\n**When new requests arise outside quarterly plan:**\n\n1. **Does this directly advance a Q1 vision element?**\n   - Yes → Evaluate against current priorities\n   - No → Default to defer unless exception criteria met\n\n2. **Exception criteria:**\n   - Critical user blocker (cannot accomplish core tasks)\n   - Regulatory or legal requirement\n   - Foundational for Q2+ work (pull forward)\n   - Opportunistic (very low effort, high strategic value)\n\n3. **If considering inclusion, ask: What would we deprioritize?**\n   - Evaluate tradeoff explicitly\n   - Ensure swapped item is truly lower priority\n   - Get stakeholder alignment on change\n\n4. **Can this be achieved with existing patterns?**\n   - Yes → Lower cost, more likely to include\n   - No → Higher bar for inclusion\n\n\u003C\u002Fdecision_frameworks>\n\n\u003Cgaps_and_dependencies>\n## Strategic Gaps Requiring Clarification\n\n[Where strategy needs more definition before design can proceed confidently]\n\n**Gap 1: [Topic]**\n- **Ambiguity:** [What's unclear]\n- **Design impact:** [Why this blocks or confuses design work]\n- **Question for stakeholders:** [Specific question]\n- **Decision owner:** [Who should answer]\n- **Urgency:** [When answer is needed – this week, this month, this quarter]\n- **Temporary path forward:** [What to assume if answer delayed]\n\n[Continue for each strategic gap]\n\n## Technical Dependencies and Blockers\n\n[Required technical capabilities that don't exist yet]\n\n**Dependency 1: [Capability name]**\n- **What it enables:** [Design work or vision elements blocked without this]\n- **Current status:** [Not started \u002F In progress \u002F Blocked]\n- **Owner:** [Team or person responsible]\n- **Timeline:** [When this will be available]\n- **Design impact if delayed:** [Consequences for design roadmap]\n- **Workaround if unavailable:** [Alternative approach or descoped experience]\n\n[Continue for each technical dependency]\n\n## Research Needs and Unknowns\n\n[Questions that must be answered through user research]\n\n**Research Need 1: [Topic]**\n- **Question:** [Specific research question]\n- **Why this matters:** [Design decisions that depend on answer]\n- **Hypotheses:** [Current assumptions to validate or invalidate]\n- **Research method:** [Interviews, usability testing, survey, analytics analysis, etc.]\n- **Participants:** [Who to include – personas, segments, sample size]\n- **Timeline:** [When research must complete to inform design]\n- **Owner:** [Researcher or designer responsible]\n- **Design path if answer is X:** [Decision tree based on findings]\n- **Design path if answer is Y:** [Alternative direction]\n\n[Continue for each research need]\n\n## Design System Gaps\n\n[Missing design system components or patterns needed for vision]\n\n**Gap 1: [Component or pattern name]**\n- **Vision element requiring this:** [Strategic theme or initiative this supports]\n- **Why existing components insufficient:** [What's missing or inadequate]\n- **Scope of new component:**\n  - States: [Default, hover, focus, disabled, error, loading, etc.]\n  - Variants: [Size, style, or functional variations needed]\n  - Responsive behavior: [Mobile, tablet, desktop considerations]\n  - Accessibility requirements: [Keyboard nav, screen reader, WCAG compliance]\n- **Effort estimate:** [Design days, complexity level]\n- **Dependencies:** [Other components or patterns this builds on]\n- **Priority:** [Critical \u002F High \u002F Medium \u002F Low]\n- **Timeline need:** [When this must be ready]\n\n[Continue for each design system gap]\n\n## Cross-Functional Dependencies\n\n[What other teams must deliver for design to proceed or ship]\n\n**Dependency on [Team Name]:**\n- **What's needed:** [Specific deliverable or decision]\n- **Why design needs this:** [Blocker explanation]\n- **Owner:** [Name or role]\n- **Requested by:** [Date]\n- **Committed date:** [When they'll deliver, if known]\n- **Status:** [On track \u002F At risk \u002F Blocked \u002F Unknown]\n- **Design contingency:** [What design does if this is delayed]\n\n[Continue for each cross-functional dependency]\n\n\u003C\u002Fgaps_and_dependencies>\n\n\u003Cimplementation_roadmap>\n## Phase 1: Current Quarter (Q1) – Foundation and Momentum\n\n**Timeline:** [Dates]  \n**Goal:** [High-level objective for this phase]\n\n### Foundational Work\n[Work that enables future phases – design system, research, core patterns]\n\n**Foundation:** [Name]\n- **Deliverables:** [Specific outputs]\n- **Effort:** [Resource estimate]\n- **Completion:** [Target date]\n- **Unlocks:** [What becomes possible after this]\n\n[Continue for each foundation]\n\n### Quick Wins\n[High-impact, low-effort improvements demonstrating vision progress]\n\n**Quick Win:** [Name]\n- **Impact:** [User or business value]\n- **Effort:** [Low effort explanation]\n- **Delivery:** [Target date]\n- **Strategic signal:** [Which vision theme this demonstrates]\n\n[Continue for each quick win]\n\n### Critical Path Items\n[Blockers for Q2+ work that must complete this quarter]\n\n**Critical Item:** [Name]\n- **Why critical:** [Explanation of dependency]\n- **Risk if delayed:** [Downstream impact]\n- **Deliverables:** [Specific outputs]\n- **Date:** [Must complete by]\n\n[Continue for each critical item]\n\n### Learning Experiments\n[Small tests to validate assumptions before major investment]\n\n**Experiment:** [Name]\n- **Hypothesis:** [What we're testing]\n- **Method:** [How we'll test – prototype, survey, A\u002FB test, etc.]\n- **Success criteria:** [What results validate hypothesis]\n- **Failure criteria:** [What results invalidate hypothesis]\n- **Decision:** [What we'll do based on results]\n- **Timeline:** [Duration of experiment]\n\n[Continue for each experiment]\n\n### Q1 Success Criteria\n\n**Design outputs:**\n- [ ] [Specific deliverable or milestone]\n- [ ] [Continue]\n\n**User outcomes:**\n- [ ] [Metric or qualitative signal]\n- [ ] [Continue]\n\n**Business results:**\n- [ ] [KPI or goal]\n- [ ] [Continue]\n\n**Strategic progress:**\n- [ ] [Vision element advanced or de-risked]\n- [ ] [Continue]\n\n## Phase 2: Next Two Quarters (Q2–Q3) – Building Toward Vision\n\n**Timeline:** [Dates]  \n**Goal:** [High-level objective for this phase]\n\n### Major Initiatives\n[Large design efforts advancing core strategic themes]\n\n**Initiative:** [Name]\n- **Strategic theme:** [Which theme this advances]\n- **Scope:** [High-level description]\n- **Dependencies:** [What from Phase 1 must be complete]\n- **Milestones:**\n  - [Milestone 1] – [Date]\n  - [Milestone 2] – [Date]\n- **Success criteria:** [How to measure success]\n\n[Continue for each major initiative]\n\n### Integration and Coherence Work\n[Connecting Phase 1 foundations into cohesive experiences]\n\n**Integration Work:** [Name]\n- **What's being integrated:** [Components, patterns, or features]\n- **Why integration matters:** [User benefit or strategic value]\n- **Timeline:** [When this happens]\n\n[Continue for each integration]\n\n### Iteration and Refinement\n[Improving based on Phase 1 learnings]\n\n**Area for refinement:** [Name]\n- **Phase 1 learning:** [What we learned]\n- **Refinement needed:** [How to improve]\n- **Timeline:** [When this happens]\n\n[Continue for each refinement area]\n\n### Decision Checkpoints\n[Points where direction may adjust based on data]\n\n**Checkpoint:** [When – e.g., \"End of Q2\"]\n- **Decision:** [What will be decided]\n- **Data inputs:** [Metrics, research, or signals informing decision]\n- **Options:** [Possible directions based on data]\n- **Decision owner:** [Who decides]\n\n[Continue for each checkpoint]\n\n## Phase 3: Future Quarters (Q4+) – Vision Realization\n\n**Timeline:** [Dates or \"Q4 and beyond\"]  \n**Goal:** [High-level objective for this phase]\n\n### Vision Completion\n[Fully realized strategic themes]\n\n**Strategic Theme:** [Name]\n- **Vision state:** [Description of fully realized theme]\n- **What's needed to complete:**\n  - [Work item]\n  - [Continue]\n- **Success criteria:** [How to know theme is fully realized]\n\n[Continue for each strategic theme]\n\n### Polish and Elevation\n[Raising experience quality to match vision]\n\n**Polish area:** [Name]\n- **Current state:** [Where quality falls short]\n- **Vision state:** [Target quality level]\n- **Work required:** [What it takes to close gap]\n\n[Continue for each polish area]\n\n### Scale and Robustness\n[Handling edge cases, localization, advanced use cases]\n\n**Scaling dimension:** [Name – e.g., \"Localization,\" \"Edge case handling\"]\n- **Scope:** [What must scale]\n- **Complexity:** [Challenges involved]\n- **Timeline:** [When this is addressed]\n\n[Continue for each scaling dimension]\n\n### Measurement and Validation\n[Confirming strategic goals achieved]\n\n**Strategic goal:** [Goal from vision]\n- **Measurement approach:** [How to validate achievement]\n- **Target metric:** [Specific number or threshold]\n- **Review cadence:** [When to check progress]\n\n[Continue for each strategic goal]\n\n## Ongoing Across All Phases\n\n### Maintenance and Debt Reduction\n**Allocation:** [% of capacity per quarter]  \n**Focus areas:**\n- [Area needing maintenance – e.g., \"accessibility improvements,\" \"mobile optimization\"]\n- [Continue]\n\n### Flexibility Buffer\n**Allocation:** [% of capacity held for emerging priorities]  \n**Use for:** [Unplanned work, urgent requests, pivots]\n\n### Research and Discovery\n**Allocation:** [% of capacity for ongoing learning]  \n**Focus:** [Continuous research to inform future phases]\n\n## Roadmap Visualization\n\n[If helpful, provide a timeline visual or table showing initiatives across phases]\n\n**Q1:** [List key initiatives]  \n**Q2:** [List key initiatives]  \n**Q3:** [List key initiatives]  \n**Q4+:** [List key initiatives]\n\n\u003C\u002Fimplementation_roadmap>\n\n\u003Cassumptions_and_validation>\n## Vision Assumptions to Validate\n\n[Beliefs embedded in strategy that should be tested]\n\n**Assumption 1: [Statement]**\n- **Type:** [Market \u002F User behavior \u002F Competitive \u002F Business model]\n- **Source:** [Where this assumption comes from in vision]\n- **Confidence level:** [High \u002F Medium \u002F Low]\n- **Validation method:** [How to test this]\n- **Timeline:** [When to validate]\n- **Impact if wrong:** [Consequence of false assumption]\n- **Pivot options:** [Alternative directions if invalidated]\n\n[Continue for each assumption]\n\n## Design Hypotheses\n\n[Testable beliefs about UX approaches]\n\n**Hypothesis 1: [Statement]**\n- **Rationale:** [Why we believe this]\n- **Test method:** [How to validate – prototype testing, A\u002FB test, analytics, etc.]\n- **Success criteria:** [Evidence that confirms hypothesis]\n- **Failure criteria:** [Evidence that refutes hypothesis]\n- **Timeline:** [When to test]\n- **Decision tree:**\n  - If validated: [Design direction to pursue]\n  - If invalidated: [Alternative approach]\n  - If inconclusive: [Further research or conservative path]\n\n[Continue for each hypothesis]\n\n## Success Indicators and Monitoring\n\n### Leading Indicators\n[Early signals that validate or invalidate direction]\n\n**Indicator:** [Metric or signal]\n- **What it measures:** [What this tells us]\n- **Target:** [Threshold or trend]\n- **Measurement method:** [How to track]\n- **Frequency:** [How often to check]\n- **Green flag:** [Signal we're on track]\n- **Yellow flag:** [Signal to investigate]\n- **Red flag:** [Signal to pivot]\n\n[Continue for each indicator]\n\n### Lagging Indicators\n[Longer-term outcomes confirming strategic success]\n\n**Indicator:** [Metric or signal]\n- **What it measures:** [What this tells us]\n- **Target:** [Threshold or goal]\n- **Timeline:** [When to expect result]\n- **Measurement method:** [How to track]\n\n[Continue for each indicator]\n\n## Review Cadence and Feedback Loops\n\n### Weekly Design Reviews\n**Attendees:** [Roles]  \n**Agenda:**\n- Work in progress review\n- **Strategy alignment check:** [Quick assessment of whether work advances vision]\n- Blockers and dependencies\n- Upcoming decisions\n\n### Mid-Quarter Checkpoint\n**Timing:** [Week 6 of 13-week quarter]  \n**Purpose:** Assess if on track to hit Q1 success criteria  \n**Review:**\n- Progress vs. plan\n- Capacity actuals vs. estimates\n- Dependency status\n- Emerging risks\n- Adjustment needs\n\n### End-of-Quarter Retrospective\n**Timing:** [Final week of quarter]  \n**Purpose:** Learn and inform next quarter planning  \n**Review:**\n- Q1 success criteria achievement\n- Assumption validation results\n- What worked well \u002F What didn't\n- Roadmap adjustments needed\n- Phase 2 planning input\n\n### Strategy Review with Leadership\n**Cadence:** [Quarterly or semi-annually]  \n**Purpose:** Ensure design work aligns with evolving business strategy  \n**Topics:**\n- Vision progress report\n- Key learnings and pivots\n- Roadmap alignment with business priorities\n- Resource needs for upcoming phases\n\n## Escalation Triggers\n\n[When to pause and reconsider direction]\n\n**Trigger 1: User research contradicts core assumptions**\n- **Action:** [Immediate review of affected design work, stakeholder alignment meeting]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 2: Technical feasibility proves impossible or dramatically more expensive**\n- **Action:** [Evaluate alternative approaches, possibly descope or rearchitect]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 3: Business priorities shift**\n- **Action:** [Reassess roadmap, reprioritize quarterly plan]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 4: Competitive landscape changes significantly**\n- **Action:** [Competitive analysis update, strategy review meeting]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 5: Success metrics trending negatively**\n- **Action:** [Root cause analysis, corrective action plan]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n\u003C\u002Fassumptions_and_validation>\n\u003C\u002Fstrategy_to_execution_bridge>\n\nFAILURE\n- Any required section\u002Ftag in `FORMAT` is missing, malformed, or incomplete.\n- Strategic themes or UX goals are missing or not tied to the vision.\n- Execution plan lacks dependencies, success criteria, or capacity analysis.\n- Validation and feedback loops are missing or superficial.\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# Strategy-to-execution bridge for UX 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**: `strategy-to-execution-bridge-for-ux-decisions`\n- **Lifecycle**: Strategize\n- **Category**: Strategy\n- **Primary artifact**: Strategy-to-execution bridge for UX decisions strategy memo with choices, tradeoffs, risks, and recommended next move\n\nUse this skill to run the Productize prompt contract for **Strategy-to-execution bridge for UX 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- {{VISION_STRATEGY}}\n- {{CURRENT_QUARTER_OBJECTIVES}}\n- {{DESIGN_TEAM_CAPACITY}}\n- {{EXISTING_DESIGN_SYSTEM}}\n- {{TECHNICAL_CONSTRAINTS}}\n\u003C\u002Fprovided_inputs>\n\nGOAL\nProduce a high-quality deliverable for: \"Strategy-to-execution bridge for UX decisions\".\nSuccess metric:\n- Translates vision and objectives into concrete UX principles, patterns, and execution plans.\n- Produces a quarter-by-quarter roadmap with dependencies, risks, and success criteria.\n- Provides decision frameworks that connect daily design choices to strategy.\n- Output follows the required structure exactly.\n\nCONSTRAINTS\n- Use only provided inputs; if information is missing, state assumptions explicitly.\n- Extract 3–5 strategic themes and map them to UX goals, patterns, and decision principles.\n- Build a quarterly execution plan with dependencies, success criteria, and capacity fit.\n- Identify gaps, blockers, and research needs that prevent execution.\n- Provide a multi-phase roadmap, validation plan, and feedback loops.\n\nFORMAT\nReturn exactly this structure:\n\n\u003Cstrategy_to_execution_bridge>\n\u003Cvision_analysis>\n## Strategic Themes\n\n[List 3–5 core strategic themes extracted from vision, with brief explanation of each]\n\n**Theme 1: [Name]**\n- Description: [What this theme means strategically]\n- UX implications: [How this affects user experience]\n- Key phrases from vision: \"[Quote relevant language]\"\n\n**Theme 2: [Name]**\n[Same structure]\n\n## User Experience Goals\n\n[Specific UX outcomes mentioned or strongly implied by vision]\n\n1. **[Goal name]:** [Description and rationale]\n   - Success looks like: [Observable outcome]\n   - Measurement: [How to track progress]\n\n2. **[Goal name]:** [Description]  \n   [Continue for each goal]\n\n## Market Positioning\n\n**Target positioning:** [Premium\u002Faccessible, technical\u002Fintuitive, comprehensive\u002Ffocused, etc.]  \n**Competitive differentiation:** [How vision positions against competitors]  \n**Customer segment priority:** [Which personas or segments are prioritized]  \n**Brand personality:** [Tone, voice, aesthetic implied]\n\n## Vision Gaps and Ambiguities\n\n[Areas where vision is too vague for execution]\n\n- **Ambiguity:** \"[Vague term or conflicting signal]\"\n  - **Why this matters:** [Impact on design decisions]\n  - **Question to resolve:** [Specific question stakeholders must answer]\n  - **Temporary assumption:** [What to assume if answer isn't available]\n\n[Continue for each ambiguity]\n\n\u003C\u002Fvision_analysis>\n\n\u003Cux_translation>\n## Design Principles\n\n[4–6 principles that operationalize the vision – avoid generic platitudes]\n\n**Principle 1: [Specific, actionable principle]**\n- **What it means:** [Operational definition]\n- **How to apply:** [Decision heuristic or guideline]\n- **Example:** [Concrete example of principle in action]\n- **Anti-pattern:** [What to avoid that violates this principle]\n\n**Principle 2: [Name]**  \n[Same structure]\n\n## Required UX Patterns\n\n[Specific interaction patterns needed to realize strategic themes]\n\n**Strategic Theme:** [Theme name]\n\n**Required Patterns:**\n1. **[Pattern name]** – [Brief description]\n   - Use cases: [Where this pattern appears]\n   - Component needs: [Design system elements required]\n   - Examples: [Reference products or specific instances]\n\n2. **[Pattern name]** – [Description]  \n   [Continue]\n\n[Repeat for each strategic theme]\n\n## Information Architecture Implications\n\n[How vision affects IA and content structure]\n\n**Navigation strategy:** [Top-level navigation approach implied by vision – task-based, feature-based, role-based, etc.]  \n**Content hierarchy:** [What information is primary vs. secondary]  \n**Discoverability approach:** [How users find features – guided onboarding, search-first, exploration, etc.]  \n**Conceptual model:** [How vision wants users to think about the product]\n\n**IA changes needed:**\n- [Specific IA shifts required to align with vision]\n- [Continue]\n\n## Visual and Interaction Design Direction\n\n**Aesthetic:** [Visual style implied – minimal, expressive, data-dense, spacious, etc.]  \n**Interaction patterns:** [Gestural, form-based, conversational, drag-and-drop, etc.]  \n**Motion and animation:** [Role of animation – functional only, delightful, prominent, minimal]  \n**Density and spacing:** [Information density – compact, generous, adaptive]  \n**Color strategy:** [Use of color – vibrant, muted, semantic only, brand-forward]\n\n## Component and Pattern Inventory\n\n[Comprehensive list of design system components needed for vision]\n\n**Existing components sufficient for vision:**\n- [Component name] – [How it supports vision]\n- [Continue]\n\n**Existing components needing enhancement:**\n- [Component name] – [What enhancement is needed and why]\n- [Continue]\n\n**New components required:**\n- [Component name] – [Purpose and rationale]\n  - Priority: [Critical \u002F High \u002F Medium \u002F Low]\n  - Dependencies: [What must exist first]\n  - Effort estimate: [Design days \u002F complexity]\n- [Continue]\n\n\u003C\u002Fux_translation>\n\n\u003Cquarterly_execution_plan>\n## Q1 Scope: Actionable This Quarter\n\n[Vision elements that can be designed and delivered this quarter]\n\n### Initiative 1: [Name]\n\n**Strategic theme:** [Which theme this advances]  \n**Design deliverables:**\n- [Specific deliverable] – [Completion date]\n- [Continue]\n\n**Design effort:** [X days research, Y days design, Z iteration cycles]  \n**Dependencies:**\n- Design: [Dependencies within design team]\n- Research: [User research needs]\n- Engineering: [Technical dependencies]\n- Product: [Product decisions needed]\n- External: [Third-party or other team dependencies]\n\n**Success criteria:**\n- Design quality: [Standards to meet]\n- User outcomes: [Behavioral or satisfaction metrics]\n- Business metrics: [Adoption, conversion, revenue, etc.]\n- Learning goals: [Assumptions validated or de-risked]\n\n**Risks and mitigations:**\n- **Risk:** [Potential issue]\n  - **Likelihood:** [High\u002FMedium\u002FLow]\n  - **Impact:** [High\u002FMedium\u002FLow]\n  - **Mitigation:** [How to reduce risk]\n\n[Continue for each Q1 initiative]\n\n## Foundational Work Required\n\n[Prerequisite work needed before vision elements can be executed]\n\n### Foundation 1: [Name]\n\n**What it enables:** [Which vision elements depend on this]  \n**Why it's foundational:** [Explanation of dependency]  \n**Deliverables:**\n- [Specific output]\n- [Continue]\n\n**Timeline:** [When this must be complete and why]  \n**Effort:** [Resource estimate]\n\n[Continue for each foundational item]\n\n## Deferred to Q2+\n\n[Vision elements not actionable this quarter]\n\n### Deferred Initiative: [Name]\n\n**Strategic theme:** [Which theme this advances]  \n**Why deferred:** [Blocker – capacity, dependencies, uncertainty, etc.]  \n**What's needed to activate:**\n- [Prerequisite] – [Who\u002Fwhat\u002Fwhen]\n- [Continue]\n\n**Tentative timeline:** [When this could begin]\n\n[Continue for each deferred item]\n\n## Capacity Analysis\n\n**Total design capacity:** [X designer-days available this quarter]  \n**Allocated capacity:**\n- Q1 initiatives: [Y designer-days] ([Z]% of capacity)\n- Foundational work: [Y designer-days] ([Z]%)\n- Maintenance and support: [Y designer-days] ([Z]%)\n- Buffer for unknowns: [Y designer-days] ([Z]%)\n\n**Capacity status:** [Over-committed \u002F Fully allocated \u002F Under-utilized]\n\n**Recommendations:**\n- [If over-committed: what to descope or defer]\n- [If under-utilized: what to pull forward or invest in]\n- [Prioritization rationale]\n\n\u003C\u002Fquarterly_execution_plan>\n\n\u003Cdecision_frameworks>\n## Daily Design Decision Criteria\n\n[Questions to ask when making design choices to ensure vision alignment]\n\n### When Choosing Between Design Alternatives\n\n1. **Vision alignment check:** Which option better advances strategic themes [list themes]?\n   - Option A: [How it aligns or conflicts]\n   - Option B: [How it aligns or conflicts]\n   - Winner: [Which to choose and why]\n\n2. **Scalability evaluation:** Which option extends to future use cases implied by vision?\n   - Consider: [Upcoming features or use cases]\n   - Test: [Can this pattern handle those scenarios?]\n\n3. **Consistency assessment:** Which option reinforces established patterns vs. introducing divergence?\n   - If new pattern is needed: [Justify with strategic rationale]\n   - If consistency conflicts with vision: [Escalate or document tradeoff]\n\n4. **User value prioritization:** Which option prioritizes user needs over internal convenience?\n   - Red flag: [Designs optimized for engineering simplicity or business politics over UX]\n\n5. **Technical feasibility reality check:** Is this implementable within constraints?\n   - If not: [Adjust design or advocate for constraint removal]\n   - If workaround needed: [Ensure workaround doesn't degrade UX]\n\n### When Vision and Immediate Needs Conflict\n\n**Favor vision if:**\n- Immediate need is temporary or can be solved another way\n- Vision direction is high-confidence and well-validated\n- Technical debt from immediate solution is significant\n\n**Favor immediate need if:**\n- Blocker for users or business (not just internal inconvenience)\n- Vision direction is uncertain or likely to change\n- Can be implemented without major technical debt\n\n**Seek creative middle ground:**\n- Phased rollout (simple now, vision-aligned later)\n- Feature flags (ship both, test and learn)\n- Modular design (immediate solution doesn't preclude vision path)\n\n**Escalate when:**\n- Tradeoff has significant strategic implications\n- Decision affects multiple teams or long-term architecture\n- Stakeholder alignment is needed\n\n### Pattern Establishment vs. Deferral\n\n**Standardize now if:**\n- Pattern will be used in 3+ places imminently\n- Consistency is critical for usability (e.g., error handling, form validation)\n- Foundation for other patterns (e.g., base components)\n\n**Defer standardization if:**\n- Single-use or rare use case\n- Vision direction unclear and pattern may change\n- Pattern is experimental and needs validation first\n\n**Create flexible pattern if:**\n- Vision direction uncertain but action needed now\n- Multiple future variations likely\n- Learning required before locking in specific implementation\n\n### Scope Management\n\n**When new requests arise outside quarterly plan:**\n\n1. **Does this directly advance a Q1 vision element?**\n   - Yes → Evaluate against current priorities\n   - No → Default to defer unless exception criteria met\n\n2. **Exception criteria:**\n   - Critical user blocker (cannot accomplish core tasks)\n   - Regulatory or legal requirement\n   - Foundational for Q2+ work (pull forward)\n   - Opportunistic (very low effort, high strategic value)\n\n3. **If considering inclusion, ask: What would we deprioritize?**\n   - Evaluate tradeoff explicitly\n   - Ensure swapped item is truly lower priority\n   - Get stakeholder alignment on change\n\n4. **Can this be achieved with existing patterns?**\n   - Yes → Lower cost, more likely to include\n   - No → Higher bar for inclusion\n\n\u003C\u002Fdecision_frameworks>\n\n\u003Cgaps_and_dependencies>\n## Strategic Gaps Requiring Clarification\n\n[Where strategy needs more definition before design can proceed confidently]\n\n**Gap 1: [Topic]**\n- **Ambiguity:** [What's unclear]\n- **Design impact:** [Why this blocks or confuses design work]\n- **Question for stakeholders:** [Specific question]\n- **Decision owner:** [Who should answer]\n- **Urgency:** [When answer is needed – this week, this month, this quarter]\n- **Temporary path forward:** [What to assume if answer delayed]\n\n[Continue for each strategic gap]\n\n## Technical Dependencies and Blockers\n\n[Required technical capabilities that don't exist yet]\n\n**Dependency 1: [Capability name]**\n- **What it enables:** [Design work or vision elements blocked without this]\n- **Current status:** [Not started \u002F In progress \u002F Blocked]\n- **Owner:** [Team or person responsible]\n- **Timeline:** [When this will be available]\n- **Design impact if delayed:** [Consequences for design roadmap]\n- **Workaround if unavailable:** [Alternative approach or descoped experience]\n\n[Continue for each technical dependency]\n\n## Research Needs and Unknowns\n\n[Questions that must be answered through user research]\n\n**Research Need 1: [Topic]**\n- **Question:** [Specific research question]\n- **Why this matters:** [Design decisions that depend on answer]\n- **Hypotheses:** [Current assumptions to validate or invalidate]\n- **Research method:** [Interviews, usability testing, survey, analytics analysis, etc.]\n- **Participants:** [Who to include – personas, segments, sample size]\n- **Timeline:** [When research must complete to inform design]\n- **Owner:** [Researcher or designer responsible]\n- **Design path if answer is X:** [Decision tree based on findings]\n- **Design path if answer is Y:** [Alternative direction]\n\n[Continue for each research need]\n\n## Design System Gaps\n\n[Missing design system components or patterns needed for vision]\n\n**Gap 1: [Component or pattern name]**\n- **Vision element requiring this:** [Strategic theme or initiative this supports]\n- **Why existing components insufficient:** [What's missing or inadequate]\n- **Scope of new component:**\n  - States: [Default, hover, focus, disabled, error, loading, etc.]\n  - Variants: [Size, style, or functional variations needed]\n  - Responsive behavior: [Mobile, tablet, desktop considerations]\n  - Accessibility requirements: [Keyboard nav, screen reader, WCAG compliance]\n- **Effort estimate:** [Design days, complexity level]\n- **Dependencies:** [Other components or patterns this builds on]\n- **Priority:** [Critical \u002F High \u002F Medium \u002F Low]\n- **Timeline need:** [When this must be ready]\n\n[Continue for each design system gap]\n\n## Cross-Functional Dependencies\n\n[What other teams must deliver for design to proceed or ship]\n\n**Dependency on [Team Name]:**\n- **What's needed:** [Specific deliverable or decision]\n- **Why design needs this:** [Blocker explanation]\n- **Owner:** [Name or role]\n- **Requested by:** [Date]\n- **Committed date:** [When they'll deliver, if known]\n- **Status:** [On track \u002F At risk \u002F Blocked \u002F Unknown]\n- **Design contingency:** [What design does if this is delayed]\n\n[Continue for each cross-functional dependency]\n\n\u003C\u002Fgaps_and_dependencies>\n\n\u003Cimplementation_roadmap>\n## Phase 1: Current Quarter (Q1) – Foundation and Momentum\n\n**Timeline:** [Dates]  \n**Goal:** [High-level objective for this phase]\n\n### Foundational Work\n[Work that enables future phases – design system, research, core patterns]\n\n**Foundation:** [Name]\n- **Deliverables:** [Specific outputs]\n- **Effort:** [Resource estimate]\n- **Completion:** [Target date]\n- **Unlocks:** [What becomes possible after this]\n\n[Continue for each foundation]\n\n### Quick Wins\n[High-impact, low-effort improvements demonstrating vision progress]\n\n**Quick Win:** [Name]\n- **Impact:** [User or business value]\n- **Effort:** [Low effort explanation]\n- **Delivery:** [Target date]\n- **Strategic signal:** [Which vision theme this demonstrates]\n\n[Continue for each quick win]\n\n### Critical Path Items\n[Blockers for Q2+ work that must complete this quarter]\n\n**Critical Item:** [Name]\n- **Why critical:** [Explanation of dependency]\n- **Risk if delayed:** [Downstream impact]\n- **Deliverables:** [Specific outputs]\n- **Date:** [Must complete by]\n\n[Continue for each critical item]\n\n### Learning Experiments\n[Small tests to validate assumptions before major investment]\n\n**Experiment:** [Name]\n- **Hypothesis:** [What we're testing]\n- **Method:** [How we'll test – prototype, survey, A\u002FB test, etc.]\n- **Success criteria:** [What results validate hypothesis]\n- **Failure criteria:** [What results invalidate hypothesis]\n- **Decision:** [What we'll do based on results]\n- **Timeline:** [Duration of experiment]\n\n[Continue for each experiment]\n\n### Q1 Success Criteria\n\n**Design outputs:**\n- [ ] [Specific deliverable or milestone]\n- [ ] [Continue]\n\n**User outcomes:**\n- [ ] [Metric or qualitative signal]\n- [ ] [Continue]\n\n**Business results:**\n- [ ] [KPI or goal]\n- [ ] [Continue]\n\n**Strategic progress:**\n- [ ] [Vision element advanced or de-risked]\n- [ ] [Continue]\n\n## Phase 2: Next Two Quarters (Q2–Q3) – Building Toward Vision\n\n**Timeline:** [Dates]  \n**Goal:** [High-level objective for this phase]\n\n### Major Initiatives\n[Large design efforts advancing core strategic themes]\n\n**Initiative:** [Name]\n- **Strategic theme:** [Which theme this advances]\n- **Scope:** [High-level description]\n- **Dependencies:** [What from Phase 1 must be complete]\n- **Milestones:**\n  - [Milestone 1] – [Date]\n  - [Milestone 2] – [Date]\n- **Success criteria:** [How to measure success]\n\n[Continue for each major initiative]\n\n### Integration and Coherence Work\n[Connecting Phase 1 foundations into cohesive experiences]\n\n**Integration Work:** [Name]\n- **What's being integrated:** [Components, patterns, or features]\n- **Why integration matters:** [User benefit or strategic value]\n- **Timeline:** [When this happens]\n\n[Continue for each integration]\n\n### Iteration and Refinement\n[Improving based on Phase 1 learnings]\n\n**Area for refinement:** [Name]\n- **Phase 1 learning:** [What we learned]\n- **Refinement needed:** [How to improve]\n- **Timeline:** [When this happens]\n\n[Continue for each refinement area]\n\n### Decision Checkpoints\n[Points where direction may adjust based on data]\n\n**Checkpoint:** [When – e.g., \"End of Q2\"]\n- **Decision:** [What will be decided]\n- **Data inputs:** [Metrics, research, or signals informing decision]\n- **Options:** [Possible directions based on data]\n- **Decision owner:** [Who decides]\n\n[Continue for each checkpoint]\n\n## Phase 3: Future Quarters (Q4+) – Vision Realization\n\n**Timeline:** [Dates or \"Q4 and beyond\"]  \n**Goal:** [High-level objective for this phase]\n\n### Vision Completion\n[Fully realized strategic themes]\n\n**Strategic Theme:** [Name]\n- **Vision state:** [Description of fully realized theme]\n- **What's needed to complete:**\n  - [Work item]\n  - [Continue]\n- **Success criteria:** [How to know theme is fully realized]\n\n[Continue for each strategic theme]\n\n### Polish and Elevation\n[Raising experience quality to match vision]\n\n**Polish area:** [Name]\n- **Current state:** [Where quality falls short]\n- **Vision state:** [Target quality level]\n- **Work required:** [What it takes to close gap]\n\n[Continue for each polish area]\n\n### Scale and Robustness\n[Handling edge cases, localization, advanced use cases]\n\n**Scaling dimension:** [Name – e.g., \"Localization,\" \"Edge case handling\"]\n- **Scope:** [What must scale]\n- **Complexity:** [Challenges involved]\n- **Timeline:** [When this is addressed]\n\n[Continue for each scaling dimension]\n\n### Measurement and Validation\n[Confirming strategic goals achieved]\n\n**Strategic goal:** [Goal from vision]\n- **Measurement approach:** [How to validate achievement]\n- **Target metric:** [Specific number or threshold]\n- **Review cadence:** [When to check progress]\n\n[Continue for each strategic goal]\n\n## Ongoing Across All Phases\n\n### Maintenance and Debt Reduction\n**Allocation:** [% of capacity per quarter]  \n**Focus areas:**\n- [Area needing maintenance – e.g., \"accessibility improvements,\" \"mobile optimization\"]\n- [Continue]\n\n### Flexibility Buffer\n**Allocation:** [% of capacity held for emerging priorities]  \n**Use for:** [Unplanned work, urgent requests, pivots]\n\n### Research and Discovery\n**Allocation:** [% of capacity for ongoing learning]  \n**Focus:** [Continuous research to inform future phases]\n\n## Roadmap Visualization\n\n[If helpful, provide a timeline visual or table showing initiatives across phases]\n\n**Q1:** [List key initiatives]  \n**Q2:** [List key initiatives]  \n**Q3:** [List key initiatives]  \n**Q4+:** [List key initiatives]\n\n\u003C\u002Fimplementation_roadmap>\n\n\u003Cassumptions_and_validation>\n## Vision Assumptions to Validate\n\n[Beliefs embedded in strategy that should be tested]\n\n**Assumption 1: [Statement]**\n- **Type:** [Market \u002F User behavior \u002F Competitive \u002F Business model]\n- **Source:** [Where this assumption comes from in vision]\n- **Confidence level:** [High \u002F Medium \u002F Low]\n- **Validation method:** [How to test this]\n- **Timeline:** [When to validate]\n- **Impact if wrong:** [Consequence of false assumption]\n- **Pivot options:** [Alternative directions if invalidated]\n\n[Continue for each assumption]\n\n## Design Hypotheses\n\n[Testable beliefs about UX approaches]\n\n**Hypothesis 1: [Statement]**\n- **Rationale:** [Why we believe this]\n- **Test method:** [How to validate – prototype testing, A\u002FB test, analytics, etc.]\n- **Success criteria:** [Evidence that confirms hypothesis]\n- **Failure criteria:** [Evidence that refutes hypothesis]\n- **Timeline:** [When to test]\n- **Decision tree:**\n  - If validated: [Design direction to pursue]\n  - If invalidated: [Alternative approach]\n  - If inconclusive: [Further research or conservative path]\n\n[Continue for each hypothesis]\n\n## Success Indicators and Monitoring\n\n### Leading Indicators\n[Early signals that validate or invalidate direction]\n\n**Indicator:** [Metric or signal]\n- **What it measures:** [What this tells us]\n- **Target:** [Threshold or trend]\n- **Measurement method:** [How to track]\n- **Frequency:** [How often to check]\n- **Green flag:** [Signal we're on track]\n- **Yellow flag:** [Signal to investigate]\n- **Red flag:** [Signal to pivot]\n\n[Continue for each indicator]\n\n### Lagging Indicators\n[Longer-term outcomes confirming strategic success]\n\n**Indicator:** [Metric or signal]\n- **What it measures:** [What this tells us]\n- **Target:** [Threshold or goal]\n- **Timeline:** [When to expect result]\n- **Measurement method:** [How to track]\n\n[Continue for each indicator]\n\n## Review Cadence and Feedback Loops\n\n### Weekly Design Reviews\n**Attendees:** [Roles]  \n**Agenda:**\n- Work in progress review\n- **Strategy alignment check:** [Quick assessment of whether work advances vision]\n- Blockers and dependencies\n- Upcoming decisions\n\n### Mid-Quarter Checkpoint\n**Timing:** [Week 6 of 13-week quarter]  \n**Purpose:** Assess if on track to hit Q1 success criteria  \n**Review:**\n- Progress vs. plan\n- Capacity actuals vs. estimates\n- Dependency status\n- Emerging risks\n- Adjustment needs\n\n### End-of-Quarter Retrospective\n**Timing:** [Final week of quarter]  \n**Purpose:** Learn and inform next quarter planning  \n**Review:**\n- Q1 success criteria achievement\n- Assumption validation results\n- What worked well \u002F What didn't\n- Roadmap adjustments needed\n- Phase 2 planning input\n\n### Strategy Review with Leadership\n**Cadence:** [Quarterly or semi-annually]  \n**Purpose:** Ensure design work aligns with evolving business strategy  \n**Topics:**\n- Vision progress report\n- Key learnings and pivots\n- Roadmap alignment with business priorities\n- Resource needs for upcoming phases\n\n## Escalation Triggers\n\n[When to pause and reconsider direction]\n\n**Trigger 1: User research contradicts core assumptions**\n- **Action:** [Immediate review of affected design work, stakeholder alignment meeting]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 2: Technical feasibility proves impossible or dramatically more expensive**\n- **Action:** [Evaluate alternative approaches, possibly descope or rearchitect]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 3: Business priorities shift**\n- **Action:** [Reassess roadmap, reprioritize quarterly plan]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 4: Competitive landscape changes significantly**\n- **Action:** [Competitive analysis update, strategy review meeting]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n**Trigger 5: Success metrics trending negatively**\n- **Action:** [Root cause analysis, corrective action plan]\n- **Decision owner:** [Role]\n- **Timeline:** [How quickly to respond]\n\n\u003C\u002Fassumptions_and_validation>\n\u003C\u002Fstrategy_to_execution_bridge>\n\nFAILURE\n- Any required section\u002Ftag in `FORMAT` is missing, malformed, or incomplete.\n- Strategic themes or UX goals are missing or not tied to the vision.\n- Execution plan lacks dependencies, success criteria, or capacity analysis.\n- Validation and feedback loops are missing or superficial.\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-strategy-to-execution-bridge-for-ux-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-strategy-to-execution-bridge-for-ux-decisions",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-strategy-to-execution-bridge-for-ux-decisions",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-strategy-to-execution-bridge-for-ux-decisions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-strategy-to-execution-bridge-for-ux-decisions\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",387,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-strategy-to-execution-bridge-for-ux-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",[],[]]