Agent skill

Speckit Baseline

Generate feature specifications by analyzing existing source code.

AGPL-3.0Auto-check passedDevelopment

Install Speckit Baseline

skills CLI

$ npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install dceoy/speckit-agent-skills speckit-baseline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/speckit-baseline .claude/skills/speckit-baseline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "speckit-baseline" agent skill from https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline into .claude/skills/speckit-baseline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-baseline", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install dceoy/speckit-agent-skills speckit-baseline --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/speckit-baseline .agents/skills/speckit-baseline && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "speckit-baseline" agent skill from https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline into .agents/skills/speckit-baseline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-baseline", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install dceoy/speckit-agent-skills speckit-baseline --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/speckit-baseline .cursor/skills/speckit-baseline && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "speckit-baseline" agent skill from https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline into .cursor/skills/speckit-baseline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-baseline", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/dceoy/speckit-agent-skills.git --path skills/speckit-baseline

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install dceoy/speckit-agent-skills speckit-baseline --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/speckit-baseline .gemini/skills/speckit-baseline && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "speckit-baseline" agent skill from https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline into .gemini/skills/speckit-baseline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-baseline", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install dceoy/speckit-agent-skills speckit-baseline

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/speckit-baseline .github/skills/speckit-baseline && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "speckit-baseline" agent skill from https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline into .github/skills/speckit-baseline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-baseline", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install dceoy/speckit-agent-skills speckit-baseline --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/speckit-baseline .opencode/skills/speckit-baseline && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "speckit-baseline" agent skill from https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline into .opencode/skills/speckit-baseline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-baseline", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: speckit-baseline
GitHub stars: 146
Token cost: ~1.1k tokens
SKILL.md length: 552 words
Files: 1
Skills in repo: 2
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Generate feature specifications by analyzing existing source code.

Works in 10 steps: Parse target input: Identify files,… → Discover and read source files → Analyze code structure → …
Tasks that involve Spec-driven development
SKILL.md covers When to Use, Inputs, Goal and Workflow, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Speckit Baseline is an agent skill from dceoy/speckit-agent-skills. Generate feature specifications by analyzing existing source code.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Spec-driven development. The repository describes itself as: Agent skills for Spec Kit. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve Spec-driven development

Example prompts

“/speckit-baseline”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

Parse target input: Identify files, directories, or patterns to analyze.
Discover and read source files
Analyze code structure
Generate a short name (2-4 words) from the analyzed code
Create the feature branch and spec file
Load the spec template from .specify/templates/spec-template.md.
Draft the specification using the template structure
Abstract implementation details
Create spec quality checklist at FEATURE_DIR/checklists/requirements.md.
Report completion with

What it can do on your machine

