What problem does it solve? When a spec-driven development pipeline is adopted on top of an existing project, architects lack the grounding needed to write a Technical Requirements Document. This Skill fills that gap by producing a baseline document describing the existing system before any new feature work begins. ## Core Features & Use Cases - Conditional pipeline stage: Runs only when the repository (or a spec-relevant area) lacks sufficient documentation of existing code. - Scoped analysis: Targets either the entire repository or a specific area relevant to an in-progress spec, based on user input. - Agent delegation: Invokes the codebase-archaeologist agent to create or update docs/BASELINE.md, and treats "documentation already sufficient" as a valid outcome. - Use Case: You adopted the SDD template on a legacy project and need the architect to design a TRD. Run this Skill first so the architect has documented system conventions, architecture, and technical debt to build on. ## Quick Start Run /sdd-baseline and specify the repository or spec area to document so the codebase-archaeologist agent produces docs/BASELINE.md.
