[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P60AG6GC7WC08GAF69MKB8":3,"skill-same:01M6P60AG6GC7WC08GAF69MKB8":98},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":77,"commitSha":78,"skillDirectory":79,"forksCount":80,"repositoryHtmlUrl":81,"repositoryHomepageUrl":6,"ownerHtmlUrl":82,"ownerBlogUrl":83,"ownerDescription":6,"updatedAt":84,"install":85,"resources":97},"01M6P60AG6GC7WC08GAF69MKB8","product-positioning",null,"Produces a reframed product positioning — a before\u002Fafter statement that replaces a keep-or-kill decision with a complementary role for the product — plus a set of strategic routes that leverage that role. Use when: 'should we deprecate X now that we have Y', 'this feature feels redundant', 'we cannot decide whether to keep this product', 'two things in our portfolio seem to overlap'.","DojoGenesis\u002Fgateway","DojoGenesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273886418?v=4","01M6P54RXMD3TZ2082Z3Z4JMQP","Cruz Morales (TresPies)","01M6P54S269YR0ZZZ96WGQM439",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fstrategic-thinking\u002Fskills\u002Fproduct-positioning\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"product positioning","positioning","product","feature","things","for","true","opus","strategic","now","STRING","leverage","thinking","kill","portfolio","use","decide","decision","system","SET","2026-11-10 10:12:30",false,"---\nname: product-positioning\nmodel: opus\ndescription: \"Produces a reframed product positioning — a before\u002Fafter statement that replaces a keep-or-kill decision with a complementary role for the product — plus a set of strategic routes that leverage that role. Use when: 'should we deprecate X now that we have Y', 'this feature feels redundant', 'we cannot decide whether to keep this product', 'two things in our portfolio seem to overlap'.\"\ncategory: strategic-thinking\ntriggers:\n  - \"should we deprecate X now that we have Y\"\n  - \"this feature feels redundant\"\n  - \"we cannot decide whether to keep this product\"\n  - \"two things in our portfolio seem to overlap\"\ntier: 1\nagents:\n  - \"primary\"\ntool_dependencies:\n  - \"file_system\"\n\ninputs:\n  - name: product_tension\n    type: string\n    description: The keep-or-kill decision or overlap tension to resolve through positioning\n    required: true\noutputs:\n  - name: positioning_document\n    type: ref\n    format: cas-ref\n    description: Reframed product positioning with before\u002Fafter statement and strategic routes leveraging the complementary role\n---\n\n# Product Positioning Scout Skill\n\n**Version:** 1.1  \n**Created:** 2026-02-07  \n**Updated:** 2026-02-07  \n**Author:** Manus AI  \n**Purpose:** To guide the process of reframing a binary product decision into a strategic product positioning opportunity by identifying the unique value of a product or feature.\n\n---\n\n## I. The Philosophy: Beyond the Binary\n\nThe most common trap in product strategy is the binary choice: keep or kill, build or buy, deprecate or maintain. These choices are limiting because they assume the value of a product is fixed. The Product Positioning Scout operates on a different principle: **value is contextual**.\n\nThis skill is about breaking free from the binary trap by asking a more powerful question: **\"What is this uniquely good at?\"** By identifying the unique context in which a product or feature shines, we can transform a \"legacy\" feature into a \"premium\" experience, a \"redundant\" product into a \"complementary\" one.\n\n**The core insight:** The reframe is the prize, not the initial answer.\n\n---\n\n## II. When to Use This Skill\n\n- When facing a decision about whether to keep or deprecate a feature or product\n- When a product or feature seems redundant or is underperforming\n- When planning a multi-surface product strategy (e.g., web, desktop, mobile)\n- At the beginning of a strategic planning cycle\n- Before using `\u002Fstrategic-scout` to ensure the question is properly framed\n\n---\n\n## III. The Workflow\n\nThis is a 5-step workflow for reframing a product decision.\n\n### Step 1: Identify the Binary Trap\n\n**Goal:** Recognize when a strategic question is being framed as a simple, limiting binary choice.\n\n**Actions:**\n- Listen for questions like \"Should we keep X or get rid of it?\"\n- Notice when the conversation is focused on resource allocation rather than strategic value\n- Identify the implicit assumption that the product\u002Ffeature has only one use case\n\n**Output:** A clear articulation of the binary trap\n\n**Example:** \"Should we deprecate the web app now that we're building desktop?\"\n\n---\n\n### Step 2: Introduce the Unlocking Question\n\n**Goal:** Reframe the conversation by asking a question that shatters the binary and opens up new possibilities.\n\n**Actions:**\n- Ask: **\"What is this uniquely good at that the other thing isn't?\"**\n- Shift the focus from \"what to do with this\" to \"what is its unique value?\"\n- Challenge the assumption that products must compete rather than complement\n\n**Output:** A reframed question that opens up new strategic possibilities\n\n**Example:** \"What is the web app uniquely good at that desktop isn't?\" → Discovery, onboarding, cross-platform access without installation\n\n---\n\n### Step 3: Explore the Unique Value\n\n**Goal:** Brainstorm the unique strengths and contexts of the product in question.\n\n**Actions:**\n- List the unique strengths of the product\u002Ffeature\n- Identify the specific contexts (e.g., mobile, on-the-go, deep work) where those strengths are most valuable\n- Consider edge cases and niche use cases that might be surprisingly valuable\n\n**Output:** A comprehensive list of unique value propositions\n\n**Example for web app:**\n- No installation required\n- Cross-platform (works on any OS)\n- Easy to share via URL\n- Great for discovery and onboarding\n- Accessible from any device\n\n---\n\n### Step 4: Re-Scout with the New Lens\n\n**Goal:** Use the new understanding of unique value to re-scout the strategic options.\n\n**Actions:**\n- Use `\u002Fstrategic-scout` with the new framing\n- Explore routes that leverage the unique value (e.g., Mobile-First PWA, Native Companion App)\n- Consider complementary positioning rather than competitive positioning\n\n**Output:** A set of strategic routes that leverage the unique value\n\n**Example routes:**\n- Route 1: Web as discovery, desktop as core product\n- Route 2: Web as free tier, desktop as premium\n- Route 3: Web for onboarding, desktop for power users\n- Route 4: Deprecate web, focus on desktop (original binary)\n\n---\n\n### Step 5: Synthesize and Propose New Positioning\n\n**Goal:** Synthesize the new routes into a coherent product strategy and positioning.\n\n**Actions:**\n- Select the best route (e.g., Hybrid - PWA Now, Native Later)\n- Define the new product positioning (e.g., Desktop for deep work, Mobile for on-the-go orchestration)\n- Propose a new timeline and pricing model\n- Document the strategic rationale\n\n**Output:** A complete product positioning strategy\n\n**Example:** \"Desktop as core ($20\u002Fmonth), Mobile PWA as premium tier (separate subscription, 4-6 weeks after desktop v1)\"\n\n---\n\n## IV. Best Practices\n\n### 1. The Reframe is Everything\n\n**Why:** The most powerful strategic moves come from reframing the question, not from choosing between existing options.\n\n**How:** Always start by questioning the framing of the decision. Is it really a binary choice?\n\n---\n\n### 2. Value is Contextual\n\n**Why:** A product's value is not inherent; it's determined by the context in which it's used.\n\n**How:** For every product\u002Ffeature, ask \"In what context is this uniquely valuable?\"\n\n---\n\n### 3. Complement, Don't Compete\n\n**Why:** The best multi-surface strategies create complementary experiences, not competing ones.\n\n**How:** Frame each surface by its unique job-to-be-done, not by its feature list.\n\n---\n\n### 4. The Unlocking Question is Universal\n\n**Why:** \"What is this uniquely good at?\" works for products, features, surfaces, and even people.\n\n**How:** Use this question whenever you're facing a binary decision about value.\n\n---\n\n### 5. Document the Reframe\n\n**Why:** The reframe is the most valuable artifact. It changes how everyone thinks about the product.\n\n**How:** Write down the before\u002Fafter framing explicitly. Share it widely.\n\n---\n\n## V. Quality Checklist\n\nBefore delivering the new strategy, ensure you can answer \"yes\" to all of the following questions:\n\n- [ ] Have you identified and articulated the initial binary trap?\n- [ ] Have you asked the \"Unlocking Question\" to reframe the conversation?\n- [ ] Have you clearly defined the unique value and context of the product\u002Ffeature?\n- [ ] Have you used `\u002Fstrategic-scout` to explore new routes based on the new framing?\n- [ ] Have you proposed a new, coherent product positioning, timeline, and business model?\n- [ ] Have you documented the strategic rationale for the new positioning?\n\n---\n\n## VI. Example: Dojo Genesis Web App Positioning\n\n**The Binary Trap:** \"Should we deprecate the web app now that we're building desktop?\"\n\n**The Unlocking Question:** \"What is the web app uniquely good at that desktop isn't?\"\n\n**The Unique Value:**\n- No installation required\n- Cross-platform access\n- Easy to share via URL\n- Great for discovery and onboarding\n- Accessible from any device\n\n**The Re-Scout:** Used `\u002Fstrategic-scout` to explore 4 routes:\n1. Deprecate web, focus on desktop\n2. Web as companion (lightweight version)\n3. Web as discovery\u002Fonboarding, desktop as core\n4. Hybrid - PWA now, native later\n\n**The New Positioning:**\n- **Desktop:** Core product for deep work ($20\u002Fmonth)\n- **Mobile PWA:** Premium tier for on-the-go orchestration (separate subscription, 4-6 weeks after desktop v1)\n- **Web:** Free tier for discovery and onboarding\n\n**The Outcome:** Transformed a deprecation decision into a multi-surface strategy where each surface has a unique, complementary role.\n\n**Key Insight:** The web app wasn't redundant—it was uniquely good at discovery and onboarding. Desktop is uniquely good at deep work. Mobile is uniquely good at on-the-go orchestration.\n\n---\n\n## VII. Common Pitfalls to Avoid\n\n### Pitfall 1: Accepting the Binary Without Question\n\n**Problem:** Most binary choices are false binaries. Accepting them limits strategic options.\n\n**Solution:** Always question the framing. Ask \"Is this really a binary choice?\"\n\n---\n\n### Pitfall 2: Focusing on Features Instead of Context\n\n**Problem:** Comparing feature lists leads to \"X is redundant because Y has all its features.\"\n\n**Solution:** Focus on context of use, not feature parity. Ask \"What is this uniquely good at?\"\n\n---\n\n### Pitfall 3: Competitive Positioning by Default\n\n**Problem:** Assuming products must compete rather than complement.\n\n**Solution:** Explore complementary positioning first. Competition should be a last resort.\n\n---\n\n### Pitfall 4: Skipping the Re-Scout\n\n**Problem:** Reframing the question but not exploring new routes based on the reframe.\n\n**Solution:** Always use `\u002Fstrategic-scout` after reframing to explore new possibilities.\n\n---\n\n### Pitfall 5: Not Documenting the Reframe\n\n**Problem:** The reframe gets lost in conversation. People revert to the binary.\n\n**Solution:** Write down the before\u002Fafter framing explicitly. Make it a reference document.\n\n---\n\n## VIII. Related Skills\n\n- **`strategic-scout`** - Use this after reframing to explore new routes\n- **`iterative-scouting`** - Use this to refine the positioning based on feedback\n- **`multi-surface-strategy`** - Use this to design the complete multi-surface strategy\n- **`release-specification`** - Use this to write specs for the new positioning\n- **`strategic-to-tactical-workflow`** - Use this to move from positioning to implementation\n\n---\n\n## Output\n\n- Before\u002Fafter framing document: the original binary question stated explicitly, then the reframed question and its implications\n- Unique value list: 3-7 specific strengths of the product tied to concrete usage contexts, not generic adjectives\n- Strategic routes: 3-5 routes that capitalize on the reframe, each with a one-line tradeoff summary\n- Recommended positioning: the selected route with pricing, timeline, and rationale\n\n## Examples\n\n**Scenario 1:** \"Should we deprecate our web app now that we have a desktop client?\" → Reframe identifying the web app's unique strength (no install, shareable URL, cross-OS access) leads to a recommendation to keep the web app as the free-tier discovery and onboarding surface, with the desktop client as the paid power-user product.\n\n**Scenario 2:** \"We have two note-taking features in our app — daily log and knowledge base. Should we cut one?\" → Unique value analysis reveals daily log is optimized for speed and recency (quick capture, ephemeral) while knowledge base is optimized for retrieval and permanence. Reframe: they serve different moments in a user's day, not the same job. Recommendation: keep both, but make the entry points contextually distinct.\n\n## Edge Cases\n\n- If the user is certain one product must be cut for financial or resource reasons, skip the reframe and go directly to Step 5 — help them position the remaining product more strongly rather than trying to save what is already decided.\n- If both products genuinely do the same job in the same context with no meaningful differentiation, the binary may not be false — document that finding honestly and recommend consolidation.\n- If the product in question is a third-party integration rather than an owned product, route to `strategic-scout` instead — positioning is only useful for things the team controls.\n\n## Anti-Patterns\n\n- Generating a unique value list made of generic descriptors (\"flexible\", \"powerful\", \"easy to use\") — every item must be tied to a specific context of use where the product outperforms the alternative.\n- Reframing without running new strategic routes — a reframe that does not produce actionable routes is just a restatement of the problem in nicer language.\n- Concluding the session without documenting the before\u002Fafter framing — the reframe is the primary deliverable and must be written down explicitly so it can be referenced later.\n- Treating reframing as a way to avoid hard cuts — if the unique value analysis produces nothing concrete, the honest output is \"this product does not have a defensible niche.\"\n\n## IX. Skill Metadata\n\n**Token Savings:** ~3,000-5,000 tokens per positioning session  \n**Quality Impact:** Transforms binary decisions into strategic opportunities  \n**Maintenance:** Update when new positioning patterns emerge\n\n**When to Update This Skill:**\n- After completing 3-5 positioning sessions (to incorporate new patterns)\n- When a new type of binary trap is discovered\n- When the unlocking question evolves or new variants emerge\n\n---\n\n**Last Updated:** 2026-02-07  \n**Maintained By:** Manus AI  \n**Status:** Active\n","# Product Positioning Scout Skill\n\n**Version:** 1.1  \n**Created:** 2026-02-07  \n**Updated:** 2026-02-07  \n**Author:** Manus AI  \n**Purpose:** To guide the process of reframing a binary product decision into a strategic product positioning opportunity by identifying the unique value of a product or feature.\n\n---\n\n## I. The Philosophy: Beyond the Binary\n\nThe most common trap in product strategy is the binary choice: keep or kill, build or buy, deprecate or maintain. These choices are limiting because they assume the value of a product is fixed. The Product Positioning Scout operates on a different principle: **value is contextual**.\n\nThis skill is about breaking free from the binary trap by asking a more powerful question: **\"What is this uniquely good at?\"** By identifying the unique context in which a product or feature shines, we can transform a \"legacy\" feature into a \"premium\" experience, a \"redundant\" product into a \"complementary\" one.\n\n**The core insight:** The reframe is the prize, not the initial answer.\n\n---\n\n## II. When to Use This Skill\n\n- When facing a decision about whether to keep or deprecate a feature or product\n- When a product or feature seems redundant or is underperforming\n- When planning a multi-surface product strategy (e.g., web, desktop, mobile)\n- At the beginning of a strategic planning cycle\n- Before using `\u002Fstrategic-scout` to ensure the question is properly framed\n\n---\n\n## III. The Workflow\n\nThis is a 5-step workflow for reframing a product decision.\n\n### Step 1: Identify the Binary Trap\n\n**Goal:** Recognize when a strategic question is being framed as a simple, limiting binary choice.\n\n**Actions:**\n- Listen for questions like \"Should we keep X or get rid of it?\"\n- Notice when the conversation is focused on resource allocation rather than strategic value\n- Identify the implicit assumption that the product\u002Ffeature has only one use case\n\n**Output:** A clear articulation of the binary trap\n\n**Example:** \"Should we deprecate the web app now that we're building desktop?\"\n\n---\n\n### Step 2: Introduce the Unlocking Question\n\n**Goal:** Reframe the conversation by asking a question that shatters the binary and opens up new possibilities.\n\n**Actions:**\n- Ask: **\"What is this uniquely good at that the other thing isn't?\"**\n- Shift the focus from \"what to do with this\" to \"what is its unique value?\"\n- Challenge the assumption that products must compete rather than complement\n\n**Output:** A reframed question that opens up new strategic possibilities\n\n**Example:** \"What is the web app uniquely good at that desktop isn't?\" → Discovery, onboarding, cross-platform access without installation\n\n---\n\n### Step 3: Explore the Unique Value\n\n**Goal:** Brainstorm the unique strengths and contexts of the product in question.\n\n**Actions:**\n- List the unique strengths of the product\u002Ffeature\n- Identify the specific contexts (e.g., mobile, on-the-go, deep work) where those strengths are most valuable\n- Consider edge cases and niche use cases that might be surprisingly valuable\n\n**Output:** A comprehensive list of unique value propositions\n\n**Example for web app:**\n- No installation required\n- Cross-platform (works on any OS)\n- Easy to share via URL\n- Great for discovery and onboarding\n- Accessible from any device\n\n---\n\n### Step 4: Re-Scout with the New Lens\n\n**Goal:** Use the new understanding of unique value to re-scout the strategic options.\n\n**Actions:**\n- Use `\u002Fstrategic-scout` with the new framing\n- Explore routes that leverage the unique value (e.g., Mobile-First PWA, Native Companion App)\n- Consider complementary positioning rather than competitive positioning\n\n**Output:** A set of strategic routes that leverage the unique value\n\n**Example routes:**\n- Route 1: Web as discovery, desktop as core product\n- Route 2: Web as free tier, desktop as premium\n- Route 3: Web for onboarding, desktop for power users\n- Route 4: Deprecate web, focus on desktop (original binary)\n\n---\n\n### Step 5: Synthesize and Propose New Positioning\n\n**Goal:** Synthesize the new routes into a coherent product strategy and positioning.\n\n**Actions:**\n- Select the best route (e.g., Hybrid - PWA Now, Native Later)\n- Define the new product positioning (e.g., Desktop for deep work, Mobile for on-the-go orchestration)\n- Propose a new timeline and pricing model\n- Document the strategic rationale\n\n**Output:** A complete product positioning strategy\n\n**Example:** \"Desktop as core ($20\u002Fmonth), Mobile PWA as premium tier (separate subscription, 4-6 weeks after desktop v1)\"\n\n---\n\n## IV. Best Practices\n\n### 1. The Reframe is Everything\n\n**Why:** The most powerful strategic moves come from reframing the question, not from choosing between existing options.\n\n**How:** Always start by questioning the framing of the decision. Is it really a binary choice?\n\n---\n\n### 2. Value is Contextual\n\n**Why:** A product's value is not inherent; it's determined by the context in which it's used.\n\n**How:** For every product\u002Ffeature, ask \"In what context is this uniquely valuable?\"\n\n---\n\n### 3. Complement, Don't Compete\n\n**Why:** The best multi-surface strategies create complementary experiences, not competing ones.\n\n**How:** Frame each surface by its unique job-to-be-done, not by its feature list.\n\n---\n\n### 4. The Unlocking Question is Universal\n\n**Why:** \"What is this uniquely good at?\" works for products, features, surfaces, and even people.\n\n**How:** Use this question whenever you're facing a binary decision about value.\n\n---\n\n### 5. Document the Reframe\n\n**Why:** The reframe is the most valuable artifact. It changes how everyone thinks about the product.\n\n**How:** Write down the before\u002Fafter framing explicitly. Share it widely.\n\n---\n\n## V. Quality Checklist\n\nBefore delivering the new strategy, ensure you can answer \"yes\" to all of the following questions:\n\n- [ ] Have you identified and articulated the initial binary trap?\n- [ ] Have you asked the \"Unlocking Question\" to reframe the conversation?\n- [ ] Have you clearly defined the unique value and context of the product\u002Ffeature?\n- [ ] Have you used `\u002Fstrategic-scout` to explore new routes based on the new framing?\n- [ ] Have you proposed a new, coherent product positioning, timeline, and business model?\n- [ ] Have you documented the strategic rationale for the new positioning?\n\n---\n\n## VI. Example: Dojo Genesis Web App Positioning\n\n**The Binary Trap:** \"Should we deprecate the web app now that we're building desktop?\"\n\n**The Unlocking Question:** \"What is the web app uniquely good at that desktop isn't?\"\n\n**The Unique Value:**\n- No installation required\n- Cross-platform access\n- Easy to share via URL\n- Great for discovery and onboarding\n- Accessible from any device\n\n**The Re-Scout:** Used `\u002Fstrategic-scout` to explore 4 routes:\n1. Deprecate web, focus on desktop\n2. Web as companion (lightweight version)\n3. Web as discovery\u002Fonboarding, desktop as core\n4. Hybrid - PWA now, native later\n\n**The New Positioning:**\n- **Desktop:** Core product for deep work ($20\u002Fmonth)\n- **Mobile PWA:** Premium tier for on-the-go orchestration (separate subscription, 4-6 weeks after desktop v1)\n- **Web:** Free tier for discovery and onboarding\n\n**The Outcome:** Transformed a deprecation decision into a multi-surface strategy where each surface has a unique, complementary role.\n\n**Key Insight:** The web app wasn't redundant—it was uniquely good at discovery and onboarding. Desktop is uniquely good at deep work. Mobile is uniquely good at on-the-go orchestration.\n\n---\n\n## VII. Common Pitfalls to Avoid\n\n### Pitfall 1: Accepting the Binary Without Question\n\n**Problem:** Most binary choices are false binaries. Accepting them limits strategic options.\n\n**Solution:** Always question the framing. Ask \"Is this really a binary choice?\"\n\n---\n\n### Pitfall 2: Focusing on Features Instead of Context\n\n**Problem:** Comparing feature lists leads to \"X is redundant because Y has all its features.\"\n\n**Solution:** Focus on context of use, not feature parity. Ask \"What is this uniquely good at?\"\n\n---\n\n### Pitfall 3: Competitive Positioning by Default\n\n**Problem:** Assuming products must compete rather than complement.\n\n**Solution:** Explore complementary positioning first. Competition should be a last resort.\n\n---\n\n### Pitfall 4: Skipping the Re-Scout\n\n**Problem:** Reframing the question but not exploring new routes based on the reframe.\n\n**Solution:** Always use `\u002Fstrategic-scout` after reframing to explore new possibilities.\n\n---\n\n### Pitfall 5: Not Documenting the Reframe\n\n**Problem:** The reframe gets lost in conversation. People revert to the binary.\n\n**Solution:** Write down the before\u002Fafter framing explicitly. Make it a reference document.\n\n---\n\n## VIII. Related Skills\n\n- **`strategic-scout`** - Use this after reframing to explore new routes\n- **`iterative-scouting`** - Use this to refine the positioning based on feedback\n- **`multi-surface-strategy`** - Use this to design the complete multi-surface strategy\n- **`release-specification`** - Use this to write specs for the new positioning\n- **`strategic-to-tactical-workflow`** - Use this to move from positioning to implementation\n\n---\n\n## Output\n\n- Before\u002Fafter framing document: the original binary question stated explicitly, then the reframed question and its implications\n- Unique value list: 3-7 specific strengths of the product tied to concrete usage contexts, not generic adjectives\n- Strategic routes: 3-5 routes that capitalize on the reframe, each with a one-line tradeoff summary\n- Recommended positioning: the selected route with pricing, timeline, and rationale\n\n## Examples\n\n**Scenario 1:** \"Should we deprecate our web app now that we have a desktop client?\" → Reframe identifying the web app's unique strength (no install, shareable URL, cross-OS access) leads to a recommendation to keep the web app as the free-tier discovery and onboarding surface, with the desktop client as the paid power-user product.\n\n**Scenario 2:** \"We have two note-taking features in our app — daily log and knowledge base. Should we cut one?\" → Unique value analysis reveals daily log is optimized for speed and recency (quick capture, ephemeral) while knowledge base is optimized for retrieval and permanence. Reframe: they serve different moments in a user's day, not the same job. Recommendation: keep both, but make the entry points contextually distinct.\n\n## Edge Cases\n\n- If the user is certain one product must be cut for financial or resource reasons, skip the reframe and go directly to Step 5 — help them position the remaining product more strongly rather than trying to save what is already decided.\n- If both products genuinely do the same job in the same context with no meaningful differentiation, the binary may not be false — document that finding honestly and recommend consolidation.\n- If the product in question is a third-party integration rather than an owned product, route to `strategic-scout` instead — positioning is only useful for things the team controls.\n\n## Anti-Patterns\n\n- Generating a unique value list made of generic descriptors (\"flexible\", \"powerful\", \"easy to use\") — every item must be tied to a specific context of use where the product outperforms the alternative.\n- Reframing without running new strategic routes — a reframe that does not produce actionable routes is just a restatement of the problem in nicer language.\n- Concluding the session without documenting the before\u002Fafter framing — the reframe is the primary deliverable and must be written down explicitly so it can be referenced later.\n- Treating reframing as a way to avoid hard cuts — if the unique value analysis produces nothing concrete, the honest output is \"this product does not have a defensible niche.\"\n\n## IX. Skill Metadata\n\n**Token Savings:** ~3,000-5,000 tokens per positioning session  \n**Quality Impact:** Transforms binary decisions into strategic opportunities  \n**Maintenance:** Update when new positioning patterns emerge\n\n**When to Update This Skill:**\n- After completing 3-5 positioning sessions (to incorporate new patterns)\n- When a new type of binary trap is discovered\n- When the unlocking question evolves or new variants emerge\n\n---\n\n**Last Updated:** 2026-02-07  \n**Maintained By:** Manus AI  \n**Status:** Active\n",{"name":5,"tier":54,"model":36,"agents":55,"inputs":57,"outputs":63,"category":69,"triggers":70,"description":7,"tool_dependencies":75},1,[56],"primary",[58],{"name":59,"type":60,"required":61,"description":62},"product_tension","string",true,"The keep-or-kill decision or overlap tension to resolve through positioning",[64],{"name":65,"type":66,"format":67,"description":68},"positioning_document","ref","cas-ref","Reframed product positioning with before\u002Fafter statement and strategic routes leveraging the complementary role","strategic-thinking",[71,72,73,74],"should we deprecate X now that we have Y","this feature feels redundant","we cannot decide whether to keep this product","two things in our portfolio seem to overlap",[76],"file_system","main","ff07df5fd8f75762c2a131e6e26d297e8ae403ee","plugins\u002Fstrategic-thinking\u002Fskills\u002Fproduct-positioning",0,"https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway","https:\u002F\u002Fgithub.com\u002FDojoGenesis","dojogenesis.com","2026-10-25 22:59:58",{"source":8,"skillName":5,"commands":86,"prompt":96,"zipAvailable":61},[87,90,93],{"tool":88,"command":89},"npx","npx skills add DojoGenesis\u002Fgateway --skill product-positioning",{"tool":91,"command":92},"bunx","bunx skills add DojoGenesis\u002Fgateway --skill product-positioning",{"tool":94,"command":95},"pnpm","pnpm dlx skills add DojoGenesis\u002Fgateway --skill product-positioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fstrategic-thinking\u002Fskills\u002Fproduct-positioning\u002FSKILL.md",[],[99,118,129,137,176,200],{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":107,"publishedAt":49},"01M6P6J0WYSD1MTGA3ZX6MGGZ5","kata-test-echo","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-test-echo\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[108,109,110,111,112,113,114,115,116,117],"kata test echo","Echo","test","json","v1","output","input","structured","contracts","schema",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":49},"01M6P6HQJNGG4WPZW0DEWMAY2N","kata-plain","An ordinary prose skill; not dispatchable.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-plain\u002FSKILL.md",[124],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[126,127,128],"kata plain","prose skill","prose",{"skillNo":130,"name":131,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":49},"01M6P6HH6Y7K8K6606MF7VZ1HB","kata-broken","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-broken\u002FSKILL.md",[],[135,136,115,116,109,117,111,110,114,112,113],"kata broken","broken",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":155,"publishedAt":49},"01M6P6GW520QJ03A6K7Y5PWJ52","voice-before-structure","Read the project's design language and philosophy before writing structural artifacts. Ground manifests, READMEs, and descriptions in the project's voice, not boilerplate. Use when creating manifests or READMEs for established projects, writing ecosystem-level documentation, building plugin descriptions or marketplace metadata, or authoring metadata that carries a project's identity. Trigger phrases: 'write the manifest', 'create a README', 'describe this plugin', 'ground yourself in the philosophy', 'ecosystem-level work'.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fvoice-before-structure\u002FSKILL.md",[143,146,149,152],{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":150,"categoryName":151,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":153,"categoryName":154,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"voice before structure","structure","voice","manifests","ecosystem","false","authoring","structural","project","artifact","philosophy","design","writing","identity","documentation","create","projects","work","read","write",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":49},"01M6P6GMNA4HJ4D5RRM3BQZ73M","system-prompt-archaeology","Produces a named ADA disposition preset (YAML) and a layered behavioral analysis (structural decomposition + evidence-cited classifications) from a system prompt. Use when: \"analyze this system prompt\", \"extract disposition from prompt\", \"reverse-engineer agent behavior\", \"what patterns does this prompt use\", \"build a preset from this prompt\".","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsystem-prompt-archaeology\u002FSKILL.md",[182],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[184,185,186,47,187,188,163,189,190,191,192,193,194,195,196,197,39,198,35,199],"system prompt archaeology","system prompt","prompt","behavioral","classify","decomposition","wisdom","patterns","engineer","decompose","evidence","ada","analyze","analysis","sonnet","reverse",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"publishedAt":49},"01M6P6G2D70T9R00HX6K154X5Y","session-lifecycle-automation","Designs and configures all three loops of solo-operator session automation — session bookends, background maintenance agents, and a delegation flywheel. Use when setting up a new workspace, recovering from the 44% zero-artifact session leak, or preparing to scale delegation across multiple concurrent agents.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsession-lifecycle-automation\u002FSKILL.md",[206],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[208,209,210,211,212,213,214,215,216,217,218,48,219,165,220,221,222,223,224,225],"automation","session lifecycle automation","session lifecycle","lifecycle","session","markdown","configure","directory","config","delegation","audit","files","solo","across","scheduled","loops","up","template"]