@sushanglewis/lincoln 1.5.0 → 1.5.2

package/framework/.claude/skills/dependencies.yaml

@@ -0,0 +1,139 @@
+---
+schema_version: 1.0.0
+description: |
+  Declares external skills and CLIs required by the Lincoln workflow.
+  Run `scripts/check-skill-dependencies.sh` to verify the local environment.
+
+# Pin policy (#62): external skills/plugins are pinned to a known-good upstream
+# ref (full SHA), never a floating branch — an upstream commit must not silently
+# change every Lincoln user's session behavior. (#39 note: pins avoid the stale
+# fixed-version problem by making every upgrade explicit and reviewable.)
+# Upgrade flow: 1) pick the new upstream ref; 2) update `ref` (and `pinned_at`);
+# 3) run the benchmark to confirm no behavior regression; 4) merge.
+# Check upstream drift vs pins: `python3 "${CLAUDE_PLUGIN_ROOT:-${LINCOLN_HOME:-$HOME/.lincoln/current}}/scripts/check-dependency-drift.py`."
+
+skills:
+  superpowers:
+    source: https://github.com/obra/superpowers.git
+    ref: 6fd4507659784c351abbd2bc264c7162cfd386dc
+    pinned_from: main
+    pinned_at: 2026-07-15
+    type: skill
+    required: true
+    license: MIT
+    required_skills:
+      - superpowers:brainstorming
+      - superpowers:writing-plans
+      - superpowers:test-driven-development
+      - superpowers:subagent-driven-development
+      - superpowers:verification-before-completion
+      - superpowers:dispatching-parallel-agents
+      - superpowers:using-git-worktrees
+      - superpowers:systematic-debugging
+      - superpowers:finishing-a-development-branch
+      - superpowers:requesting-code-review
+      - superpowers:receiving-code-review
+      - superpowers:writing-skills
+
+  gsd:
+    source: https://github.com/gsd-build/get-shit-done.git
+    ref: bdcaab2c752d9a33a1a1ca9acf3a3c81fb991815
+    pinned_from: main
+    pinned_at: 2026-07-15
+    type: skill
+    required: true
+    license: MIT
+    required_skills:
+      - gsd-import
+      - gsd-docs-update
+      - gsd-forensics
+      - gsd-ns-review
+      - gsd-code-review
+      - gsd-debug
+      - gsd-eval-review
+      - gsd-ingest-docs
+
+  openspec:
+    source: https://github.com/Fission-AI/openspec.git
+    ref: v0.5.0
+    type: cli
+    binary: openspec
+    required: true
+    platforms:
+      macos: npm install -g @fission-ai/openspec
+      linux: npm install -g @fission-ai/openspec
+    install_note: Requires Node.js >= 20.
+
+  gh:
+    source: https://cli.github.com/
+    type: cli
+    binary: gh
+    required: true
+    platforms:
+      macos: brew install gh
+      linux: sudo apt-get install gh
+    install_note: After install, run 'gh auth login'.
+
+  ffmpeg:
+    source: https://ffmpeg.org/
+    type: cli
+    binary: ffmpeg
+    required: false
+    platforms:
+      macos: brew install ffmpeg
+      linux: sudo apt-get install ffmpeg
+    install_note: Optional. Only needed for audio/video processing during interview ingestion (recording transcription).
+
+  faster-whisper:
+    source: https://github.com/SYSTRAN/faster-whisper.git
+    type: cli
+    binary: faster-whisper
+    required: false
+    platforms:
+      macos: pip install faster-whisper
+      linux: pip install faster-whisper
+    install_note: |
+      Optional. Only needed for interview recording transcription.
+      Recommended local Whisper implementation.
+      Alternatives: openai-whisper (`pip install openai-whisper`) or OpenAI API.
+
+  lc-explore-opensource:
+    source: inline
+    type: skill
+    path: .claude/skills/lc-explore-opensource
+
+  lc-build-codebase-knowledge:
+    source: inline
+    type: skill
+    path: .claude/skills/lc-build-codebase-knowledge
+
+  lc-workflow-router:
+    source: inline
+    type: skill
+    path: .claude/skills/lc-workflow-router
+
+  # oh-my-claudecode — optional multi-agent orchestration layer, installed by default
+  oh-my-claudecode:
+    source: https://github.com/Yeachan-Heo/oh-my-claudecode.git
+    ref: 590fb988931d34a12604be0ca4215c818079018e
+    pinned_from: main
+    pinned_at: 2026-07-15
+    type: plugin
+    required: false
+    default_install: true
+    license: MIT
+    platforms:
+      macos: git clone https://github.com/Yeachan-Heo/oh-my-claudecode.git ~/.claude/skills/oh-my-claudecode && git -C ~/.claude/skills/oh-my-claudecode checkout 590fb988931d34a12604be0ca4215c818079018e
+      linux: git clone https://github.com/Yeachan-Heo/oh-my-claudecode.git ~/.claude/skills/oh-my-claudecode && git -C ~/.claude/skills/oh-my-claudecode checkout 590fb988931d34a12604be0ca4215c818079018e
+    install_note: Optional but recommended. Installed as a skill under ~/.claude/skills/.
+    recommended_skills:
+      - oh-my-claudecode:plan
+      - oh-my-claudecode:team
+      - oh-my-claudecode:verify
+      - oh-my-claudecode:autopilot
+      - oh-my-claudecode:ralph
+      - oh-my-claudecode:ultrawork
+      - oh-my-claudecode:deep-interview
+      - oh-my-claudecode:ai-slop-cleaner
+      - oh-my-claudecode:wiki
+      - oh-my-claudecode:writer-memory

