SpecKit Companion
A VS Code extension that implements the living spec closed-loop mechanism, automatically loading and folding back capability specifications before and after coding tasks according to YAML configuration.
Timeline (last 90 days)
SpecKit Companion is a VS Code extension whose author proposed the concept of living spec after writing 238 specifications.
SpecKit Companion's living specs feature is off by default and is only enabled once a living-specs.yml file appears in the project root directory.
In living-specs.yml, each capability specifies the matching file globs via the match field, determining which capability a change belongs to.
In living-specs.yml, the spec field determines where the specification file is stored: if omitted, it is stored centrally in the capabilities/ directory; if specified, it is placed in the folder of the code it describes.
SpecKit Companion provides a Living Specs sidebar view that displays all capabilities as a tree grouped by location, with specifications rendered as pages rather than raw markdown.
Write-back content is written into the feature specification and appears in the same PR diff as the code, so that changes to the living spec are actually reviewed.
If a run loads a living spec but writes nothing to it, at completion it is called out with a "nothing to write back" prompt, turning skipping the write-back into a visible event rather than a silent failure.
The author's first real case was a webview rendering change; the ticket did not mention HTML security, but the living spec for that area did, and this rule ultimately became a checkable acceptance item.
A markdown file sitting right next to the code it describes will be read regardless of whether a spec process is followed, regardless of which vendor's model is used, and regardless of the prompt.
All Facts (9)
A markdown file sitting right next to the code it describes will be read regardless of whether a spec process is followed, regardless of which vendor's model is used, and regardless of the prompt.
50%UnverifiedSpecKit Companion's living specs feature is off by default and is only enabled once a living-specs.yml file appears in the project root directory.
50%UnverifiedIn living-specs.yml, each capability specifies the matching file globs via the match field, determining which capability a change belongs to.
50%UnverifiedIn living-specs.yml, the spec field determines where the specification file is stored: if omitted, it is stored centrally in the capabilities/ directory; if specified, it is placed in the folder of the code it describes.
50%UnverifiedSpecKit Companion provides a Living Specs sidebar view that displays all capabilities as a tree grouped by location, with specifications rendered as pages rather than raw markdown.
50%UnverifiedWrite-back content is written into the feature specification and appears in the same PR diff as the code, so that changes to the living spec are actually reviewed.
50%UnverifiedIf a run loads a living spec but writes nothing to it, at completion it is called out with a "nothing to write back" prompt, turning skipping the write-back into a visible event rather than a silent failure.
50%UnverifiedSpecKit Companion is a VS Code extension whose author proposed the concept of living spec after writing 238 specifications.
50%UnverifiedThe author's first real case was a webview rendering change; the ticket did not mention HTML security, but the living spec for that area did, and this rule ultimately became a checkable acceptance item.
50%