ljg-roundtable

lijigang/ljg-skills · updated May 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/lijigang/ljg-skills --skill ljg-roundtable
0 commentsdiscussion
summary

为了执行本项技能,请严格按照以下步骤操作:

skill.md

Usage

Instructions

为了执行本项技能,请严格按照以下步骤操作:

  1. 读取参考资料 读取 ~/.claude/skills/ljg-roundtable/references/original-prompt.org 了解原始框架设计意图。

  2. 解析议题 从用户输入中提取核心议题。如果用户只说"圆桌讨论"未给议题,询问议题。

  3. 选人:提议代表人物 根据议题,选择 3-5 位真实历史/当代人物作为代表,覆盖尽可能多的立场维度。每位人物需要:

    • 姓名(真实人物,非虚构)
    • MBTI 人格类型
    • 核心立场(一句话)
    • 选择理由(为什么此人对此议题有独特视角)

    选人原则:

    • 立场必须形成张力网络(非简单正反方)
    • 优先选择在该领域有经典著作或知名言论的人物
    • 至少包含一位"意外视角"——来自议题本身领域之外的人
  4. 开场:统一定义 以主持人身份开场,展示参会人物列表,然后提出定义性问题

    「在深入探讨之前,我们应当如何定义 [议题核心概念]?它的核心要素是什么?」

    每位参会者依次发言,格式为:

    【人物名】【行动标签】:发言内容
    
    **简言之**:一句话总结
    

    行动标签包括:陈述质疑补充反驳修正综合

  5. 对话循环 每轮执行以下流程:

    5a. 动态发言轮

    • 不是每人固定说一次——根据讨论动态决定谁该发言
    • 每人发言必须是对前面发言的回应(质疑/补充/反驳),不许自说自话
    • 每段发言末尾必须有 **简言之**: 一句话压缩

    5b. 主持人综述 发言结束后,主持人做三件事:

    • 提炼本轮核心争议点(不是面面俱到,而是找到最深的裂缝)
    • 生成ASCII 思考框架图(拓扑图/矩阵/光谱/树形——选最贴合本轮结构的形式)
    • 提出下一层引导问题(从核心争议中生长出来的更深问题)

    ASCII 图的设计原则:

    • 高度概括本轮讨论的结构,不是复述内容
    • 标出正/负反馈环、因果链、张力维度
    • 形式不固定:可以是 2x2 矩阵、光谱轴、因果环路、层级树——哪种最见骨用哪种

    5c. 用户指令 综述后展示指令菜单:

    【主持】:(指令: 可 / 止 / 深入此节 / 引入新人物)
    

    指令含义:

    • :接受下一层问题,继续推进
    • :结束讨论,进入总结
    • 深入此节:不推进新问题,继续围绕当前争议点深挖
    • 引入新人物:用户指定一位新人物加入(主持人介绍并请其就当前话题表态)
  6. 结束:生成知识网络 用户发出 指令后:

    • 主持人做全局总结
    • 生成完整知识网络 ASCII 图:标出所有关键概念、立场、争议点及其关系
    • 列出未解决的开放问题(讨论中暴露但未穷尽的方向)
  7. 写入 org 文件(完整保存,一字不差) 将讨论全部原文写入 org-mode 文件,不压缩、不删减、不改写任何发言内容:

    1. 运行 date +%Y%m%dT%H%M%S 获取时间戳
    2. 写入 ~/Documents/notes/{timestamp}--圆桌-{议题关键词}__roundtable.org
    3. org 文件结构:
      #+title: 圆桌:{议题}
      #+date: [{日期}]
      #+filetags: :roundtable:
      * 议题与参会者
      [完整的参会者介绍,包括姓名、MBTI、立场、选择理由]
      * 开场:定义
      [主持人开场词 + 每位参会者的完整定义性发言,原文照录]
      * 各轮讨论记录
      ** 第 N 轮:{引导问题}
      *** 发言记录
      [本轮所有发言的完整原文,包括行动标签、全部论述、简言之]
      *** 主持人综述
      [核心争议点 + ASCII 框架图 + 下一层引导问题,原文照录]
      * 知识网络(全局)
      [完整的全局总结 + ASCII 知识网络图]
      * 开放问题
      [所有未解决的开放问题]
      
      关键要求:每一段发言、每一个 ASCII 图、每一句主持人综述,都必须完整保留原文,禁止摘要或压缩。
    4. 向用户报告文件路径

主持人行为准则

  • 理性之锚:冷静客观,不偏向任何一方
  • 挖深不铺广:每轮只追一条最深的裂缝,不面面俱到
  • 求真 > 和谐:鼓励尖锐但有建设性的交锋,拒绝表面共识
  • 元认知:在综述中暴露讨论的结构(假设、前提、推理链),不只复述内容

参会者行为准则

  • 必须忠于其真实思想体系发言,不是泛泛而谈
  • 引用/化用其经典著作或知名观点
  • 发言有锋芒:质疑要见骨,补充要推进,不说正确的废话
  • 每段结尾 **简言之** 一句话压到极致
how to use ljg-roundtable

How to use ljg-roundtable on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ljg-roundtable
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lijigang/ljg-skills --skill ljg-roundtable

The skills CLI fetches ljg-roundtable from GitHub repository lijigang/ljg-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ljg-roundtable

Reload or restart Cursor to activate ljg-roundtable. Access the skill through slash commands (e.g., /ljg-roundtable) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.770 reviews
  • Shikha Mishra· Dec 28, 2024

    We added ljg-roundtable from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ishan Brown· Dec 28, 2024

    ljg-roundtable has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Mia Zhang· Dec 20, 2024

    Registry listing for ljg-roundtable matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ishan Smith· Dec 8, 2024

    I recommend ljg-roundtable for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mia Patel· Dec 4, 2024

    Solid pick for teams standardizing on skills: ljg-roundtable is focused, and the summary matches what you get after install.

  • Xiao Farah· Dec 4, 2024

    ljg-roundtable is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Kiara Srinivasan· Dec 4, 2024

    ljg-roundtable reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Hana Kapoor· Nov 27, 2024

    Useful defaults in ljg-roundtable — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ishan Srinivasan· Nov 23, 2024

    Registry listing for ljg-roundtable matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mia Sethi· Nov 23, 2024

    Keeps context tight: ljg-roundtable is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 70

1 / 7