speckit-baseline

Analyze source code to generate feature specifications with user stories and acceptance criteria.

120|25|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/dceoy/speckit-agent-skills --skill speckit-baseline-dceoy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-baseline
Source: https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-baseline
Command: npx skills add https://github.com/dceoy/speckit-agent-skills --skill speckit-baseline-dceoy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate feature specifications by analyzing existing source code to document requirements, guide refactoring, and align implementation with business goals.

Core Features & Use Cases

  • Parse and normalize a target codebase to identify scope and language.
  • Discover and read source files to map structure, dependencies, and interfaces.
  • Analyze code to extract entry points, public interfaces, data models, APIs, and behaviors.
  • Generate a concise feature short name (2-4 words) that captures the primary function.
  • Create a feature spec by applying standard Spec Kit templates and store it under specs/ with a corresponding checklist.
  • Abstract implementation details to focus on what and why, not how.
  • Produce a completion report with branch/spec paths and discovered features.

Quick Start

Run the speckit-baseline skill on a codebase to generate a new feature specification.

Frequently Asked Questions about speckit-baseline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate feature specifications from existing source code?

Generate feature specifications by parsing a codebase to extract entry points, public interfaces, data models, and APIs, then translating them into a formal spec with user stories and acceptance criteria.

What is the best way to document requirements for refactoring an undocumented codebase?

Document refactoring requirements by analyzing existing source files to map structure and behaviors, abstracting implementation details to produce a feature specification focused on what the system does and why.

Can I use Spec Kit templates to create user stories and acceptance criteria for any programming language?

Spec Kit templates apply to existing codebases across multiple languages, parsing and normalizing the target code to generate user stories, acceptance criteria, data models, and implementation notes.

How does code analysis translate existing code constructs into a formal feature spec?

Code analysis identifies constructs like entry points and public interfaces, then maps dependencies and behaviors to generate a concise feature short name and a complete specification stored under the specs directory.

Does generating a feature specification require external dependencies or specific environment setup?

Generating a feature specification requires no external dependencies, allowing you to run the analysis directly on a target codebase to discover features and produce a completion report with branch and spec paths.

What limitations exist when abstracting implementation details into system requirements?

Abstracting implementation details focuses the specification on system requirements and business goals rather than how the code functions, ensuring the generated spec prioritizes what the feature does and why it exists.