speckit-baseline — Claude Code skill: specs from existing code

What speckit-baseline 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.