AugmentClaude

Comet Open

Explore ideas and clarify requirements to create a structured change proposal.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/comet-open-rpamis/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Use when kicking off a new change — explores the idea, clarifies requirements, and creates a structured change proposal.

What this skill does

This skill guides you through the initial phase of structured change management, helping you explore ideas thoroughly and produce a clear proposal document.

Comet Open is the entry point for creating a new change. It walks you through requirement exploration, ensures your scope is well-defined, and produces three foundational artifacts: a proposal (the "why" and "what"), a design summary (the "how" at a high level), and a task list. The skill enforces decision checkpoints at key moments—such as when confirming requirements are clear, choosing a change name, and reviewing the final documents—to prevent ambiguity from creeping into later phases.

What it does

  • Explores your idea and clarifies requirements by loading the openspec-explore skill, asking you targeted questions about goals, non-goals, scope boundaries, known unknowns, and acceptance scenarios.
  • Detects large or multi-faceted requests and optionally recommends splitting them into multiple independent changes before proceeding.
  • Confirms requirement clarity with you before creating any artifacts, ensuring the scope is locked down.
  • Generates three core documents:
    • proposal.md (problem, goals, scope, non-goals)
    • design.md (high-level architecture, approach choices)
    • tasks.md (checklist of work items)
  • Initializes change state by creating .openspec.yaml, .comet.yaml, and the change directory structure.
  • Pauses for your review and sign-off on all three documents before automatically advancing to the design phase.

How to use it

Trigger /comet-open when you have a new idea or feature you want to propose. Bring a description of what you're trying to accomplish—as detailed or rough as you like. The skill will lead you through a series of questions to clarify the problem, scope, and success criteria. At each major decision point (requirement confirmation, change name selection, and final document review), the skill will pause and ask you to confirm before moving forward. Once you approve the three documents, the skill applies state guards and automatically transitions the change into the design phase.

Note: this skill's internal instructions are written in Chinese. Claude reads them natively and will work with you in English.

Related skills