package/framework/.claude/skills/draft-product-design/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: draft-product-design
+description: 基于已确认需求生成产品设计评审文档包
+triggers:
+  - "生成产品设计文档"
+  - "draft-product-design"
+inputs:
+  - name: session_id
+    description: 访谈会话 ID
+    required: true
+  - name: design_id
+    description: 产品设计 ID，如 checkout-redesign
+    required: true
+outputs:
+  - "{process_slug}/pages/docs/design-review.html"
+  - "{process_slug}/pages/docs/scenarios.html"
+  - "{process_slug}/pages/docs/feature-catalog.html"
+  - "{process_slug}/pages/docs/data-model.html"
+  - "{process_slug}/pages/docs/flows.html"
+  - "{process_slug}/pages/docs/feasibility.html"
+  - "{process_slug}/pages/docs/page-map.html"
+  - "{process_slug}/pages/docs/version-log.html"
+  - "{process_slug}/pages/docs/api-list.html"
+  - "{process_slug}/handoffs/pm-to-ux/pm-to-ux.handoff.yaml"
+required_tools:
+  - Read
+  - Bash
+  - Write
+---
+
+# draft-product-design
+
+## Purpose
+
+Using [draft-product-design] to 基于已确认需求生成产品设计评审文档包.
+
+
+基于已确认需求生成面向 PM 评审的简洁产品设计文档包。
+
+运行入口： prompts/main.md

package/framework/.claude/skills/draft-product-design/prompts/main.md

