Assess Comet GitHub issues against current requirements, code, tests, and installation behavior. Classify reports as defects, configuration problems, duplicates, or feature requests, then summarize supporting evidence, uncertainty, and recommended next steps.
- Checking whether a reported bug can be reproduced
- Distinguishing installation problems from product defects
- Finding duplicate issues or already implemented behavior
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Close a verified development change by merging specification updates into the main specifications. Annotate design and planning documents, then move the change into an archive, with a preview option and user confirmation before execution.
- Archive a verified development change
- Merge specification updates into the main specifications
- Preview archive actions before execution
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Turn existing OpenSpec change documents into a detailed technical design. The skill guides clarification, compares implementation options, and records risks and testing plans, then creates a design document after user approval and prepares the implementation handoff.
- Develop a high-level proposal into a technical design
- Compare implementation options and testing strategies
- Resume design work from saved handoff documents
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Create or upgrade Comet workflow skills from a description of the desired process and available local skills. Define each step’s responsibilities, required outputs, and checks, then generate the skill package and assess its evaluation results and publication readiness.
- Customize the five phases of Comet Classic
- Create a workflow using existing local skills
- Add outputs and checks to an existing Comet workflow
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Turn a development idea into an OpenSpec proposal, design document, and task checklist. Clarify goals and acceptance scenarios through discussion, assess whether large plans need splitting, and initialize the Comet workflow after user confirmation.
- Clarifying requirements before starting development
- Splitting a large product plan into independent changes
- Creating a proposal, design document, and task checklist
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Guides development from requirements through implementation, independent checks, and delivery. Stores requirements, progress, and acceptance results in the project so the agent can resume interrupted work and continue within the scope the user has confirmed.
- Clarifying requirements and acceptance criteria
- Resuming interrupted development
- Checking implementation against every acceptance criterion
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Guide software changes through scope definition, design, implementation, verification, and archiving with OpenSpec and Superpowers. Recorded workflow state helps resume unfinished work, while hotfix and tweak paths support smaller changes with required user decisions.
- Start a software change with clear scope and specifications
- Resume an interrupted Classic change
- Choose a hotfix or tweak path for a small change
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Diagnose Comet Hook, installation, routing, and runtime problems by checking actual packaged execution paths. The skill separates configuration issues, mismatched generated files, and source defects, then reports evidence and the smallest next step without changing the installation or code.
- Investigate Hook or installation failures
- Separate configuration problems from code defects
- Compare generated runtime files with source code
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Carry an approved Comet design into an implementation plan, code changes, tests, and required reviews. It tracks task acceptance and recovery records so unfinished development can resume using the confirmed execution strategy.
- Implementing tasks from an approved design
- Choosing execution, testing, and review options
- Resuming unfinished development from recorded progress
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Handle small or medium changes, such as configuration or prompt updates, through a single OpenSpec change. This workflow connects planning documents, implementation, verification, and archiving, with user decisions when scope grows or final approval is needed.
- Adjusting project configuration
- Improving documentation or prompts
- Updating existing requirements and acceptance scenarios
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Carry out focused configuration, documentation, or prompt changes through a single OpenSpec change. Create concise planning documents, implement tasks, run verification, and prepare archiving, with support for specification updates and user decisions when scope grows.
- Making a focused configuration change
- Improving documentation or prompts
- Implementing an adjustment defined by a specification
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Start a Comet change by clarifying goals, scope, exclusions, and acceptance scenarios. Assess whether larger requests need splitting, then create OpenSpec proposal, design, and task documents alongside the Comet state file for user review.
- Clarifying requirements before development
- Splitting a large product requirements document into changes
- Creating proposal, design, and task documents
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Guides development from requirements through implementation, independent checks, and delivery. Stores requirements, progress, and acceptance results in the project so the agent can resume interrupted work and continue within the scope the user has confirmed.
- Clarifying requirements and acceptance criteria
- Resuming interrupted development
- Checking implementation against every acceptance criterion
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Route Comet GitHub requests to the right workflow for PR review, issue assessment, idea submission, CI failure diagnosis, or issue implementation. Clarify the requested scope and explain the evidence behind the recommended next action.
- Choose the right workflow for an Issue or PR
- Route a bug report for evidence-based assessment
- Find the workflow for diagnosing failed automated checks
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Handle existing behavior bugs through a streamlined workflow covering change records, implementation, tests, verification, and archiving. Check that the root cause is removed and ask for a decision when the repair expands in scope.
- Fix a bug in an existing feature
- Track a repair from change creation through verification
- Check whether the root cause has been removed
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Create or resume an implementation plan after design is complete. Choose workspace isolation, execution method, testing approach, and review depth, then track tasks and specification updates until the change is ready for verification.
- Create an implementation plan from a completed design
- Adjust code review depth to the change
- Choose test-first or direct implementation
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Guide a development change through requirements, design, implementation, verification, and archiving. Comet combines OpenSpec for specifications with Superpowers for technical work, detects the current phase, and routes the agent to the appropriate next step.
- Starting a development change with a structured workflow
- Resuming work from its recorded development phase
- Routing a bug fix or small adjustment to a preset
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Review the selected Comet change without modifying files or advancing the workflow. Compare implementation differences with requirements, report concrete correctness and security issues, and explain review scope, available test evidence, and remaining uncertainties.
- Reviewing a selected Comet change on demand
- Checking implementation differences against requirements
- Inspecting security and edge-case risks
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Turn an approved design into an implementation plan, then carry out its tasks using a chosen workspace and execution method. Track progress, apply the selected testing approach, and complete checks before handing the change to verification.
- Create an implementation plan from a design document
- Choose a branch or separate Git working directory
- Choose test-first or direct implementation
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Routes a Comet request to the Native or Classic workflow based on project settings. When project settings are missing, it saves the global defaults locally so later changes to those defaults do not alter the project's choice.
- Start a workflow with /comet
- Use the workflow selected in project settings
- Save default workflow settings for a new project
rpamis/comet☆ 3.2KUpdated Oct 25, 2026
Have Codex implement a defined work order, then have Claude independently inspect the changes and run verification checks. The workflow records evidence and limitations, bounds correction rounds, and requires updated reviews when later edits change the result.
- Implementing a defined work order with Codex
- Getting an independent Claude review of Codex changes
- Recording verification evidence and limitations
chaseai-yt/claudex-loop☆ 3.2KUpdated Oct 15, 2026
Strengthen implementation plans through guided questions, checks against project terminology and design decisions, and repeated Codex reviews. Produce an agreed plan, updated documentation, and a review log before the user approves coding.
- Check a plan against established project terminology
- Clarify ambiguous requirements before implementation
- Review a high-stakes plan with a second AI model
chaseai-yt/claudex-loop☆ 3.2KUpdated Oct 15, 2026
Clarify an implementation plan through one question at a time with Claude, then have Codex challenge its assumptions in read-only reviews. Repeated revisions produce a documented plan and review log for the user's approval before coding.
- Clarify ambiguous requirements before implementation
- Review plans for authentication, payments, or migrations
- Challenge a plan with a second model
chaseai-yt/claudex-loop☆ 3.2KUpdated Oct 15, 2026
Choose a suitable model and role for work in Claude Code or Codex, from a second opinion to focused debugging or delegation. Prepare a scoped handoff and, when requested, execute it once and verify the result.
- Choosing a model and role for a task
- Getting another perspective on a plan or implementation
- Investigating a blocker after repeated failed attempts
chaseai-yt/claudex-loop☆ 3.2KUpdated Oct 15, 2026