# To Spec

Turn the current conversation into a spec and publish it to the project issue tracker, ...

- Repository: https://github.com/rpamis/comet (3263 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rpamis/comet --skill to-spec -g -a claude-code -y`
Codex: `npx skills add rpamis/comet --skill to-spec -g -a codex -y`
Cursor: `npx skills add rpamis/comet --skill to-spec -g -a cursor -y`
Gemini CLI: `npx skills add rpamis/comet --skill to-spec -g -a gemini-cli -y`

## Description

Turn the current conversation into a spec and publish it to the project issue tracker, no interview, just synthesis of what you've already discussed.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user, just synthesize what you already know.

The issue tracker and triage label vocabulary should have been provided to you, run `/setup-matt-pocock-skills` if not.

## Process

1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.

2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.

<spec-template>

## Problem Statement

The problem that the user is facing, from the user's perspective.

## Solution

The solution to the problem, from the user's perspective.

## User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

1. As an <actor>, I want a <feature>, so that <benefit>

<user-story-example>
1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>

This list of user stories should be extremely extensive and cover all aspects of the feature.

## Implementation Decisions

A list of implementation decisions that were made. This can include:

- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific intera

The rest: https://github.com/rpamis/comet/blob/HEAD/eval/archives/grill-test-20261013/application/skills/to-spec/SKILL.md