# speckit-baseline

This skill reads your source files and turns them into a framework-agnostic feature spec with user stories and requirements. Useful when a codebase exists but written requirements do not.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1500 installs · ★ 153
- Author: dceoy
- License: AGPL-3.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/dceoy/speckit-agent-skills/tree/HEAD/skills/speckit-baseline/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/speckit-baseline

## What it does

You point the skill at a path, a file list or a glob pattern. It expands the pattern, opens the files and maps the structure: entry points, public interfaces, function signatures, data models, API routes. Language and framework come from the code itself. Then it picks a 2–4 word action-noun name and runs `.specify/scripts/bash/create-new-feature.sh --json` to create the feature branch and spec file, loading the template from `.specify/templates/spec-template.md`.

The draft covers user stories, acceptance scenarios, functional requirements, key entities and success criteria. Implementation details get abstracted: a check like `user.role === 'admin'` becomes a rule that only administrators may perform the action. Unclear spots are marked `[NEEDS CLARIFICATION]`, at most 3 at a time. Inferences made during analysis go into the assumptions section, and a quality checklist lands at `FEATURE_DIR/checklists/requirements.md`.

You need a repo with `.specify/` set up, scripts and templates included. An empty or vague target stops the skill, which then asks a focused question. Someone who knows the feature has to review the result, because a misinterpreted branch or route ends up as a wrong requirement. After that, `speckit-clarify` and `speckit-plan` pick up the spec for open questions and refactoring plans.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/speckit-baseline/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/speckit-baseline/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/speckit-baseline/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/speckit-baseline/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install dceoy/speckit-agent-skills speckit-baseline
```

2. **Manually: put the files in place**
- File: `.github/skills/speckit-baseline/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/dceoy/speckit-agent-skills --path skills/speckit-baseline
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/speckit-baseline/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/dceoy/speckit-agent-skills/tree/HEAD/skills/speckit-baseline/SKILL.md

## When to use it
- document an inherited codebase that has no written requirements
- capture a feature's behaviour before refactoring it
- recover business rules from conditionals in code
- turn API routes and data models into formal requirements
- flag code paths whose intent is unclear

## Example prompts
- Generate a spec from `src/auth/` and list what needs clarification
- Analyze `src/services/*.ts` and create a feature branch for the payments spec
- Turn the legacy `legacy/orders.py` module into a specification

## Similar
- [grill-with-docs](https://affpapa.org/en/nevibecode/skills/grill-with-docs.md) — skill · 1219756 installs
- [skill-creator](https://affpapa.org/en/nevibecode/skills/skill-creator.md) — skill · 414180 installs
- [setup-matt-pocock-skills](https://affpapa.org/en/nevibecode/skills/setup-matt-pocock-skills.md) — skill · 1052851 installs
- [handoff](https://affpapa.org/en/nevibecode/skills/handoff.md) — skill · 1038491 installs
- [triage](https://affpapa.org/en/nevibecode/skills/triage.md) — skill · 990453 installs
- [domain-modeling](https://affpapa.org/en/nevibecode/skills/domain-modeling.md) — skill · 876391 installs

From the same set: [dceoy/speckit-agent-skills](https://affpapa.org/en/nevibecode/by/dceoy/speckit-agent-skills.md) — 11 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md