@sushanglewis/lincoln 1.5.0 → 1.5.2

package/framework/.claude/skills/lc-competitive-analysis/prompts/main.md

@@ -0,0 +1,70 @@
+# lc-competitive-analysis prompt
+
+You are executing the Lincoln workflow step `lc-competitive-analysis`: analyze the competitive landscape.
+
+## Goal
+
+Produce `{process_slug}/research/{session_id}/competitive.md` with a structured competitive analysis, including positioning, SWOT, and differentiation opportunities.
+
+## Inputs
+
+- `session_id`: the research session identifier
+- `{process_slug}/research/{session_id}/scope.md`
+- `{process_slug}/research/{session_id}/market.md`
+- `{process_slug}/research/{session_id}/product.md`
+
+## Steps
+
+1. Read prior research documents.
+2. Identify direct and indirect competitors.
+3. For each competitor, summarize positioning, target segment, key strengths, and key weaknesses.
+4. Build a SWOT for our product (or proposed product) in this competitive context.
+5. Identify 2-4 differentiation opportunities.
+6. Use WebSearch / WebFetch to verify claims.
+7. Write `competitive.md` using the template below.
+
+## Output template
+
+```markdown
+# Competitive Analysis: <Title>
+
+## Competitor Landscape
+
+| Competitor | Type | Positioning | Target Segment | Key Strengths | Key Weaknesses |
+|------------|------|-------------|----------------|---------------|----------------|
+| ...        | ...  | ...         | ...            | ...           | ...            |
+
+## SWOT (Our Product)
+
+### Strengths
+- ...
+
+### Weaknesses
+- ...
+
+### Opportunities
+- ...
+
+### Threats
+- ...
+
+## Differentiation Opportunities
+
+1. **<Opportunity 1>**
+   - Evidence: ...
+   - How to exploit: ...
+
+## Strategic Implications
+
+- <what this means for positioning>
+```
+
+## Rules
+
+- Be specific: avoid generic claims like "better UX" without evidence.
+- Cite sources for competitor facts.
+- Distinguish current state from future threats.
+
+## Exit Criteria
+
+- `competitive.md` includes a competitor table, SWOT, and at least two differentiation opportunities.

package/framework/.claude/skills/lc-explore-opensource/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: lc-explore-opensource
+description: Use during product design when the requirement can be solved or informed by existing open-source projects.
+version: 1.0.0
+---
+
+# Lincoln Explore Open Source
+
+## Purpose
+
+Using [lc-explore-opensource] to research open-source projects that can solve or inform the current requirement.
+
+Research existing open-source projects that solve a similar problem, score them against Lincoln criteria, and produce a recommendation document.
+
+## When to Use
+
+- `oss-first-design` workflow template is active.
+- `product-design-docs` stage identifies a subproblem that could be delegated to an existing library/tool.
+- PM says "看看有没有开源方案".
+
+## Inputs
+
+- Requirement keywords
+- Target technology stack
+- Constraints (license, self-host vs SaaS, language)
+
+## Outputs
+
+- `{process_slug}/docs/research/{change_name}-oss-options.md`
+
+## Rules
+
+- Prefer active projects with clear documentation.
+- Score on business fit, technical fit, license, maintenance, and integration cost.
+- Do not download or execute third-party code.
+- Present at least 2 options plus a "build from scratch" baseline.

package/framework/.claude/skills/lc-explore-opensource/prompts/explore-opensource.md

@@ -0,0 +1,77 @@
+# explore-opensource prompt
+
+You are the Lincoln Open Source Researcher. Find and evaluate open-source projects that could address the current requirement.
+
+## Inputs
+
+- Requirement summary (from `{process_slug}/pages/docs/requirements.html`)
+- Design topic (from current design context)
+- Target stack/language (from `{process_slug}/pages/docs/design-review.html`)
+
+## Steps
+
+1. Extract 2-5 search keywords from the requirement.
+2. Search GitHub/npm/PyPI/crates for candidate projects:
+   - Use `WebSearch` or GitHub MCP.
+   - Record name, repo URL, license, last update, stars/downloads.
+3. For each candidate, read README and summarize:
+   - What problem it solves
+   - Key features relevant to the requirement
+   - Integration approach
+   - License compatibility
+4. Score each candidate 1-5 on:
+   - Business fit: does it match the user problem?
+   - Technical fit: does it match our stack?
+   - Maintenance: recent commits, issue response, release cadence
+   - Documentation: README, examples, API docs
+   - Integration cost: API surface, deployment complexity
+5. Compute a weighted total: business 30%, technical 25%, maintenance 20%, docs 15%, integration 10%.
+6. Write `{process_slug}/docs/research/{change_name}-oss-options.md` with:
+   - Executive recommendation
+   - Candidate table
+   - Detailed pros/cons for top 2
+   - Build-from-scratch baseline
+   - Next-step recommendation
+
+## Output format
+
+```markdown
+# Open Source Research: <Topic>
+
+## Recommendation
+
+**Top choice:** <project name>
+**Reason:** <one sentence>
+
+## Candidates
+
+| Project | License | Stars | Business | Technical | Maintenance | Docs | Integration | Total |
+|---------|---------|-------|----------|-----------|-------------|------|-------------|-------|
+| ...     | ...     | ...   | ...      | ...       | ...         | ...  | ...         | ...   |
+
+## Top candidate details
+
+### 1. <Project A>
+- Repo:
+- Pros:
+- Cons:
+- Integration notes:
+
+### 2. <Project B>
+...
+
+## Build-from-scratch baseline
+
+- Effort estimate:
+- Maintenance burden:
+- When it wins:
+
+## Next steps
+
+1. ...
+```
+
+## Human gate
+
+- Present the candidate table to PM.
+- Do not make a final recommendation binding without PM confirmation.

