/spec-init#

Initialize a new spec workspace in .specs/.

Usage#

Claude Code:

/spec-init "user authentication with email and password"

Antigravity:

/spec-init "user authentication with email and password"
# or
@spec-init "user authentication with email and password"

Description#

/spec-init is the first step of the CafeKit Spec workflow.

It creates a new folder at .specs/[feature-name]/ and initializes:

• spec.json (phase + approval metadata)
• requirements.md (project description input placeholder)

What Happens#

1. Generate feature name from your description
2. Create .specs/[feature-name]/
3. Write initial spec.json
4. Write initial requirements.md with your project description

Example Output#

> /spec-init "user authentication with email and password"

✅ Created: .specs/user-authentication/
✅ Created: .specs/user-authentication/spec.json
✅ Created: .specs/user-authentication/requirements.md

requirements.md starts with:

# Requirements Document

## Project Description (Input)
User authentication with email and password

## Requirements
<!-- Will be generated in /spec-requirements phase -->

Notes#

• Feature names are generated in kebab-case
• This phase only initializes structure and metadata
• Requirements/design/tasks are generated in later phases

Next Steps#

• /spec-requirements - Generate detailed requirements from the project description