@@ -0,0 +1,47 @@
+# draft-product-design
+
+You are executing the Lincoln workflow step `product-design-docs`: turn approved requirements into a concise product design review package for the human PM.
+
+## Goal
+
+Create `{process_slug}/pages/docs/` HTML design documents with enough product, data, flow, feasibility, and technical framing for PM review and later development planning, without creating unnecessary review burden.
+
+## Input
+
+- `session_id`: the interview session identifier
+- `design_id`: a kebab-case product design identifier
+
+## 子技能准备
+
+在执行本 prompt 前：
+1. 调用 `superpowers:brainstorming` 探索 ≥2 种设计方向并说明 trade-offs，等待 PM 确认。
+2. PM 确认后，调用 `superpowers:writing-plans` 规划文档文件结构与每份文档的职责。
+
+## Steps
+
+1. Validate that `{process_slug}/pages/docs/requirements.html` is approved (contains `<!-- status: approved -->`).
+2. Read `{process_slug}/pages/docs/requirements.html`, `user-stories.html`, and the root-level `{process_slug}/pages/docs/prd.html`.
+3. Produce the design package under `{process_slug}/pages/docs/` using `.claude/templates/issue-package/page-doc.html.tpl`. Each page embeds Markdown in `<script type="text/markdown" id="docSource">` with a `<!-- version: v1.0 -->` marker and meta tags (`doc-title`, `nav-label`, `nav-group`, `doc-version`, `doc-uid`). Also include the annotation tags `doc-purpose`, `doc-layout`, `doc-fields`, `doc-boundaries`, `doc-exceptions` (and `doc-stories`, `doc-rules`, `doc-refs` when useful) so the portal right panel explains functionality, layout, fields, boundary cases, and exception flows:
+   - `design-review.html`: PM-facing entry point with decision summary, scope, links to all design docs, open questions, and approval checklist.
+   - `scenarios.html`: target users, primary scenarios, boundary scenarios, and non-goals.
+   - `feature-catalog.html`: concise feature list, priority, acceptance mapping, and source requirement links.
+   - `data-model.html`: core entities, fields, constraints, validation rules, and state transitions.
+   - `flows.html`: Mermaid user flow, business flow, screen flow, sequence diagram, and architecture diagram.
+   - `page-map.html`: page inventory, page relationships, navigation, and routing/state notes.
+   - `feasibility.html`: business feasibility, technical feasibility, current official framework/library options, usable open-source projects, risks, and recommended stack.
+   - `version-log.html`: design decision version history and rationale.
+   - `api-list.html`: internal and external APIs/data contracts the feature depends on.
+4. Create the PM→UX handoff contract at `{process_slug}/handoffs/pm-to-ux/pm-to-ux.handoff.yaml` referencing the approved design docs and PRD versions.
+5. Keep all documents traceable to the approved requirement and transcript timestamps where available.
+6. Update the root `{process_slug}/pages/docs/prd.html` section 9 "相关产物链接" with links to the new design documents. If the PRD already has an approved snapshot (`pages/docs/snapshots/prd-v*.html`), warn the PM that any content change requires bumping the version marker and re-freezing via `python scripts/lincoln_prd.py freeze`.
+7. Ask the PM to review `design-review.html` and linked docs (they can open `{process_slug}/index.html` in a browser).
+8. When the PM confirms, add `<!-- status: approved -->` to `design-review.html`.
+9. Run `python scripts/stage_loader.py --stage product-design-docs --action record-artifacts`.
+
+## Rules
+
+- Use Chinese for PM-facing content unless the requirements are in English.
+- Keep documents short and reviewable; prefer tables and Mermaid diagrams over long prose.
+- For technical frameworks and open-source projects, check current official docs or primary repositories before recommending.
+- Do not create a Pencil prototype in this step.
+- After approval, tell the user to run: `claude build-product-prototype <session_id> <design_id>`.