package/framework/.claude/skills/lc-first-principles/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-first-principles
+description: 帮助 PM 回归底层真相，挑战假设，识别第一性原理，为研究奠定坚实基础。
+version: 1.0.0
+triggers:
+  - "lc-first-principles"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/first-principles.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-first-principles
+
+## Purpose
+
+Using [lc-first-principles] to 帮助 PM 回归底层真相，挑战假设，识别第一性原理，为研究奠定坚实基础.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-first-principles` 阶段。
+- PM 需要 帮助 PM 回归底层真相，挑战假设，识别第一性原理，为研究奠定坚实基础。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/first-principles.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。

package/framework/.claude/skills/lc-first-principles/prompts/main.md

@@ -0,0 +1,73 @@
+# lc-first-principles prompt
+
+You are executing the Lincoln workflow step `lc-first-principles`: explore the first principles behind the research topic.
+
+## Goal
+
+Produce `{process_slug}/research/{session_id}/first-principles.md` that captures the fundamental truths, unstated assumptions, and root causes beneath the research topic.
+
+## Inputs
+
+- `session_id`: the research session identifier
+- `{process_slug}/research/{session_id}/scope.md`
+
+## Steps
+
+1. Read the approved `scope.md`.
+2. Ask: "What are we actually trying to decide?" "Why does this problem exist?" "What must be true for any solution to matter?"
+3. List the explicit and implicit assumptions held by the PM, users, and team.
+4. For each assumption, ask "Is this always true?" and "What would happen if it were false?"
+5. Trace each assumption down to a first principle: a statement that cannot be reduced further within this context.
+6. Identify 1-3 root causes or fundamental truths that reshape how the research should be framed.
+7. Write `first-principles.md` using the template below.
+
+## Output template
+
+```markdown
+# First-Principles Analysis: <Title>
+
+## Decision Context
+
+<复述 scope 中的决策背景>
+
+## Explicit Assumptions
+
+| Assumption | Why it is held | Evidence | Risk if false |
+|------------|----------------|----------|---------------|
+| ...        | ...            | ...      | ...           |
+
+## Implicit Assumptions
+
+- <unspoken beliefs that need surfacing>
+
+## First Principles
+
+1. **<Principle 1>**
+   - Reasoning: <why it is fundamental>
+   - Implication: <how it reframes the research>
+
+## Root Causes
+
+1. <Root cause 1>
+2. <Root cause 2>
+
+## Reframed Research Questions
+
+1. <问题 1，基于第一性原理>
+2. <问题 2>
+
+## Questions for PM Confirmation
+
+- <1-2 questions to confirm the reframing>
+```
+
+## Human Interaction Rules
+
+- Present the reframed questions to the PM.
+- Pause for PM feedback. If the PM provides refinements, update the document and continue; otherwise proceed.
+- If the PM disagrees with an assumption, capture the revised view and update the document.
+
+## Exit Criteria
+
+- `first-principles.md` is complete and has been reviewed by the PM (revisions incorporated if any).
+- At least one implicit assumption has been surfaced and validated.

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

@@ -0,0 +1,34 @@
+---
+name: lc-handoff
+description: 为当前阶段生成交接文档，并标记人类审批通过
+triggers:
+  - "生成交接文档"
+  - "lc-handoff"
+  - "handoff"
+inputs:
+  - name: stage
+    description: 当前阶段 ID，如 clarify
+    required: false
+outputs:
+  - "{process_slug}/handoffs/lc-handoff-{stage}.md"
+required_tools:
+  - Read
+  - Bash
+  - Write
+---
+
+# lc-handoff
+
+## Purpose
+
+Using [lc-handoff] to 为当前阶段生成交接文档，并标记人类审批通过.
+
+
+为当前阶段生成交接文档，并在人类 PM 确认后标记 gate 审批通过。
+
+执行步骤：
+1. 读取 `<process_slug>/workflow-stage.yaml` 确定当前 stage 和 process_slug。
+2. 收集当前 stage 的产物、决策、待解决问题。
+3. 写入 `<process_slug>/handoffs/lc-handoff-{stage}.md`。
+4. 人类 PM 确认后，调用 `python scripts/stage_loader.py --stage {stage} --action approve-gate`。
+5. 调用 `python scripts/stage_loader.py --action append-node` 追加节点记录。

package/framework/.claude/skills/lc-init-branch/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: lc-init-branch
+description: 基于 GitHub issue 初始化 Lincoln issue work package 和 feature branch
+triggers:
+  - "初始化 Lincoln 分支"
+  - "lc-init-branch"
+  - "创建 Lincoln feature branch"
+  - "初始化 issue 工作包"
+inputs:
+  - name: issue_number
+    description: GitHub issue 编号，如 21
+    required: true
+  - name: session_id
+    description: 会话 ID，如 2026-06-27-stakeholder；可选，默认基于 issue 生成
+    required: false
+  - name: design_id
+    description: 设计 ID，如 checkout-redesign；可选，默认基于 issue 生成
+    required: false
+  - name: process_slug
+    description: 过程包目录名；可选，默认 issue-{number}
+    required: false
+outputs:
+  - git branch issue-{number}（若当前在 main）
+  - 分支根目录下的 {process_slug}/ 过程包（designs/ docs/ interviews/ openspec/ recordings/ requirements/）
+  - '"{process_slug}/workflow-stage.yaml" 含 issue_number'
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-init-branch
+
+## Purpose
+
+Using [lc-init-branch] to 基于 GitHub issue 初始化 Lincoln issue work package 和 feature branch.
+
+
+PM 在 Conductor 中基于 GitHub issue 初始化 workspace 后，调用此 skill 创建对应的过程包：
+
+1. 若当前在 `main`，切出 `issue-{number}` feature branch；若已处于 feature branch，则使用该分支。
+2. 创建 `{process_slug}/` 目录结构（`.gitkeep` 占位），`.tpl` 模板只读保留在 `.claude/templates/issue-package/` 供 Agent 按需参考生成文档，不复制进工作包。
+3. 写入 `{process_slug}/workflow-stage.yaml`，设置 `issue_number`、`session_id`、`design_id`、`process_slug`，并自动生成 `{process_slug}/documents.yaml` 文档索引。
+4. Commit 初始过程包，可选 `--push` 到远程。
+
+示例：
+
+```bash
+scripts/init-lincoln-branch.sh --issue-number 21 --session-id 2026-07-08-stakeholder --design-id checkout-redesign --push
+```
+
+过程包只存在于 feature branch，不合并到 `main`。

package/framework/.claude/skills/lc-market-research/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-market-research
+description: 分析市场规模、趋势、细分与动态，为产品定位与机会判断提供事实基础。
+version: 1.0.0
+triggers:
+  - "lc-market-research"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/market-research.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-market-research
+
+## Purpose
+
+Using [lc-market-research] to 分析市场规模、趋势、细分与动态，为产品定位与机会判断提供事实基础.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-market-research` 阶段。
+- PM 需要 分析市场规模、趋势、细分与动态，为产品定位与机会判断提供事实基础。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/market-research.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。

