speckit-baseline

Analyze source files to extract structure and behavior for spec generation.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-baseline-empoweredhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-baseline
Source: https://github.com/EmpoweredHouse/accrete/tree/main/skills/speckit-baseline
Command: npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-baseline-empoweredhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit Baseline helps teams generate clear, actionable feature specifications by analyzing existing source code, reducing ambiguity and onboarding time.

Core Features & Use Cases

  • Analyze codebases to identify entry points, interfaces, and dependencies.
  • Produce a structured spec template mapping code patterns to user stories, requirements, and entities.
  • Save specs into a standard template folder for version-controlled governance.

Quick Start

Provide the target codebase path to analyze and run the baseline spec generation workflow.

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 specs from existing source code?

Generate feature specs by analyzing your source files to extract structure and behavior. The tool maps code patterns to user stories, requirements, and entities, producing a structured spec template for your codebase.

Can I automatically create documentation for a legacy codebase with missing or outdated specs?

Yes, you can create documentation for legacy repositories by analyzing the codebase scope and source files. It identifies entry points, interfaces, and dependencies to produce structured feature specifications.

How do I map code patterns to user stories and requirements?

Map code patterns to user stories by analyzing source files to extract behavior and structure. The workflow maps these code patterns directly to user stories, requirements, and entities, saving them into a spec template.

Does this spec generation workflow work for code refactoring and new feature work?

Yes, spec generation works for code refactors and new feature work. It analyzes the target codebase path to identify scope and extracts structure and behavior to produce an updated feature spec template.

What is the best way to save generated feature specs for version-controlled governance?

Save generated feature specs for version-controlled governance by using standard spec templates. The workflow produces a structured spec template and saves it directly into a standard template folder within your repository.