[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D6APVYF5WT4M96JSBCHS5P":3,"skill-same:01M6D6APVYF5WT4M96JSBCHS5P":70},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6D6APVYF5WT4M96JSBCHS5P","positioning",null,"Orchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-research\u002Fclaude\u002Fpositioning\u002Farchive\u002Fv0.23\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37],"research","product","orchestrator","v0","Market","frameworks","synthesize","focus","visual","2026-11-10 10:12:30",false,"---\nname: positioning\ndescription: Orchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning\ntype: research\nversion: v0.23\nargument-hint: \"[optional: \\\"product\\\" | \\\"--synthesize\\\" | focus area]\"\ncontext_intake: scoped\nvisual_tier: visual\ninvocation: orchestrator\n---\n\n## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell, instead of the target skill. After install, tell Claude users to run `\u002Freload-skills`, then `\u002Fclear` or restart if the skill remains invisible. Only the currently running skill and skills verified available in the active session or project-local install state are directly recommendable. For unavailable pack skills, recommend `npx skillpacks install \u003Cpack-or-skill>`; for unavailable base skills, recommend `npx skillpacks init` before the skill.\n\n# Positioning — Orchestrator\n\nThis is an **orchestrator skill** using the parent router delegation pattern (see `docs\u002Forchestrator-convention.md`). It detects context, recommends applicable positioning frameworks, and synthesizes their outputs. Individual frameworks live as child skills under `frameworks\u002F`.\n\n## Report-First Approval Gate\n\nDefault to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.\n\nDo not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.\n\nAfter approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.\n\nDo not include downstream or cross-skill command recommendations while a scope, framework findings, or synthesis approval is pending. The approval request itself is the next action, and the only terminal command section allowed before approval is `## Recommended Next Command After Compiling YAML` and it must name this same parent orchestrator, such as `\u002Fpositioning` plus the same product\u002Fresearch path argument when present. Parent-loop continuation is not downstream routing. Only emit downstream next-skill routing after the synthesized `positioning.md` artifact has been approved and written.\n\n## Staged Research Workflow\n\nUse this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.\n\n1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions\u002Fconfidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled YAML approval of the research scope. Do not perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.\n2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, perform the synthesized research, run required source\u002Fcode checks, and write only a non-canonical working packet: flat mode uses `research\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`; product-path mode uses `research\u002F{slug}\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`. Replace `\u003Cskill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `\u003Cpre>\u003Ccode>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions\u002Fconfidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.\n3. **Stage 3 - Finalize approved artifacts.** Consume final compiled YAML for artifact approval only when it has no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths below, and convert the alignment page to `confirmed` with the approval record preserved.\n\nCanonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.\n\n## Evidence And Feedback Handling\n\nTreat user feedback as input to evaluate, not as automatic ground truth.\n\n- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.\n- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.\n- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.\n- When uncertain, say what is known, what is inferred, and what would change the conclusion.\n\n## Prerequisites\n\n- **Hard**: `research\u002Ficp.md` (or `research\u002F{slug}\u002Ficp.md`) must exist. If not, tell the user to run `\u002Fcustomer-discovery` first and stop.\n- **Hard**: `research\u002Fcompetitive-analysis.md` (or `research\u002F{slug}\u002Fcompetitive-analysis.md`) must exist. If not, tell the user to run `\u002Fcompetitive-analysis` first and stop.\n- **Strong default**: `research\u002Fjourney-map.md` (or `research\u002F{slug}\u002Fjourney-map.md`) should exist before writing canonical positioning. If missing, recommend `\u002Fjourney-map` first unless the user explicitly needs a provisional positioning analysis.\n- **Soft**: Read these if they exist:\n  - `research\u002Fjourney-map.md` — where value is delivered, the aha moment\n  - `research\u002Fcustomer-feedback.md` — real customer language about what makes the product different\n  - `research\u002Fmonetization.md` — pricing context for value perception\n\n## Execution Model — Research Session Loop\n\nThis is a **self-advancing Pattern A research orchestrator** (see `docs\u002Fresearch-session-loop-convention.md`). Each invocation starts cold, resolves its state from **pasted YAML + filesystem**, runs **exactly one heavy phase**, emits the next gate, and stops. The user advances the loop by clearing context and re-invoking `\u002Fpositioning`. The user never invokes a framework subskill directly — the orchestrator follows each selected framework's subskill inline.\n\nWhen a framework is pending, the only user-facing continuation route is re-invoking `\u002Fpositioning` with the same product\u002Fresearch path argument when present, for example `\u002Fpositioning research\u002Fafps-tracker`. Never tell the user to run a path-shaped child framework command; the parent resolves the pending framework from the run manifest and filesystem.\n\n\n### Terminal Handoff Contract\n\nEvery terminal response for this Research Session Loop must end with `## Next Work` and one command section. Use `## Recommended Next Command After Compiling YAML` only while a `review` page is waiting for compiled YAML. Use `## Recommended Next Command` only after approved YAML has been consumed and the approved artifact has been written or updated. Do not put any other section after the applicable command section.\n\n### Self-Routing Continuation Payload\n\nEvery `review` alignment page this parent creates must include `agent_routing` in the bottom compiled YAML. The mapping routes a fresh agent back to this parent orchestrator; it does not authorize direct framework invocation or replace parent-owned state resolution. Use this shape, preserving the current product\u002Fresearch path argument when present:\n\n```yaml\nagent_routing:\n  workflow: pattern-a-research-loop\n  parent_skill: positioning\n  command: \"\u002Fpositioning research\u002F{slug}\"\n  product_path: research\u002F{slug}        # omit in flat mode\n  gate_owner: parent-orchestrator\n  gate_type: framework-findings        # or framework-selection, shortcut-selection, synthesis\n  framework_slug: \u003Cframework-slug>     # only for framework-findings gates\n  framework_mode: inline-subskill      # only for framework-findings gates\n  run_manifest: research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml\n  next_resolution: parent-resolves-from-yaml-and-filesystem\n```\n\nFor framework selection, shortcut, and synthesis gates, omit `framework_slug` and `framework_mode`; `gate_type` must name the actual gate. The `command` field must be the same parent command shown under `## Recommended Next Command After Compiling YAML`. The parent consumes the YAML, writes or amends the artifact, archives consumed sources, derives progress from the run manifest plus canonical-intermediate files, and decides whether to load a framework subskill inline.\n\nFor review-pending framework, selection, shortcut, or synthesis pages, `## Next Work` tells the user to review the alignment page and compile YAML, and the command section names `\u002Fpositioning` with the same product\u002Fresearch path argument when present, then clear context before continuing. For post-write pending-framework states, `## Next Work` reports progress as \"k of N frameworks complete\" and says the next run executes the next pending framework; `## Recommended Next Command` names `\u002Fpositioning`.\n\nAfter every framework write, recalculate pending frameworks from the run manifest and canonical-intermediate files before writing this handoff. If no selected frameworks remain and canonical `positioning.md` is missing, `## Next Work` says the next run builds the unified synthesis review page, and `## Recommended Next Command` names `\u002Fpositioning --synthesize` with the same product\u002Fresearch path argument when present. After approved synthesis writes canonical `positioning.md`, the final command section names only the first downstream command selected by the Next Steps decision tree.\n\n\nState lives in two places only:\n\n- **Run manifest** — `research\u002F_working\u002Fpositioning-run.yaml` (flat) or `research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml` (product-path). Records the selected framework set and each framework's intermediate path. Written when the multi-select YAML is approved. Shape:\n\n  ```yaml\n  orchestrator: positioning\n  slug: skills-showcase            # omit in flat mode\n  selected_frameworks:\n    - slug: jtbd-positioning\n      intermediate: research\u002Fskills-showcase\u002Fpositioning-jtbd-positioning.md\n    - slug: strategic-canvas\n      intermediate: research\u002Fskills-showcase\u002Fpositioning-strategic-canvas.md\n  ```\n\n- **Canonical-intermediate existence** — a selected framework is *done* when `research\u002Fpositioning-{framework}.md` (or `research\u002F{slug}\u002Fpositioning-{framework}.md`) exists, *pending* otherwise. `pending = selected − existing-intermediates`. The manifest stores selection only, not per-framework status.\n\n`research\u002F.progress.yaml` stays coarse — its `pipeline_stage` is a pointer, not per-framework status.\n\n### State resolution (resolve the first match; YAML first, then most-progressed A→E)\n\nOn each invocation, after Product-Path Scope Resolution (step 0), resolve state:\n\n| State | Detected when | Heavy phase this session | Emits \u002F stops with |\n|---|---|---|---|\n| **0 — pasted YAML** | a compiled alignment YAML is pasted | branch on `approval_status`: `ready-for-agent-review` → apply the approval for the gate it answers (light: write manifest and\u002For prior framework intermediate, archive consumed source), then fall through to the next pending state below; `not-approved` → amend the named page (refinement session) and stop | amended page, or proceeds ↓ |\n| **A — done** | canonical `research\u002Fpositioning.md` (or `research\u002F{slug}\u002Fpositioning.md`) exists | — | done; emit next-skill route (step 6) |\n| **B — synthesize** | run manifest exists, all selected intermediates exist, no canonical `positioning.md` (also forced by `--synthesize`) | **synthesis** (step 4) | synthesis `review` page |\n| **C — run framework** | run manifest exists, ≥1 selected framework pending | **run next pending framework inline at its research stage** (step 3b) | that framework's findings `review` page |\n| **E — build selection** | no run manifest and no canonical (cold start) | mode detect → load context → recommend frameworks → build multi-select page (steps 1–3a) | multi-select `review` page |\n\n**Cold entry (no state F).** This orchestrator uses `context_intake: scoped` — there is **no deep-interview phase**. A cold start (nothing on disk, after the hard `research\u002Ficp.md` + `research\u002Fcompetitive-analysis.md` prerequisites are satisfied) resolves directly to **state E**; the 1–3 light scope questions in Context Gathering fold into the head of the E session. The `product`\u002F`post-launch`\u002F`obviously-awesome` shortcut short-circuits E→C with a fixed framework set (step 5).\n\n**Light vs heavy.** Recording the approved selection into the run manifest (state 0→C head), writing an already-reviewed framework intermediate, and archiving a consumed source are *light* — they fold into the head of the next heavy session. The heavy phase (one framework's research, synthesis) is the only thing isolated per session.\n\n**Shortcuts.** `\u002Fpositioning --synthesize` forces state B. `\u002Fpositioning product` (also `post-launch`, `obviously-awesome`) is the product-positioning shortcut (step 5): after the user approves the shortcut plan, it writes a fixed single-framework set (`obviously-awesome`) into the run manifest and enters state C. Do not queue framework work in `tasks\u002Ftodo.md` or hand it to `\u002Fexec`.\n\n---\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n### 1. Mode Detection\n\nDetect **market-positioning mode** (default) or **product-positioning mode**:\n\n**Market-positioning mode** activates when:\n- No `research\u002Fcustomer-feedback.md` with post-launch customer evidence, AND\n- No production codebase with live users detected, AND\n- `$ARGUMENTS` does not contain \"product\", \"post-launch\", or \"obviously-awesome\"\n\nAvailable frameworks in market mode:\n- `jtbd-positioning` — Jobs-to-be-Done positioning analysis\n- `strategic-canvas` — Blue Ocean strategic canvas (eliminate\u002Freduce\u002Fraise\u002Fcreate)\n- `moore-positioning` — Geoffrey Moore positioning hypothesis\n- `category-design` — Play Bigger category creation\n\n**Product-positioning mode** activates when:\n- `research\u002Fcustomer-feedback.md` exists with real customer data, OR\n- `$ARGUMENTS` contains \"product\", \"post-launch\", or \"obviously-awesome\", OR\n- Production spec exists AND customer feedback references real users\n\nAvailable frameworks in product mode:\n- `obviously-awesome` — April Dunford (requires real customer evidence)\n- `strategic-canvas` — optionally, for category refresh\n\n### 2. Load Context\n\n- Read `research\u002Ficp.md` — ICP segments, pain points, value props, trigger events\n- Read `research\u002Fcompetitive-analysis.md` — competitor landscape, gaps\n- Read `research\u002Fjourney-map.md` if it exists — aha moment, value delivery\n- Read `research\u002Fcustomer-feedback.md` if it exists — real language, satisfaction drivers\n- Read CLAUDE.md, README for product context\n- Read any existing `research\u002Fpositioning-*.md` intermediate artifacts (from prior runs)\n\n### 3a. State E — Framework Selection & Build Multi-Select Page\n\nBuild the framework multi-select `review` alignment page with:\n\n1. **Mode explanation**: which mode was detected and why (evidence for detection)\n2. **Available evidence summary**: what research exists and what's missing\n3. **Multi-select framework section**: checkboxes for each available framework with:\n   - Framework name and one-line description\n   - Why it's recommended or optional for this context\n   - Pre-checked defaults based on available evidence:\n     - Market mode defaults: `jtbd-positioning` + `strategic-canvas` + `moore-positioning` pre-checked; `category-design` unchecked (recommended only when strategic canvas shows no existing category fits)\n     - Product mode defaults: `obviously-awesome` pre-checked; `strategic-canvas` unchecked (optional refresh)\n4. **Loop plan explanation**: the selected set is the scope-and-candidate approval gate; each selected framework will then be run inline (one findings page per framework) and the run advances by re-invoking `\u002Fpositioning`\n5. **Approval gate**: framework selection confirmation\n\nThis multi-select approval **is** the Stage-1 scope approval for the whole selected set. Stop for compiled YAML. Do **not** write the run manifest or run any framework in this session — that is state C.\n\n### 3b. State C — Run Next Pending Framework (inline)\n\nThis session consumes the approved multi-select YAML (state 0→C) or advances after a prior framework's approval. At the **head** of the session, do the light bookkeeping first:\n\n1. **Write the run manifest** if it does not yet exist: `research\u002F_working\u002Fpositioning-run.yaml` (flat) or `research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml` (product-path), recording `selected_frameworks` with each framework's `slug` and canonical `intermediate` path. Include only frameworks the user selected. Example (market mode):\n\n   ```yaml\n   orchestrator: positioning\n   selected_frameworks:\n     - slug: jtbd-positioning\n       intermediate: research\u002Fpositioning-jtbd-positioning.md\n     - slug: strategic-canvas\n       intermediate: research\u002Fpositioning-strategic-canvas.md\n     - slug: moore-positioning\n       intermediate: research\u002Fpositioning-moore-positioning.md\n   ```\n\n2. **If a prior framework's reviewed content was just approved** by the pasted YAML, write its canonical intermediate `research\u002Fpositioning-{fw}.md` (or `research\u002F{slug}\u002Fpositioning-{fw}.md`) from the already-reviewed working packet, and archive that framework's working packet and superseded review page.\n\nThen run the **one heavy phase** for this session:\n\n3. **Determine the next pending framework** = the first framework in `selected_frameworks` whose canonical intermediate does not yet exist.\n4. **Load and follow that framework subskill's `SKILL.md` inline**, entering at its **research stage (Stage 2)**: the multi-select approval already satisfied the framework's Stage-1 scope gate, so perform the framework's research, write its working packet, and build a single findings `review` page for that framework. Stop for that framework's compiled YAML.\n\n**Advance the loop by self-re-invocation.** When a framework findings page is in `review`, end the terminal message with `## Next Work` telling the user to review the page and compile YAML, followed by `## Recommended Next Command After Compiling YAML` naming `\u002Fpositioning` with the same product\u002Fresearch path argument when present. After a framework's compiled YAML is approved and its canonical intermediate is written, recalculate pending frameworks from the manifest and filesystem before writing the handoff. If pending frameworks remain, end with `## Next Work` reporting progress as \"k of N frameworks complete\" and saying the next run executes the next pending framework, followed by `## Recommended Next Command` naming `\u002Fpositioning`. If no pending frameworks remain and canonical `positioning.md` is missing, end with `## Next Work` saying the next run builds the unified synthesis review page, followed by `## Recommended Next Command` naming `\u002Fpositioning --synthesize` with the same product\u002Fresearch path argument when present. Do not emit cross-skill routing here — that happens only after synthesis.\n\n\n### 4. State B — Synthesis (auto-detected; also `\u002Fpositioning --synthesize`)\n\nEnter synthesis when the run manifest exists, **all** selected framework intermediates exist, and no canonical `research\u002Fpositioning.md` yet exists. An explicit `\u002Fpositioning --synthesize` also forces this state. Read all selected intermediate framework outputs (the `intermediate` paths recorded in the run manifest), e.g.:\n- `research\u002Fpositioning-jtbd-positioning.md`\n- `research\u002Fpositioning-strategic-canvas.md`\n- `research\u002Fpositioning-moore-positioning.md`\n- `research\u002Fpositioning-category-design.md`\n- `research\u002Fpositioning-obviously-awesome.md`\n\nAt least one must exist. If none exist, tell user to run framework selection first.\n\nSynthesize into unified `research\u002Fpositioning.md`:\n\n**Market-positioning synthesis includes:**\n- Combined positioning hypothesis drawing from all framework outputs\n- Moore template filled with evidence from JTBD + Canvas + Category analysis\n- Evidence matrix: each claim mapped to which framework(s) support it\n- Confidence levels per claim (strong\u002Fmoderate\u002Fhypothesized)\n- Validation plan: what needs testing before the position is canonical\n- Mode header: `> Mode: Market Positioning (hypothesized, pre-product)`\n\n**Product-positioning synthesis includes:**\n- Positioning statement (Obviously Awesome output)\n- Evidence matrix grounded in customer feedback\n- Confidence levels (most should be \"strong\" — backed by customer data)\n- Mode header: `> Mode: Product Positioning (customer-grounded)`\n\nBuild alignment page for synthesis approval with:\n- Full proposed `research\u002Fpositioning.md` content\n- Evidence matrix combining all framework sources\n- Confidence\u002Fassumption register\n- Proposed file changes gate\n- Approval gate\n\nAfter approval: write `research\u002Fpositioning.md`, then on this canonical write **archive the run manifest** (`positioning-run.yaml`) and the synthesis working packet under `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-working-path>`, update `research\u002F.progress.yaml` `pipeline_stage` to `positioning`, and emit the downstream next-step routing (step 6). This is the one place cross-orchestrator routing is allowed.\n\n### 5. State C via Product-Positioning Shortcut (`\u002Fpositioning product`)\n\nSkip multi-select. Build an alignment page for the shortcut execution plan with:\n\n1. **Shortcut explanation**: product-positioning shortcut selected and why `obviously-awesome` is the only queued framework\n2. **Evidence readiness**: customer-feedback requirement and any missing evidence caveats\n3. **Proposed loop plan**: the single `obviously-awesome` framework that will be recorded in the run manifest\n4. **Approval gate**: require final compiled YAML approval before writing the run manifest\n\nDo not write the run manifest before alignment approval. The next action is review of the HTML alignment page.\n\nAfter user approval via final compiled YAML, write this selected set to the run manifest and enter the next pending framework session:\n\n```yaml\norchestrator: positioning\nselected_frameworks:\n  - slug: obviously-awesome\n    intermediate: research\u002Fpositioning-obviously-awesome.md\n```\n\nThen enter **state C** and run `obviously-awesome` inline per step 3b. The loop advances by re-invoking `\u002Fpositioning`.\n\n### 6. Next Steps (after synthesis only)\n\nInclude 3–5 applicable items with \"Recommended + Other options\" framing:\n\n- IF no `research\u002Fjourney-map.md`: check for `customer-lifecycle` pack → recommend `\u002Fjourney-map`\n- DEFAULT: check `.agents\u002Fproject.json.enabled_packs` for `product-design` — if not enabled, recommend `npx skillpacks install product-design` from the project shell; if enabled, recommend `\u002Fuser-flow-map [positioning-backed product direction]`\n- IF solution-customer fit is weak\u002Fdisputed: `\u002Fvalue-prop-canvas`\n- IF revenue\u002Fchannels\u002Fcost\u002Fdefensibility risks exposed: `\u002Flean-canvas`\n- IF no `research\u002Fgtm.md`: check for `business-growth` pack → recommend `\u002Fgtm`\n- IF `research\u002Fgtm.md` exists: recommend `\u002Fgtm` refresh\n- IF no `research\u002Fmonetization.md`: check for `business-growth` pack → recommend `\u002Fmonetization`\n- IF codebase exists: check for `business-ops` pack → recommend `\u002Fmvp-gap`\n\n### 7. Downstream Impact Check (after synthesis write)\n\nCheck for downstream research documents that may be affected:\n- `research\u002Fgtm.md`\n\nClassify impact as None\u002FMinor\u002FMajor per standard pattern.\n\n## Optional Research Trigger Map\n\nThese detours are conditional framework owners, not required AFPS chain links. Apply after synthesis.\n\n| Positioning signal | Owner | Trigger threshold |\n|---|---|---|\n| Solution-customer fit weak\u002Fdisputed, value mapping low confidence | `\u002Fvalue-prop-canvas` | Trigger: unique attributes can't be confidently mapped to value. Skip: value mapping clear even if hypothesized. |\n| Business-model risk (revenue\u002Fchannels\u002Fcost\u002Fdefensibility) exposed by category strategy | `\u002Flean-canvas` | Trigger: risk would change UX or prototype choices. Skip: normal competitive findings. |\n| Pricing architecture central to positioning (premium vs value changes direction) | `\u002Fmonetization` | Trigger: category\u002Fvalue mapping requires grounded pricing. Skip: pricing not a differentiator. |\n\n## Output\n\n### State E \u002F State C output: run manifest plus per-framework findings review page\n\nThe state-E multi-select page; then, per state-C session, the run manifest `research\u002F_working\u002Fpositioning-run.yaml` (or `research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml`, written at the head of the first state-C session) plus the next pending framework's findings review page. One findings page per selected framework; the canonical intermediate `research\u002Fpositioning-{framework}.md` is written on that framework's approval.\n\n### State B output (synthesis): `research\u002Fpositioning.md` (or `research\u002F{slug}\u002Fpositioning.md`)\n\n```markdown\n# Positioning\n\n> Based on: [list of framework outputs used]\n> Date: [current date]\n> Mode: Market Positioning (hypothesized, pre-product) | Product Positioning (customer-grounded)\n> Frameworks applied: [list]\n\n## Positioning Statement\n\n**For** [target segment]\n**who** [key pain \u002F trigger event]\n**[product name] is a** [market category]\n**that** [key value \u002F unique benefit]\n**Unlike** [primary competitive alternative]\n**[product name]** [key differentiator]\n\n## Summary\n[2-3 sentences: the positioning thesis]\n\n## Evidence Matrix\n\n| Claim | Supporting Framework(s) | Evidence | Confidence | Assumption Status |\n|-------|------------------------|----------|------------|-------------------|\n| [claim] | JTBD \u002F Canvas \u002F Moore \u002F Category \u002F OA | [source] | Strong \u002F Moderate \u002F Hypothesized | Validated \u002F Needs testing |\n\n## Framework Synthesis\n\n### From JTBD Analysis\n[Key findings — primary job, outcome positioning]\n\n### From Strategic Canvas\n[Key findings — eliminate\u002Freduce\u002Fraise\u002Fcreate moves, competitive gaps]\n\n### From Moore Hypothesis\n[Key findings — positioning template, evidence gaps]\n\n### From Category Design\n[Key findings — category diagnosis, POV if new category]\n\n### From Obviously Awesome\n[Key findings — if product mode]\n\n## Target Segment\n[Best-fit segment with evidence from multiple frameworks]\n\n## Market Category\n[Chosen category with evidence from multiple frameworks]\n\n## Confidence Register\n\n| Element | Confidence | Evidence Source | What Would Change It |\n|---------|-----------|----------------|---------------------|\n| [element] | [level] | [source] | [condition] |\n\n## Validation Plan (market mode only)\n[What needs testing before this position is canonical]\n\n## Positioning Implications\n\n### For Messaging\n### For Product\n### For Sales\n### For Pricing\n\n## Downstream Impact\n[Standard pattern]\n\n## Next Steps\n[Standard routing]\n```\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`.\n- One-time condition-gated records go in `tasks\u002Frecord-todo.md`.\n- Cadence-based reviews go in `tasks\u002Frecurring-todo.md`.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless promoted.\n\n## Constraints\n\n- **Requires ICP + competitive analysis.** Positioning without knowing the customer and the competition is guesswork.\n- **Customer-grounded.** Every positioning decision must connect to real customer behavior or research evidence.\n- **Mode detection is evidence-based.** Do not override mode detection without user confirmation.\n- **Parent owns the research loop.** It records selected frameworks in the run manifest and runs one pending framework inline per invocation. Do not queue framework work in `tasks\u002Ftodo.md` or hand it to `\u002Fexec`.\n- **Synthesis requires at least one framework output.** Do not synthesize from zero evidence.\n- **Do not overwrite existing `research\u002Fpositioning.md`** without asking the user first.\n\n## Context Gathering\n\n**Step 1 — Scope questions.** Before researching, ask the user 1–3 questions via `AskUserQuestion` to understand: their product\u002Fservice, target audience, and what they hope to learn or decide from this research.\n\n**Step 2 — Research.** Conduct research scoped by the user's answers.\n\n**Step 3 — Findings validation.** Before building the alignment page, present the 3–5 most important findings and ask the user to validate or correct any critical assumptions.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fpositioning-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell, instead of the target skill. After install, tell Claude users to run `\u002Freload-skills`, then `\u002Fclear` or restart if the skill remains invisible. Only the currently running skill and skills verified available in the active session or project-local install state are directly recommendable. For unavailable pack skills, recommend `npx skillpacks install \u003Cpack-or-skill>`; for unavailable base skills, recommend `npx skillpacks init` before the skill.\n\n# Positioning — Orchestrator\n\nThis is an **orchestrator skill** using the parent router delegation pattern (see `docs\u002Forchestrator-convention.md`). It detects context, recommends applicable positioning frameworks, and synthesizes their outputs. Individual frameworks live as child skills under `frameworks\u002F`.\n\n## Report-First Approval Gate\n\nDefault to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.\n\nDo not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.\n\nAfter approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.\n\nDo not include downstream or cross-skill command recommendations while a scope, framework findings, or synthesis approval is pending. The approval request itself is the next action, and the only terminal command section allowed before approval is `## Recommended Next Command After Compiling YAML` and it must name this same parent orchestrator, such as `\u002Fpositioning` plus the same product\u002Fresearch path argument when present. Parent-loop continuation is not downstream routing. Only emit downstream next-skill routing after the synthesized `positioning.md` artifact has been approved and written.\n\n## Staged Research Workflow\n\nUse this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.\n\n1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions\u002Fconfidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled YAML approval of the research scope. Do not perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.\n2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, perform the synthesized research, run required source\u002Fcode checks, and write only a non-canonical working packet: flat mode uses `research\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`; product-path mode uses `research\u002F{slug}\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`. Replace `\u003Cskill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `\u003Cpre>\u003Ccode>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions\u002Fconfidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.\n3. **Stage 3 - Finalize approved artifacts.** Consume final compiled YAML for artifact approval only when it has no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths below, and convert the alignment page to `confirmed` with the approval record preserved.\n\nCanonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.\n\n## Evidence And Feedback Handling\n\nTreat user feedback as input to evaluate, not as automatic ground truth.\n\n- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.\n- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.\n- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.\n- When uncertain, say what is known, what is inferred, and what would change the conclusion.\n\n## Prerequisites\n\n- **Hard**: `research\u002Ficp.md` (or `research\u002F{slug}\u002Ficp.md`) must exist. If not, tell the user to run `\u002Fcustomer-discovery` first and stop.\n- **Hard**: `research\u002Fcompetitive-analysis.md` (or `research\u002F{slug}\u002Fcompetitive-analysis.md`) must exist. If not, tell the user to run `\u002Fcompetitive-analysis` first and stop.\n- **Strong default**: `research\u002Fjourney-map.md` (or `research\u002F{slug}\u002Fjourney-map.md`) should exist before writing canonical positioning. If missing, recommend `\u002Fjourney-map` first unless the user explicitly needs a provisional positioning analysis.\n- **Soft**: Read these if they exist:\n  - `research\u002Fjourney-map.md` — where value is delivered, the aha moment\n  - `research\u002Fcustomer-feedback.md` — real customer language about what makes the product different\n  - `research\u002Fmonetization.md` — pricing context for value perception\n\n## Execution Model — Research Session Loop\n\nThis is a **self-advancing Pattern A research orchestrator** (see `docs\u002Fresearch-session-loop-convention.md`). Each invocation starts cold, resolves its state from **pasted YAML + filesystem**, runs **exactly one heavy phase**, emits the next gate, and stops. The user advances the loop by clearing context and re-invoking `\u002Fpositioning`. The user never invokes a framework subskill directly — the orchestrator follows each selected framework's subskill inline.\n\nWhen a framework is pending, the only user-facing continuation route is re-invoking `\u002Fpositioning` with the same product\u002Fresearch path argument when present, for example `\u002Fpositioning research\u002Fafps-tracker`. Never tell the user to run a path-shaped child framework command; the parent resolves the pending framework from the run manifest and filesystem.\n\n\n### Terminal Handoff Contract\n\nEvery terminal response for this Research Session Loop must end with `## Next Work` and one command section. Use `## Recommended Next Command After Compiling YAML` only while a `review` page is waiting for compiled YAML. Use `## Recommended Next Command` only after approved YAML has been consumed and the approved artifact has been written or updated. Do not put any other section after the applicable command section.\n\n### Self-Routing Continuation Payload\n\nEvery `review` alignment page this parent creates must include `agent_routing` in the bottom compiled YAML. The mapping routes a fresh agent back to this parent orchestrator; it does not authorize direct framework invocation or replace parent-owned state resolution. Use this shape, preserving the current product\u002Fresearch path argument when present:\n\n```yaml\nagent_routing:\n  workflow: pattern-a-research-loop\n  parent_skill: positioning\n  command: \"\u002Fpositioning research\u002F{slug}\"\n  product_path: research\u002F{slug}        # omit in flat mode\n  gate_owner: parent-orchestrator\n  gate_type: framework-findings        # or framework-selection, shortcut-selection, synthesis\n  framework_slug: \u003Cframework-slug>     # only for framework-findings gates\n  framework_mode: inline-subskill      # only for framework-findings gates\n  run_manifest: research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml\n  next_resolution: parent-resolves-from-yaml-and-filesystem\n```\n\nFor framework selection, shortcut, and synthesis gates, omit `framework_slug` and `framework_mode`; `gate_type` must name the actual gate. The `command` field must be the same parent command shown under `## Recommended Next Command After Compiling YAML`. The parent consumes the YAML, writes or amends the artifact, archives consumed sources, derives progress from the run manifest plus canonical-intermediate files, and decides whether to load a framework subskill inline.\n\nFor review-pending framework, selection, shortcut, or synthesis pages, `## Next Work` tells the user to review the alignment page and compile YAML, and the command section names `\u002Fpositioning` with the same product\u002Fresearch path argument when present, then clear context before continuing. For post-write pending-framework states, `## Next Work` reports progress as \"k of N frameworks complete\" and says the next run executes the next pending framework; `## Recommended Next Command` names `\u002Fpositioning`.\n\nAfter every framework write, recalculate pending frameworks from the run manifest and canonical-intermediate files before writing this handoff. If no selected frameworks remain and canonical `positioning.md` is missing, `## Next Work` says the next run builds the unified synthesis review page, and `## Recommended Next Command` names `\u002Fpositioning --synthesize` with the same product\u002Fresearch path argument when present. After approved synthesis writes canonical `positioning.md`, the final command section names only the first downstream command selected by the Next Steps decision tree.\n\n\nState lives in two places only:\n\n- **Run manifest** — `research\u002F_working\u002Fpositioning-run.yaml` (flat) or `research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml` (product-path). Records the selected framework set and each framework's intermediate path. Written when the multi-select YAML is approved. Shape:\n\n  ```yaml\n  orchestrator: positioning\n  slug: skills-showcase            # omit in flat mode\n  selected_frameworks:\n    - slug: jtbd-positioning\n      intermediate: research\u002Fskills-showcase\u002Fpositioning-jtbd-positioning.md\n    - slug: strategic-canvas\n      intermediate: research\u002Fskills-showcase\u002Fpositioning-strategic-canvas.md\n  ```\n\n- **Canonical-intermediate existence** — a selected framework is *done* when `research\u002Fpositioning-{framework}.md` (or `research\u002F{slug}\u002Fpositioning-{framework}.md`) exists, *pending* otherwise. `pending = selected − existing-intermediates`. The manifest stores selection only, not per-framework status.\n\n`research\u002F.progress.yaml` stays coarse — its `pipeline_stage` is a pointer, not per-framework status.\n\n### State resolution (resolve the first match; YAML first, then most-progressed A→E)\n\nOn each invocation, after Product-Path Scope Resolution (step 0), resolve state:\n\n| State | Detected when | Heavy phase this session | Emits \u002F stops with |\n|---|---|---|---|\n| **0 — pasted YAML** | a compiled alignment YAML is pasted | branch on `approval_status`: `ready-for-agent-review` → apply the approval for the gate it answers (light: write manifest and\u002For prior framework intermediate, archive consumed source), then fall through to the next pending state below; `not-approved` → amend the named page (refinement session) and stop | amended page, or proceeds ↓ |\n| **A — done** | canonical `research\u002Fpositioning.md` (or `research\u002F{slug}\u002Fpositioning.md`) exists | — | done; emit next-skill route (step 6) |\n| **B — synthesize** | run manifest exists, all selected intermediates exist, no canonical `positioning.md` (also forced by `--synthesize`) | **synthesis** (step 4) | synthesis `review` page |\n| **C — run framework** | run manifest exists, ≥1 selected framework pending | **run next pending framework inline at its research stage** (step 3b) | that framework's findings `review` page |\n| **E — build selection** | no run manifest and no canonical (cold start) | mode detect → load context → recommend frameworks → build multi-select page (steps 1–3a) | multi-select `review` page |\n\n**Cold entry (no state F).** This orchestrator uses `context_intake: scoped` — there is **no deep-interview phase**. A cold start (nothing on disk, after the hard `research\u002Ficp.md` + `research\u002Fcompetitive-analysis.md` prerequisites are satisfied) resolves directly to **state E**; the 1–3 light scope questions in Context Gathering fold into the head of the E session. The `product`\u002F`post-launch`\u002F`obviously-awesome` shortcut short-circuits E→C with a fixed framework set (step 5).\n\n**Light vs heavy.** Recording the approved selection into the run manifest (state 0→C head), writing an already-reviewed framework intermediate, and archiving a consumed source are *light* — they fold into the head of the next heavy session. The heavy phase (one framework's research, synthesis) is the only thing isolated per session.\n\n**Shortcuts.** `\u002Fpositioning --synthesize` forces state B. `\u002Fpositioning product` (also `post-launch`, `obviously-awesome`) is the product-positioning shortcut (step 5): after the user approves the shortcut plan, it writes a fixed single-framework set (`obviously-awesome`) into the run manifest and enters state C. Do not queue framework work in `tasks\u002Ftodo.md` or hand it to `\u002Fexec`.\n\n---\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n### 1. Mode Detection\n\nDetect **market-positioning mode** (default) or **product-positioning mode**:\n\n**Market-positioning mode** activates when:\n- No `research\u002Fcustomer-feedback.md` with post-launch customer evidence, AND\n- No production codebase with live users detected, AND\n- `$ARGUMENTS` does not contain \"product\", \"post-launch\", or \"obviously-awesome\"\n\nAvailable frameworks in market mode:\n- `jtbd-positioning` — Jobs-to-be-Done positioning analysis\n- `strategic-canvas` — Blue Ocean strategic canvas (eliminate\u002Freduce\u002Fraise\u002Fcreate)\n- `moore-positioning` — Geoffrey Moore positioning hypothesis\n- `category-design` — Play Bigger category creation\n\n**Product-positioning mode** activates when:\n- `research\u002Fcustomer-feedback.md` exists with real customer data, OR\n- `$ARGUMENTS` contains \"product\", \"post-launch\", or \"obviously-awesome\", OR\n- Production spec exists AND customer feedback references real users\n\nAvailable frameworks in product mode:\n- `obviously-awesome` — April Dunford (requires real customer evidence)\n- `strategic-canvas` — optionally, for category refresh\n\n### 2. Load Context\n\n- Read `research\u002Ficp.md` — ICP segments, pain points, value props, trigger events\n- Read `research\u002Fcompetitive-analysis.md` — competitor landscape, gaps\n- Read `research\u002Fjourney-map.md` if it exists — aha moment, value delivery\n- Read `research\u002Fcustomer-feedback.md` if it exists — real language, satisfaction drivers\n- Read CLAUDE.md, README for product context\n- Read any existing `research\u002Fpositioning-*.md` intermediate artifacts (from prior runs)\n\n### 3a. State E — Framework Selection & Build Multi-Select Page\n\nBuild the framework multi-select `review` alignment page with:\n\n1. **Mode explanation**: which mode was detected and why (evidence for detection)\n2. **Available evidence summary**: what research exists and what's missing\n3. **Multi-select framework section**: checkboxes for each available framework with:\n   - Framework name and one-line description\n   - Why it's recommended or optional for this context\n   - Pre-checked defaults based on available evidence:\n     - Market mode defaults: `jtbd-positioning` + `strategic-canvas` + `moore-positioning` pre-checked; `category-design` unchecked (recommended only when strategic canvas shows no existing category fits)\n     - Product mode defaults: `obviously-awesome` pre-checked; `strategic-canvas` unchecked (optional refresh)\n4. **Loop plan explanation**: the selected set is the scope-and-candidate approval gate; each selected framework will then be run inline (one findings page per framework) and the run advances by re-invoking `\u002Fpositioning`\n5. **Approval gate**: framework selection confirmation\n\nThis multi-select approval **is** the Stage-1 scope approval for the whole selected set. Stop for compiled YAML. Do **not** write the run manifest or run any framework in this session — that is state C.\n\n### 3b. State C — Run Next Pending Framework (inline)\n\nThis session consumes the approved multi-select YAML (state 0→C) or advances after a prior framework's approval. At the **head** of the session, do the light bookkeeping first:\n\n1. **Write the run manifest** if it does not yet exist: `research\u002F_working\u002Fpositioning-run.yaml` (flat) or `research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml` (product-path), recording `selected_frameworks` with each framework's `slug` and canonical `intermediate` path. Include only frameworks the user selected. Example (market mode):\n\n   ```yaml\n   orchestrator: positioning\n   selected_frameworks:\n     - slug: jtbd-positioning\n       intermediate: research\u002Fpositioning-jtbd-positioning.md\n     - slug: strategic-canvas\n       intermediate: research\u002Fpositioning-strategic-canvas.md\n     - slug: moore-positioning\n       intermediate: research\u002Fpositioning-moore-positioning.md\n   ```\n\n2. **If a prior framework's reviewed content was just approved** by the pasted YAML, write its canonical intermediate `research\u002Fpositioning-{fw}.md` (or `research\u002F{slug}\u002Fpositioning-{fw}.md`) from the already-reviewed working packet, and archive that framework's working packet and superseded review page.\n\nThen run the **one heavy phase** for this session:\n\n3. **Determine the next pending framework** = the first framework in `selected_frameworks` whose canonical intermediate does not yet exist.\n4. **Load and follow that framework subskill's `SKILL.md` inline**, entering at its **research stage (Stage 2)**: the multi-select approval already satisfied the framework's Stage-1 scope gate, so perform the framework's research, write its working packet, and build a single findings `review` page for that framework. Stop for that framework's compiled YAML.\n\n**Advance the loop by self-re-invocation.** When a framework findings page is in `review`, end the terminal message with `## Next Work` telling the user to review the page and compile YAML, followed by `## Recommended Next Command After Compiling YAML` naming `\u002Fpositioning` with the same product\u002Fresearch path argument when present. After a framework's compiled YAML is approved and its canonical intermediate is written, recalculate pending frameworks from the manifest and filesystem before writing the handoff. If pending frameworks remain, end with `## Next Work` reporting progress as \"k of N frameworks complete\" and saying the next run executes the next pending framework, followed by `## Recommended Next Command` naming `\u002Fpositioning`. If no pending frameworks remain and canonical `positioning.md` is missing, end with `## Next Work` saying the next run builds the unified synthesis review page, followed by `## Recommended Next Command` naming `\u002Fpositioning --synthesize` with the same product\u002Fresearch path argument when present. Do not emit cross-skill routing here — that happens only after synthesis.\n\n\n### 4. State B — Synthesis (auto-detected; also `\u002Fpositioning --synthesize`)\n\nEnter synthesis when the run manifest exists, **all** selected framework intermediates exist, and no canonical `research\u002Fpositioning.md` yet exists. An explicit `\u002Fpositioning --synthesize` also forces this state. Read all selected intermediate framework outputs (the `intermediate` paths recorded in the run manifest), e.g.:\n- `research\u002Fpositioning-jtbd-positioning.md`\n- `research\u002Fpositioning-strategic-canvas.md`\n- `research\u002Fpositioning-moore-positioning.md`\n- `research\u002Fpositioning-category-design.md`\n- `research\u002Fpositioning-obviously-awesome.md`\n\nAt least one must exist. If none exist, tell user to run framework selection first.\n\nSynthesize into unified `research\u002Fpositioning.md`:\n\n**Market-positioning synthesis includes:**\n- Combined positioning hypothesis drawing from all framework outputs\n- Moore template filled with evidence from JTBD + Canvas + Category analysis\n- Evidence matrix: each claim mapped to which framework(s) support it\n- Confidence levels per claim (strong\u002Fmoderate\u002Fhypothesized)\n- Validation plan: what needs testing before the position is canonical\n- Mode header: `> Mode: Market Positioning (hypothesized, pre-product)`\n\n**Product-positioning synthesis includes:**\n- Positioning statement (Obviously Awesome output)\n- Evidence matrix grounded in customer feedback\n- Confidence levels (most should be \"strong\" — backed by customer data)\n- Mode header: `> Mode: Product Positioning (customer-grounded)`\n\nBuild alignment page for synthesis approval with:\n- Full proposed `research\u002Fpositioning.md` content\n- Evidence matrix combining all framework sources\n- Confidence\u002Fassumption register\n- Proposed file changes gate\n- Approval gate\n\nAfter approval: write `research\u002Fpositioning.md`, then on this canonical write **archive the run manifest** (`positioning-run.yaml`) and the synthesis working packet under `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-working-path>`, update `research\u002F.progress.yaml` `pipeline_stage` to `positioning`, and emit the downstream next-step routing (step 6). This is the one place cross-orchestrator routing is allowed.\n\n### 5. State C via Product-Positioning Shortcut (`\u002Fpositioning product`)\n\nSkip multi-select. Build an alignment page for the shortcut execution plan with:\n\n1. **Shortcut explanation**: product-positioning shortcut selected and why `obviously-awesome` is the only queued framework\n2. **Evidence readiness**: customer-feedback requirement and any missing evidence caveats\n3. **Proposed loop plan**: the single `obviously-awesome` framework that will be recorded in the run manifest\n4. **Approval gate**: require final compiled YAML approval before writing the run manifest\n\nDo not write the run manifest before alignment approval. The next action is review of the HTML alignment page.\n\nAfter user approval via final compiled YAML, write this selected set to the run manifest and enter the next pending framework session:\n\n```yaml\norchestrator: positioning\nselected_frameworks:\n  - slug: obviously-awesome\n    intermediate: research\u002Fpositioning-obviously-awesome.md\n```\n\nThen enter **state C** and run `obviously-awesome` inline per step 3b. The loop advances by re-invoking `\u002Fpositioning`.\n\n### 6. Next Steps (after synthesis only)\n\nInclude 3–5 applicable items with \"Recommended + Other options\" framing:\n\n- IF no `research\u002Fjourney-map.md`: check for `customer-lifecycle` pack → recommend `\u002Fjourney-map`\n- DEFAULT: check `.agents\u002Fproject.json.enabled_packs` for `product-design` — if not enabled, recommend `npx skillpacks install product-design` from the project shell; if enabled, recommend `\u002Fuser-flow-map [positioning-backed product direction]`\n- IF solution-customer fit is weak\u002Fdisputed: `\u002Fvalue-prop-canvas`\n- IF revenue\u002Fchannels\u002Fcost\u002Fdefensibility risks exposed: `\u002Flean-canvas`\n- IF no `research\u002Fgtm.md`: check for `business-growth` pack → recommend `\u002Fgtm`\n- IF `research\u002Fgtm.md` exists: recommend `\u002Fgtm` refresh\n- IF no `research\u002Fmonetization.md`: check for `business-growth` pack → recommend `\u002Fmonetization`\n- IF codebase exists: check for `business-ops` pack → recommend `\u002Fmvp-gap`\n\n### 7. Downstream Impact Check (after synthesis write)\n\nCheck for downstream research documents that may be affected:\n- `research\u002Fgtm.md`\n\nClassify impact as None\u002FMinor\u002FMajor per standard pattern.\n\n## Optional Research Trigger Map\n\nThese detours are conditional framework owners, not required AFPS chain links. Apply after synthesis.\n\n| Positioning signal | Owner | Trigger threshold |\n|---|---|---|\n| Solution-customer fit weak\u002Fdisputed, value mapping low confidence | `\u002Fvalue-prop-canvas` | Trigger: unique attributes can't be confidently mapped to value. Skip: value mapping clear even if hypothesized. |\n| Business-model risk (revenue\u002Fchannels\u002Fcost\u002Fdefensibility) exposed by category strategy | `\u002Flean-canvas` | Trigger: risk would change UX or prototype choices. Skip: normal competitive findings. |\n| Pricing architecture central to positioning (premium vs value changes direction) | `\u002Fmonetization` | Trigger: category\u002Fvalue mapping requires grounded pricing. Skip: pricing not a differentiator. |\n\n## Output\n\n### State E \u002F State C output: run manifest plus per-framework findings review page\n\nThe state-E multi-select page; then, per state-C session, the run manifest `research\u002F_working\u002Fpositioning-run.yaml` (or `research\u002F{slug}\u002F_working\u002Fpositioning-run.yaml`, written at the head of the first state-C session) plus the next pending framework's findings review page. One findings page per selected framework; the canonical intermediate `research\u002Fpositioning-{framework}.md` is written on that framework's approval.\n\n### State B output (synthesis): `research\u002Fpositioning.md` (or `research\u002F{slug}\u002Fpositioning.md`)\n\n```markdown\n# Positioning\n\n> Based on: [list of framework outputs used]\n> Date: [current date]\n> Mode: Market Positioning (hypothesized, pre-product) | Product Positioning (customer-grounded)\n> Frameworks applied: [list]\n\n## Positioning Statement\n\n**For** [target segment]\n**who** [key pain \u002F trigger event]\n**[product name] is a** [market category]\n**that** [key value \u002F unique benefit]\n**Unlike** [primary competitive alternative]\n**[product name]** [key differentiator]\n\n## Summary\n[2-3 sentences: the positioning thesis]\n\n## Evidence Matrix\n\n| Claim | Supporting Framework(s) | Evidence | Confidence | Assumption Status |\n|-------|------------------------|----------|------------|-------------------|\n| [claim] | JTBD \u002F Canvas \u002F Moore \u002F Category \u002F OA | [source] | Strong \u002F Moderate \u002F Hypothesized | Validated \u002F Needs testing |\n\n## Framework Synthesis\n\n### From JTBD Analysis\n[Key findings — primary job, outcome positioning]\n\n### From Strategic Canvas\n[Key findings — eliminate\u002Freduce\u002Fraise\u002Fcreate moves, competitive gaps]\n\n### From Moore Hypothesis\n[Key findings — positioning template, evidence gaps]\n\n### From Category Design\n[Key findings — category diagnosis, POV if new category]\n\n### From Obviously Awesome\n[Key findings — if product mode]\n\n## Target Segment\n[Best-fit segment with evidence from multiple frameworks]\n\n## Market Category\n[Chosen category with evidence from multiple frameworks]\n\n## Confidence Register\n\n| Element | Confidence | Evidence Source | What Would Change It |\n|---------|-----------|----------------|---------------------|\n| [element] | [level] | [source] | [condition] |\n\n## Validation Plan (market mode only)\n[What needs testing before this position is canonical]\n\n## Positioning Implications\n\n### For Messaging\n### For Product\n### For Sales\n### For Pricing\n\n## Downstream Impact\n[Standard pattern]\n\n## Next Steps\n[Standard routing]\n```\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`.\n- One-time condition-gated records go in `tasks\u002Frecord-todo.md`.\n- Cadence-based reviews go in `tasks\u002Frecurring-todo.md`.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless promoted.\n\n## Constraints\n\n- **Requires ICP + competitive analysis.** Positioning without knowing the customer and the competition is guesswork.\n- **Customer-grounded.** Every positioning decision must connect to real customer behavior or research evidence.\n- **Mode detection is evidence-based.** Do not override mode detection without user confirmation.\n- **Parent owns the research loop.** It records selected frameworks in the run manifest and runs one pending framework inline per invocation. Do not queue framework work in `tasks\u002Ftodo.md` or hand it to `\u002Fexec`.\n- **Synthesis requires at least one framework output.** Do not synthesize from zero evidence.\n- **Do not overwrite existing `research\u002Fpositioning.md`** without asking the user first.\n\n## Context Gathering\n\n**Step 1 — Scope questions.** Before researching, ask the user 1–3 questions via `AskUserQuestion` to understand: their product\u002Fservice, target audience, and what they hope to learn or decide from this research.\n\n**Step 2 — Research.** Conduct research scoped by the user's answers.\n\n**Step 3 — Findings validation.** Before building the alignment page, present the 3–5 most important findings and ask the user to validate or correct any critical assumptions.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fpositioning-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":29,"version":43,"invocation":31,"description":7,"visual_tier":37,"argument-hint":44,"context_intake":45},"v0.23","[optional: \"product\" | \"--synthesize\" | focus area]","scoped","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbusiness-research\u002Fclaude\u002Fpositioning\u002Farchive\u002Fv0.23",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill positioning",{"tool":62,"command":63},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill positioning",{"tool":65,"command":66},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill positioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-research\u002Fclaude\u002Fpositioning\u002Farchive\u002Fv0.23\u002FSKILL.md",true,[],[71,83,93,105,118,129],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":38},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[78,79,80,81,32,82],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":38},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[90,91,92,82,80,32],"deck install valid","deck","install",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":38},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[100,101,102,82,103,104,80,32],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":38},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[115,116,82,103,32,117,80],"codex missing skill valid","missing","fallback",{"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":38},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[124],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},[82,103,117,126,127,128,32,80],"base skill","codex base skill fallback valid","base",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":38},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[82,102,101,136,104,32,80],"claude pack guard valid"]