Read from SKILL.md and the folder at commit 52e6e7d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Speckit Baseline loads about 1.1k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 552 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~21
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dceoy/speckit-agent-skills at commit 52e6e7d, republished under its AGPL-3.0 licence (© dceoy). 552 words, ~1,121 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-baseline/SKILL.md (or your agent's skills folder).

name: speckit-baseline
description: Generate feature specifications by analyzing existing source code.

Spec Kit Baseline Skill

When to Use

You need a spec for existing or legacy code.
You want to document a feature before refactoring.
You inherited a codebase without written requirements.

Inputs

A target path, file list, or glob pattern describing the code to analyze.
Repo context with .specify/ scripts and templates.

If the target is missing or ambiguous, ask a focused question before continuing.

Goal

Generate a technology-agnostic spec for existing code, then create the feature branch/spec file using the standard Spec Kit templates.

Workflow

Parse target input: Identify files, directories, or patterns to analyze.
- Accept file paths, glob patterns, or directory paths.
- If empty: stop and ask for a concrete target.
Discover and read source files:
- Expand globs to a file list.
- Read file contents for analysis.
- Identify primary language(s) and frameworks.
- Map key file relationships and dependencies.
Analyze code structure:
- Identify entry points and public interfaces.
- Extract function/method signatures and behaviors.
- Find data models and entities.
- Detect API endpoints and routes.
- Identify user-facing functionality.
Generate a short name (2-4 words) from the analyzed code:
- Use action-noun format (e.g., "user-auth", "payment-processing").
- Base on primary functionality discovered.
- Preserve technical terms where meaningful.
Create the feature branch and spec file:
- Find the highest existing feature number for this short name (branches/specs).
- Run .specify/scripts/bash/create-new-feature.sh --json with the calculated number and short name.
- Read BRANCH_NAME, FEATURE_DIR, and SPEC_FILE paths from the script JSON output.
- For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
Load the spec template from .specify/templates/spec-template.md.
Draft the specification using the template structure:
- User Stories: Infer from user-facing code paths and interactions.
- Acceptance Scenarios: Derive from validation logic, error handling, and tests.
- Functional Requirements: Extract from business rules and constraints.
- Key Entities: Identify from data models and schemas.
- Success Criteria: Infer from metrics, logging, or performance-related code.
- Assumptions: Document inferences made during analysis.
Abstract implementation details:
- Convert technical patterns to user-focused requirements.
- Remove framework-specific terminology.
- Focus on WHAT the code does, not HOW it does it.
Create spec quality checklist at FEATURE_DIR/checklists/requirements.md.
Report completion with:
- Branch name and spec file path.
- Summary of analyzed files.
- Key features discovered.
- Areas needing clarification or review.

Show full SKILL.md (177 more words)Show less

Outputs

specs/<feature>/spec.md
specs/<feature>/checklists/requirements.md

Key rules

Focus on extracting WHAT and WHY from HOW.
Abstract away implementation details in the generated spec.
Document assumptions made during code analysis.
Flag areas where code behavior is unclear.
Preserve discovered business rules and constraints.
Use [NEEDS CLARIFICATION] for ambiguous code sections (max 3).
Generated specs should be validated by someone who knows the feature.

Examples

Code Pattern → Spec Requirement:

if (user.role === 'admin') → "System MUST restrict action to administrator users"
password.length >= 8 → "Passwords MUST be at least 8 characters"
cache.set(key, value, 3600) → "System MUST cache results for improved performance"
try { ... } catch (e) { notify(e) } → "System MUST notify users when errors occur"

Code Pattern → User Story:

Login endpoint with OAuth → "As a user, I can sign in using my social account"
Shopping cart logic → "As a customer, I can add items to my cart for later purchase"
Report generation → "As an analyst, I can generate reports on system activity"

Next Steps

After generating spec.md:

Clarify with domain experts using speckit-clarify.
Plan modernization/refactoring with speckit-plan.
Compare the generated spec with actual requirements to identify gaps.

Files

Just SKILL.md in skills/speckit-baseline of dceoy/speckit-agent-skills.

Open the folder on GitHubat commit 52e6e7d

Compare with similar skills

Speckit Baseline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Speckit Baseline compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Speckit Baseline this skilldceoy/speckit-agent-skills	146	—	~1.1k	Automated safety check: Pass	AGPL-3.0	10 days ago
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec	71k	2 repos	~5.6k	Automated safety check: Pass	MIT	today
Speckit ConstitutionWeihanLi/WeihanLi.Common	242	11 repos	~2.1k	Automated safety check: Pass	Apache-2.0	24 days ago
Speckit Plankunstmusik/blue	154	18 repos	~2.1k	Automated safety check: Pass	GPL-3.0	today
Speckit Specifykunstmusik/blue	154	18 repos	~4.7k	Automated safety check: Pass	GPL-3.0	today
Review Spdzhu1090093659/spec_driven_develop	985	—	~1.5k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

OpenSpec Bulk Change Archiver
Fission-AI/OpenSpec
Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.
71k GitHub starsUsed in 2 repos~5.6k tokens
DevelopmentAuto-check passed
Speckit Constitution
WeihanLi/WeihanLi.Common
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
242 GitHub starsUsed in 11 repos~2.1k tokens
DevelopmentAuto-check passed
Speckit Plan
kunstmusik/blue
Execute the implementation planning workflow using the plan template to generate design artifacts.
154 GitHub starsUsed in 18 repos~2.1k tokens
DevelopmentAuto-check passed
Speckit Specify
kunstmusik/blue
Create or update the feature specification from a natural language feature description.
154 GitHub starsUsed in 18 repos~4.7k tokens
DevelopmentAuto-check passed
Review Spd
zhu1090093659/spec_driven_develop
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
985 GitHub stars~1.5k tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Speckit Tasks
kunstmusik/blue
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
154 GitHub starsUsed in 18 repos~3k tokens
DevelopmentAuto-check passed

Questions about Speckit Baseline

What does Speckit Baseline do?

Generate feature specifications by analyzing existing source code. Speckit Baseline is an agent skill from dceoy/speckit-agent-skills. Generate feature specifications by analyzing existing source code.

When should I use Speckit Baseline?

Speckit Baseline fits situations like: tasks that involve Spec-driven development.

How do I install Speckit Baseline in Claude Code?

Run `npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a claude-code`. Or copy the skill folder (skills/speckit-baseline in dceoy/speckit-agent-skills) into .claude/skills/speckit-baseline in your project. Claude Code loads it when a task matches its description.

How do I install Speckit Baseline in Codex?

Run `npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a codex`. Or copy the skill folder (skills/speckit-baseline in dceoy/speckit-agent-skills) into .agents/skills/speckit-baseline in your project. Codex loads it when a task matches its description.

Can I use Speckit Baseline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dceoy/speckit-agent-skills --skill speckit-baseline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-baseline, .gemini/skills/speckit-baseline, .github/skills/speckit-baseline and .opencode/skills/speckit-baseline in your project.

What does Speckit Baseline need to run?

SKILL.md names no scripts, command-line tools or credentials: Speckit Baseline is instructions for the agent only.

Does Speckit Baseline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Speckit Baseline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Speckit Baseline use?

Speckit Baseline is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Speckit Baseline use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Speckit Baseline?

Skills that share tags, products or a category with Speckit Baseline: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Speckit Plan (kunstmusik/blue, 154 stars) and Speckit Specify (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Baseline?

dceoy (a GitHub user) maintains it in dceoy/speckit-agent-skills, which has 146 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 28, 2026.

Source: dceoy/speckit-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Speckit Baseline

Install Speckit Baseline

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Spec Kit Baseline Skill

When to Use

Inputs

Goal

Workflow

Outputs

Key rules

Examples

Next Steps

Files

Compare with similar skills

Similar skills

OpenSpec Bulk Change Archiver

Speckit Constitution

Speckit Plan

Speckit Specify

Review Spd

Speckit Tasks

More from dceoy/speckit-agent-skills

Claude Command Converter

Questions about Speckit Baseline

Install Speckit Baseline

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Spec Kit Baseline Skill

When to Use

Inputs

Goal

Workflow

Outputs

Key rules

Examples

Next Steps

Files

Compare with similar skills

Similar skills

OpenSpec Bulk Change Archiver

Speckit Constitution

Speckit Plan

Speckit Specify

Review Spd

Speckit Tasks

More from dceoy/speckit-agent-skills

Claude Command Converter

Related

Questions about Speckit Baseline