skills.rest
asengardeon
asengardeonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

baseline

Generates baseline documentation for undocumented legacy codebases via a codebase-archaeologist agent.

Updated Aug 25, 2026
Search Tags:#documentation#technical debt#codebase analysis#legacy code#baseline#spec-driven development
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill baseline-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: baseline
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/plugins/btt-sdd/skills/baseline
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill baseline-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When adopting a spec-driven development pipeline on an existing or legacy project, architects lack the grounding documentation needed to design a sound technical specification (TRD). This Skill fills that gap by producing a baseline document describing the existing system. ## Core Features & Use Cases - Conditional Pipeline Stage: Runs only when the repository lacks sufficient documentation about existing code, avoiding redundant work. - Codebase Archaeology: Invokes the codebase-archaeologist agent to analyze a repository or a specific area and produce docs/BASELINE.md covering system overview, conventions, and technical debt. - Scoped Analysis: Supports scoping to the whole repository or a specific area relevant to an in-progress spec. - Use Case: You adopted the SDD template on a legacy project and the architect flagged missing grounding for a TRD. Run this Skill to document the existing system before designing the new feature. ## Quick Start Ask the assistant to run the baseline step on this repository to generate docs/BASELINE.md describing the existing codebase.

Frequently Asked Questions about baseline

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

FAQPage Schema
How do I document a legacy codebase before writing a technical spec?▼

Run the baseline step, which invokes a codebase-archaeologist agent to analyze the repository and produce docs/BASELINE.md. The document covers the system overview, main conventions, and identified technical debt, giving the architect grounding for the TRD.

When should I run the baseline step in an SDD pipeline?▼

Run it only when the repository or the area relevant to a spec lacks sufficient documentation about existing code, such as when the template was adopted on a legacy project. It is a conditional stage, not a mandatory one.

Can I scope codebase documentation to a specific area instead of the whole repository?▼

Yes. You can pass a scope argument targeting a specific area relevant to an in-progress spec, or the Skill will ask you to clarify the scope if it is not clear.

What happens if the codebase already has enough documentation?▼

The codebase-archaeologist agent may conclude that documentation is already sufficient and create nothing. This is a valid, expected outcome, and the Skill reports it to the user normally.

Does the baseline step modify or refactor existing code?▼

No. The process only documents what it finds and never corrects or refactors the code, even when the agent tool is unavailable and the process is followed manually.

Related Skills

Explore More Software Engineering Skills→
elsa-workflowselsa-workflows
7.9k

speckit-clarify

Detects underspecified areas in feature specs and records targeted clarification answers.

Official
Advanced
phanijappsphanijapps

new-adr

Generate sequential Architecture Decision Records with standardized documentation templates.

Community
Intermediate
ananddtyagiananddtyagi
688

document-sync

Analyzes codebase and configuration to detect documentation drift and generate verified updates.

Community
Advanced
cosmicdreamscosmicdreams

interviews

Generate role-specific retro interview answers and write them to markdown files.

Community
Intermediate