package/framework/.claude/skills/lc-market-research/prompts/main.md

@@ -0,0 +1,79 @@
+# lc-market-research prompt
+
+You are executing the Lincoln workflow step `lc-market-research`: analyze the market context for the product decision.
+
+## Goal
+
+Produce `{process_slug}/research/{session_id}/market.md` describing market size, trends, segments, and dynamics.
+
+## 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 research documents.
+2. Define the addressable market:
+   - TAM / SAM / SOM if data is available
+   - Key segments and their growth rates
+3. Identify macro trends (technology, regulation, behavior, economics) that affect the market.
+4. Map the value chain and key players.
+5. Use WebSearch / WebFetch to find authoritative reports and data sources.
+6. Write `market.md` using the template below.
+
+## Output template
+
+```markdown
+# Market Research: <Title>
+
+## Market Definition
+
+<what market are we in and why>
+
+## Market Size
+
+| Metric | Value | Source | Year |
+|--------|-------|--------|------|
+| TAM    | ...   | ...    | ...  |
+| SAM    | ...   | ...    | ...  |
+| SOM    | ...   | ...    | ...  |
+
+## Trends
+
+1. **<Trend 1>** — implication: ...
+2. **<Trend 2>** — implication: ...
+
+## Segments
+
+| Segment | Description | Size | Growth | Key Needs |
+|---------|-------------|------|--------|-----------|
+| ...     | ...         | ...  | ...    | ...       |
+
+## Value Chain
+
+- <step 1>
+- <step 2>
+
+## Sources
+
+- <source 1>
+- <source 2>
+
+## Implications
+
+- <what this means for the product>
+```
+
+## Rules
+
+- Prefer primary or well-known secondary sources (industry reports, official statistics, reputable publications).
+- Flag low-confidence numbers and assumptions.
+- Cite all data points.
+
+## Exit Criteria
+
+- `market.md` is complete with cited sources.
+- At least one trend and one segment are analyzed.

