create-spec

name	create-spec
description	use this skill when the user ask you to create the spec file or to create the specification plan(spec.md).

Create Specification

Help user Create the spec.md file for a new feature or change. Always follow the rules in Gemini.md.

step 0 - Interactive Interview Phase

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time using the ask_question tool that will show the user ui so its easy for user to answer these questions, waiting for feedback on each question before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Domain awareness

During codebase exploration, also look for existing documentation:

File structure

Most repos have a single context:

/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:

/
├── CONTEXT-MAP.md
├── docs/
│   └── adr/                          ← system-wide decisions
├── src/
│   ├── ordering/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/                 ← context-specific decisions
│   └── billing/
│       ├── CONTEXT.md
│       └── docs/adr/

Create files lazily — only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"

Update CONTEXT.md inline

When a term is resolved, update CONTEXT.md right there. Don't batch these up — capture them as they happen. Use the format in CONTEXT-FORMAT.md.

CONTEXT.md should be totally devoid of implementation details. Do not treat CONTEXT.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

1. Hard to reverse — the cost of changing your mind later is meaningful
2. Surprising without context — a future reader will wonder "why did they do it this way?"
3. The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.

Step 1 — Check working directory is clean

Run git status and check for uncommitted, unstaged, or untracked files. If any exist, stop immediately and tell the user to commit or stash changes before proceeding. DO NOT CONTINUE until the working directory is clean.

Step 2 — setup the git branch

Create a new git branch for the feature. The branch name should follow this format: feature/[ID]-[feature-name-kebab-case]

Where:

1. step_number — zero-padded to 2 digits: 2 → 02, 11 → 11

2. feature_title — human readable title in Title Case

   • Example: "Registration" or "Login and Logout"

3. feature_slug — git and file safe slug

   • Lowercase, kebab-case
   • Only a-z, 0-9 and -
   • Maximum 40 characters
   • Example: registration, login-logout

4. branch_name — format: feature/<feature_slug>

   • Example: feature/registration

If you cannot infer these from user input, ask the user to clarify before proceeding.

Step 4 — Switch to main and pull latest

Run:

git checkout main
git pull origin main

Step 5 — Create and switch to the feature branch

Run:

git checkout -b <branch_name>

Step 6 — Research the codebase

Read these files before writing the spec:

• Gemini.md — Global and project read both.
• All files in .agents/specs/ — avoid duplicating existing specs

Step 7 — Write the spec

Generate a spec document with this exact structure:

read EXAMPLE.md. this example file contains the ui chat sidebar spec example try to create the spec just like that