update-spec
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
Best for code documentation during d…Works with GitHub
⌘source
- author
@mindfold-ai- language
- TypeScript
★6.7kstars
366forks
Apr 30, 2026
✦overview.md
Key Features
- ·Captures executable contracts after implementation
- ·Enforces mandatory sections for infra changes
- ·Includes signatures, contracts, validation matrices
- ·Timing-based triggers for spec updates
- ·Adds test points and assertion requirements
Use Cases
- →Update code-spec after implementing a new feature
- →Document bug fix with contracts and validation
- →Record design decisions with executable contracts
- →Capture new patterns discovered during development
- →Update cross-layer contracts when interfaces change
Best for
- ✓code documentation during development
- ✓cross-layer contract changes
Not ideal for
- !writing specs before implementation begins
FAQs
name
update-spec
description
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
Update Code-Spec - Capture Executable Contracts
When you learn something valuable (from debugging, implementing, or discussion), use this skill to update the relevant code-spec documents.
Timing: After completing a task, fixing a bug, or discovering a new pattern
Code-Spec First Rule (CRITICAL)
In this project, "spec" for implementation work means code-spec:
- Executable contracts (not principle-only text)
- Concrete signatures, payload fields, env keys, and boundary behavior
- Testable validation/error behavior
If the change touches infra or cross-layer contracts, code-spec depth is mandatory.
Required sections for infra/cross-layer specs:
- Scope / Trigger
- Signatures (command/API/DB)
- Contracts (request/response/env)
- Validation & Error Matrix
- Good/Base/Bad Cases
- Tests Required (with assertion points)
- Wrong vs Correct (at least one pair)
When to Update Code-Specs
| Trigger | Example | Target Spec |
|---|---|---|
| Implemented a feature | Added template download with giget | Relevant backend/ or frontend/ file |
$install
1-click copynpx skills add mindfold-ai/Trellis --skill update-specSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
2/ 5
fairThe main idea is there, but the wording is messy and easy to misinterpret.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.