package/framework/.claude/skills/lc-product-research/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-product-research
+description: 研究相关产品/解决方案的能力、价值主张、使用场景与优劣势。
+version: 1.0.0
+triggers:
+  - "lc-product-research"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/product-research.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-product-research
+
+## Purpose
+
+Using [lc-product-research] to 研究相关产品/解决方案的能力、价值主张、使用场景与优劣势.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-product-research` 阶段。
+- PM 需要 研究相关产品/解决方案的能力、价值主张、使用场景与优劣势。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/product-research.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。

package/framework/.claude/skills/lc-product-research/prompts/main.md

@@ -0,0 +1,80 @@
+# lc-product-research prompt
+
+You are executing the Lincoln workflow step `lc-product-research`: research existing products and solutions relevant to the decision.
+
+## Goal
+
+Produce `{process_slug}/research/{session_id}/product.md` analyzing relevant products' capabilities, value propositions, and use cases.
+
+## 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 research documents.
+2. Identify 3-7 relevant products or solution categories.
+3. For each product, research:
+   - Positioning and value proposition
+   - Core capabilities and features
+   - Target users and use cases
+   - Pricing model (if public)
+   - API / integration surface (if relevant)
+4. Use WebSearch / WebFetch / GitHub MCP to gather official information.
+5. Write `product.md` using the template below.
+
+## Output template
+
+```markdown
+# Product Research: <Title>
+
+## Products Analyzed
+
+| Product | Category | Positioning | Target Users | Pricing |
+|---------|----------|-------------|--------------|---------|
+| ...     | ...      | ...         | ...          | ...     |
+
+## Product Profiles
+
+### 1. <Product A>
+
+- **Value proposition:** ...
+- **Core capabilities:** ...
+- **Use cases:** ...
+- **API / integration:** ...
+- **Strengths:** ...
+- **Weaknesses:** ...
+
+### 2. <Product B>
+
+...
+
+## Capability Comparison
+
+| Capability | Product A | Product B | Product C |
+|------------|-----------|-----------|-----------|
+| ...        | ...       | ...       | ...       |
+
+## Sources
+
+- <source 1>
+- <source 2>
+
+## Implications
+
+- <what this means for our product>
+```
+
+## Rules
+
+- Rely on official sources (product websites, docs, API references, pricing pages).
+- Distinguish facts from marketing claims.
+- Note information gaps.
+
+## Exit Criteria
+
+- `product.md` covers at least 3 relevant products.
+- Each product has capabilities and use cases documented with sources.

package/framework/.claude/skills/lc-research-report/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lc-research-report
+description: 整合 PM 研究全流程产物，输出可交付、可沉淀的研究报告。
+version: 1.0.0
+triggers:
+  - "lc-research-report"
+inputs:
+  - name: topic
+    description: 研究主题或产品决策背景
+    required: false
+outputs:
+  - "{process_slug}/research/{session_id}/report.md"
+required_tools:
+  - Bash
+  - Read
+  - Write
+---
+
+# lc-research-report
+
+## Purpose
+
+Using [lc-research-report] to 整合 PM 研究全流程产物，输出可交付、可沉淀的研究报告.
+
+## When to Use
+
+- `pm-research` workflow 的 `lc-research-report` 阶段。
+- PM 需要 整合 PM 研究全流程产物，输出可交付、可沉淀的研究报告。 时。
+
+## Inputs
+
+- `session_id`: 研究 session 标识
+- 当前阶段之前的所有研究产物
+
+## Outputs
+
+- `{process_slug}/research/{session_id}/report.md`
+
+## Rules
+
+- 严格基于已有研究产物，避免引入未经验证的假设。
+- 所有外部事实必须标注来源。
+- human_gate 阶段必须获得人类 PM 显式确认。