Spec update
Make a minimal evidence-backed update to a non-plan product, architecture, API, schema, or behavior contract. Use when implementation or validation cannot determine correctness from the current authoritative contract.From its SKILL.md
npx -y skills add yarlson/yarstack --skill spec-updateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 201 tokens by cl100k_base, as published. Nobody here has run it
Specification Update
Correct an authoritative semantic contract only when current work depends on it.
Workflow
- Identify the missing or incorrect contract, its canonical document and owner, and the current task it blocks.
- Use
plan-updatefor implementation-plan mechanics anddocs-drift-reviewfor ordinary prose drift. - Distinguish an evidence-backed clarification from a new product or architecture decision.
- Use
architecture-refinefor an unresolved architecture decision. Stop for the user or named owner when available evidence cannot determine intended behavior. - Confirm authority before editing linked documents outside the repository or requested scope.
- Apply only the minimum supported correction in the document's existing structure and style.
- State the downstream acceptance or validation effect, then return to the invoking task.
Do not create speculative features, use specifications as implementation logs, rewrite unrelated sections, or silently invent behavior.
Finish with the changed contract, supporting evidence, concrete decision, downstream impact, and any remaining blocker.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.