Run a Thread discussion with several members to compare perspectives, options or tradeoffs and produce shared notes. Applies to the host and invited contributors throughout that discussion; excludes solo work, unrelated messages and closed discussions.
Installs into .claude/skills of the current project.
Are you the author of Campfire?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/murray17-campfire)
---
name: campfire
description: Run a Thread discussion with several members to compare perspectives, options or tradeoffs and produce shared notes. Applies to the host and invited contributors throughout that discussion; excludes solo work, unrelated messages and closed discussions.
---
# Campfire
The current Default Lead hosts independent views, at most one focused response round, then one final set of notes. Public messages make this an independent discussion, not a blind review. Use the user's language for prose and template headings.
## Roles
| Current input | Action |
| --- | --- |
| User directly asks the current Default Lead to host | Follow [Lead](references/lead.md) |
| Ordinary member receives a user broadcast or a call that also reaches the Lead | Follow [Member](references/member.md); wait for a formal invitation |
| Member receives this discussion's independent-view or response request | Follow [Member](references/member.md); return one complete result |
| Host receives an invited member's current-round reply | Follow [Lead](references/lead.md) |
| Notes, late contributions or unrelated messages | Do not restart the discussion |
Use trusted roles and request/reply relationships, not message titles. One Lead may host only one unfinished Campfire per Thread. This workflow needs at least two contributors and is not for sustained two-person questioning or strict information isolation.
## Discussion bounds
- Round 1: invite 2-3 members in one multi-recipient message.
- Round 2: optional, once, with 1-2 members addressing one disagreement that could change the conclusion.
- Each member returns one complete result per round. After round 2, publish the final [Notes](references/notes.md); no extra clarification round.
- User requests to stop, replace the topic, remove a member or summarize now take precedence. Late views do not reopen published notes.
## Member reply contract
Include a core judgment, two main reasons, the most important risk/limit, what would change the judgment, and confidence. For Chinese, aim for 200-250 characters, at most 300; use comparable brevity in other languages.
Return the full result to the requester once. Omit repeated background, other members' views, acknowledgements and progress. Contributors do not recruit others, summarize the whole discussion or start another round.