package/framework/.claude/skills/lc-analyze-frameworks/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-analyze-frameworks
+description: 提供并应用分析框架（SWOT、波特五力、商业模式画布、PEST、用户分析等），必要时生成 ECharts/HTML 可视化方案。
+version: 1.0.0
+triggers:
+  - "lc-analyze-frameworks"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/analysis-frameworks.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-analyze-frameworks
+
+## Purpose
+
+Using [lc-analyze-frameworks] to 提供并应用分析框架（SWOT、波特五力、商业模式画布、PEST、用户分析等），必要时生成 ECharts/HTML 可视化方案.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-analyze-frameworks` 阶段。
+- PM 需要 提供并应用分析框架（SWOT、波特五力、商业模式画布、PEST、用户分析等），必要时生成 ECharts/HTML 可视化方案。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/analyze-frameworks.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。

package/framework/.claude/skills/lc-analyze-frameworks/prompts/main.md

@@ -0,0 +1,95 @@
+# lc-analyze-frameworks prompt
+
+You are executing the Lincoln workflow step `lc-analyze-frameworks`: select and apply analysis frameworks to the research.
+
+## Goal
+
+Produce `{process_slug}/research/{session_id}/analysis-frameworks.md` that selects the right frameworks, applies them, and specifies how to visualize the results (ECharts or HTML).
+
+## Inputs
+
+- `session_id`: the research session identifier
+- `{process_slug}/research/{session_id}/scope.md`
+- `{process_slug}/research/{session_id}/first-principles.md`
+- `{process_slug}/research/{session_id}/stakeholders.md`
+
+## Steps
+
+1. Read prior documents.
+2. From the framework catalog, select 2-4 frameworks suited to the decision:
+   - SWOT — for strategic positioning
+   - Porter's Five Forces — for market attractiveness
+   - Business Model Canvas — for value creation logic
+   - PEST — for macro context
+   - User Analysis (jobs-to-be-done, personas) — for demand side
+   - Custom multi-dimensional framework — when none of the above fit
+3. Justify each selection in one sentence.
+4. Apply each framework using the evidence collected so far; note gaps.
+5. For each framework, specify the best visualization:
+   - SWOT → quadrant matrix (HTML/CSS grid or ECharts custom series)
+   - Porter's Five Forces → radar chart or horizontal bar (ECharts)
+   - Business Model Canvas → HTML table/grid
+   - PEST → 2x2 matrix or quadrant chart
+   - User Analysis → persona cards or journey flow (HTML)
+   - Custom → choose the most intuitive ECharts/HTML rendering
+6. Optionally generate the actual HTML/ECharts file in `{process_slug}/research/{session_id}/visualizations/`.
+7. Write `analysis-frameworks.md` using the template below.
+
+## Output template
+
+```markdown
+# Analysis Frameworks: <Title>
+
+## Selected Frameworks
+
+| Framework | Why Selected | Key Dimensions | Visualization |
+|-----------|--------------|----------------|---------------|
+| SWOT      | ...          | ...            | quadrant matrix |
+| ...       | ...          | ...            | ...           |
+
+## Framework Applications
+
+### SWOT
+
+#### Strengths
+- ...
+
+#### Weaknesses
+- ...
+
+#### Opportunities
+- ...
+
+#### Threats
+- ...
+
+### Porter's Five Forces
+
+| Force | Intensity | Evidence |
+|-------|-----------|----------|
+| ...   | ...       | ...      |
+
+## Visualization Plan
+
+- <file path and chart type for each framework>
+
+## Generated Visualizations
+
+- `{process_slug}/research/{session_id}/visualizations/swot.html`
+- ...
+
+## Implications
+
+- <what the frameworks reveal>
+```
+
+## Rules
+
+- Match the framework to the decision, not the other way around.
+- Visualizations should be renderable in a browser (HTML/ECharts); embed data inline so they work offline.
+- If generating HTML, include a concise title and legend.
+
+## Exit Criteria
+
+- `analysis-frameworks.md` selects and applies at least two frameworks.
+- Each framework has a specified visualization format.

package/framework/.claude/skills/lc-benchmark/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: lc-benchmark
+description: Generate a Lincoln benchmark report on explicit request.
+triggers:
+  - lc-benchmark
+  - 运行 benchmark
+  - 生成 benchmark 报告
+inputs:
+  - name: trigger
+    description: Optional trigger context (manual, handoff, pr_created, pr_merged, session_stop)
+    required: false
+outputs:
+  - "{process_slug}/benchmark/lc-benchmark-{trigger}-{timestamp}.md"
+  - "{process_slug}/benchmark/lc-benchmark-{trigger}-{timestamp}.json"
+required_tools:
+  - Bash
+---
+
+# lc-benchmark
+
+## Purpose
+
+Using [lc-benchmark] to generate a Lincoln session benchmark report.
+
+Run Lincoln benchmark metrics and write the Markdown + JSON report pair to the
+active issue package's `benchmark/` directory. Benchmark is opt-in: it is no
+longer triggered automatically on session stop or PR events.
+
+## When to Use
+
+- The PM or QA explicitly asks for a benchmark report.
+- After a meaningful milestone (handoff, PR creation/merge) when humans want
+to review L1-L5 metrics.
+- During release readiness review.
+
+## Inputs
+
+- Active `{process_slug}/workflow-stage.yaml` (auto-resolved).
+- Optional `--trigger` context to label the report.
+
+## Outputs
+
+- `{process_slug}/benchmark/lc-benchmark-{trigger}-{timestamp}.md`
+- `{process_slug}/benchmark/lc-benchmark-{trigger}-{timestamp}.json`
+
+## Rules
+
+- Default trigger is `manual`.
+- Do not run benchmark after every tool use or session stop.
+- Reports should be generated only when a human explicitly requests metrics or
+when a release/hygiene gate requires them.
+
+## Invocation
+
+Prefer using the `lc-benchmark` command or Skill tool. Equivalent CLI:
+
+```bash
+python3 "${CLAUDE_PLUGIN_ROOT:-${LINCOLN_HOME:-$HOME/.lincoln/current}}/scripts/lc-benchmark-cli.py"
+python3 "${CLAUDE_PLUGIN_ROOT:-${LINCOLN_HOME:-$HOME/.lincoln/current}}/scripts/lc-benchmark-cli.py" --trigger handoff
+python3 "${CLAUDE_PLUGIN_ROOT:-${LINCOLN_HOME:-$HOME/.lincoln/current}}/scripts/lc-benchmark-cli.py" --state-file issue-<N>/workflow-stage.yaml --trigger manual
+```

package/framework/.claude/skills/lc-build-codebase-knowledge/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: lc-build-codebase-knowledge
+description: Use when starting Lincoln on an existing project with source code but no feature knowledge base yet.
+version: 1.0.0
+---
+
+# Lincoln Build Codebase Knowledge
+
+## Purpose
+
+Using [lc-build-codebase-knowledge] to scan an existing codebase and generate feature knowledge documents under `knowledge/`.
+
+Scan an existing codebase, identify its major features/modules, and generate feature knowledge documents under `knowledge/` so Lincoln can iterate from facts instead of assumptions.
+
+## When to Use
+
+- Project already has source code.
+- `knowledge/03-features/` is empty or out of date.
+- The `existing-project-iteration` workflow template is active.
+
+## Inputs
+
+- Repository root
+- Existing source tree
+- Existing `README.md`, `CHANGELOG.md`, and any architectural docs
+
+## Outputs
+
+- `knowledge/00-index.md` — master index
+- `knowledge/03-features/existing-<feature>.md` — one per core feature
+- `knowledge/05-glossary/00-index.md` — domain terms inferred from code
+
+## Rules
+
+- Do not modify source code.
+- Infer features from directory structure, public APIs, and README.
+- Cross-check generated docs against source files (cite file paths).
+- Stop and ask the PM when confidence is low.

package/framework/.claude/skills/lc-build-codebase-knowledge/prompts/build-codebase-knowledge.md

@@ -0,0 +1,61 @@
+# build-codebase-knowledge prompt
+
+You are the Lincoln Codebase Knowledge Builder. Your job is to turn an existing codebase into a concise feature knowledge base.
+
+## Phase 1 — Structural scan
+
+1. Run `scripts/build-codebase-knowledge.py --root .` to get a machine-readable feature map.
+2. Read `README.md`, `CHANGELOG.md`, and any `ARCHITECTURE.md` / `docs/` files.
+3. Identify the top 3-10 features/modules that a PM would care about.
+
+## Phase 2 — Deep read per feature
+
+For each feature from the map:
+
+1. Read the entry-point files listed by the scanner.
+2. Summarize in one paragraph:
+   - What the feature does (business value)
+   - How it is implemented (high-level technical approach)
+   - Key files and public APIs
+3. List acceptance criteria that could be derived from existing tests or behavior.
+
+## Phase 3 — Write knowledge documents
+
+1. Create `knowledge/00-index.md` with a table of features and links.
+2. Create `knowledge/03-features/existing-<feature>.md` for each feature using the template below.
+3. Create `knowledge/05-glossary/00-index.md` with domain terms and definitions inferred from code.
+
+## Feature document template
+
+```markdown
+# <Feature Name>
+
+## Business knowledge
+
+- Purpose:
+- User value:
+- Linked requirements:
+
+## Technical knowledge
+
+- Entry points:
+- Key files:
+- Public API / surface:
+- Data model:
+- Dependencies:
+
+## Acceptance criteria
+
+- [ ] <criterion 1>
+- [ ] <criterion 2>
+
+## Source references
+
+- `src/...`
+- `tests/...`
+```
+
+## Human gate
+
+- Ask the PM to review `knowledge/00-index.md` before continuing.
+- Mark `codebase-knowledge-ready` in `<process_slug>/workflow-stage.yaml` only after PM confirms or 5 minutes pass with no objections.

package/framework/.claude/skills/lc-collect-intelligence/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-collect-intelligence
+description: 基于权威报告、官方动态、开放 API、官网等渠道，体系化收集研究所需的权威信息并标注来源。
+version: 1.0.0
+triggers:
+  - "lc-collect-intelligence"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/collected-intelligence.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-collect-intelligence
+
+## Purpose
+
+Using [lc-collect-intelligence] to 基于权威报告、官方动态、开放 API、官网等渠道，体系化收集研究所需的权威信息并标注来源.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-collect-intelligence` 阶段。
+- PM 需要 基于权威报告、官方动态、开放 API、官网等渠道，体系化收集研究所需的权威信息并标注来源。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/collect-intelligence.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。

