Comet Open
Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).
Install
npx skills add rpamis/comet --skill comet-opengit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/039-release/comet-classic-039-open ~/.claude/skills/comet-openPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Comet Phase 1: Open ## Prerequisites - No active change, or user wants to create a new change ## Steps ### 0. Output Language Constraint Every prompt and artifact request passed to OpenSpec must include the output-language constraint: use the language of the user request that triggered this workflow. When resuming an existing change with a clear dominant artifact language, preserve that language unless the user explicitly asks to switch. ### 1. Explore Ideas and Clarify Requirements **Immediately execute:** Use the Skill tool to load the `openspec-explore` skill. Skipping this step is prohibited. After the skill loads, explore the problem space following its guidance, but do not treat one Q&A turn as sufficient clarification. You must continue asking, align with the user, and form a clarification summary covering: - Goals: the problem the user truly wants to solve and the expected outcome - Non-goals: what is explicitly out of scope for this change - Scope boundaries: included/excluded modules, users, platforms, or data - Key unknowns: unresolved assumptions, risks, or dependencies - Draft acceptance scenarios: at least the core success scenario and important boundary scenarios The clarification summary must include: goals, non-goals, scope boundaries, key unknowns, and draft acceptance scenarios. ### 1a. PRD Split Preflight (Blocking Point)
Details
- Skill name
comet-open- Repository
- rpamis/comet
- Path
eval/local/skills/benchmarks/039-release/comet-classic-039-open/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Comet Open skill do?
Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).
How do I install the Comet Open skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill comet-open. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comet Open popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Comet Open
3.3krpamis/comet
Use when Comet 需要创建新的 OpenSpec change,或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。
Comet Memory
3.3krpamis/comet
Use when Comet must decide whether a bounded semantic review packet contains a personal memory worth creating, updating, forgetting, or skipping.
Comet Tweak
3.3krpamis/comet
使用 Classic 预设流程完成单个 change 的轻量调整。在用户明确调用 /comet-tweak、选择 tweak,或恢复 workflow: tweak 时使用。
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.