package/framework/.claude/skills/lc-collect-intelligence/prompts/main.md

@@ -0,0 +1,72 @@
+# lc-collect-intelligence prompt
+
+You are executing the Lincoln workflow step `lc-collect-intelligence`: systematically gather authoritative information for the research.
+
+## Goal
+
+Produce `{process_slug}/research/{session_id}/collected-intelligence.md` that compiles evidence from authoritative sources, organized by research question and analysis framework.
+
+## Inputs
+
+- `session_id`: the research session identifier
+- `{process_slug}/research/{session_id}/scope.md`
+- `{process_slug}/research/{session_id}/analysis-frameworks.md`
+- Any prior research documents
+
+## Steps
+
+1. Read the scope and selected analysis frameworks.
+2. For each research question and framework, derive an information checklist.
+3. Gather information from authoritative sources:
+   - Industry reports (Gartner, IDC, McKinsey, etc.)
+   - Official product docs, blogs, release notes
+   - Open API docs and changelogs
+   - Public financial reports, investor decks
+   - Reputable news and analysis sites
+4. For each piece of evidence, record:
+   - Claim / fact
+   - Source URL
+   - Source type
+   - Confidence (high / medium / low)
+   - Relevant research question
+5. Write `collected-intelligence.md` using the template below.
+
+## Output template
+
+```markdown
+# Collected Intelligence: <Title>
+
+## Research Questions → Evidence
+
+### Q1: <question>
+
+| Claim | Source | Type | Confidence | Notes |
+|-------|--------|------|------------|-------|
+| ...   | ...    | ...  | ...        | ...   |
+
+## Framework-Specific Evidence
+
+### SWOT
+- **Strengths evidence:** ...
+- **Weaknesses evidence:** ...
+
+## Information Gaps
+
+- <what we still need to know>
+
+## Source Index
+
+1. <source 1>
+2. <source 2>
+```
+
+## Rules
+
+- Prioritize authoritative sources over anonymous opinions.
+- Quote or paraphrase accurately; never fabricate sources.
+- Mark low-confidence information explicitly.
+
+## Exit Criteria
+
+- `collected-intelligence.md` has evidence mapped to research questions.
+- Every claim has a source and confidence rating.

package/framework/.claude/skills/lc-competitive-analysis/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-competitive-analysis
+description: 分析竞争格局，评估竞争对手定位、能力、优势与劣势，形成差异化洞察。
+version: 1.0.0
+triggers:
+  - "lc-competitive-analysis"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/competitive.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-competitive-analysis
+
+## Purpose
+
+Using [lc-competitive-analysis] to 分析竞争格局，评估竞争对手定位、能力、优势与劣势，形成差异化洞察.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-competitive-analysis` 阶段。
+- PM 需要 分析竞争格局，评估竞争对手定位、能力、优势与劣势，形成差异化洞察。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/competitive-analysis.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。