skills.rest
Jerry-Z07
Jerry-Z07COMMUNITY
Explore all skills by this author →
GitHub

update-spec

Capture implementation and design decisions into executable code-spec documents.

21|4|Updated Dec 24, 2025
Search Tags:#testing#documentation#contracts#signatures#infra#cross-layer#code-spec
One-click install
npx skills add https://github.com/Jerry-Z07/WindBoard --skill update-spec-jerry-z07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/Jerry-Z07/WindBoard/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/Jerry-Z07/WindBoard --skill update-spec-jerry-z07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Creates and maintains executable code-spec documents that capture concrete signatures, payload structures, env keys, and boundary behavior.
  • Enforces depth for infra/cross-layer changes, ensuring signatures, contracts, validation matrices, and test points are present.
  • Useful after implementing a feature, fixing a bug, making a design decision, discovering a pattern, or updating cross-layer contracts.

Quick Start

Update the relevant code-spec documentation immediately after completing a task.

Frequently Asked Questions about update-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are executable code-spec documents and when do I need them?▼

Code-spec documents capture actionable insights from implementation and debugging into .trellis/spec/ files, enforcing depth for infra and cross-layer changes. They mandate sections for signatures, contracts, validation matrices, and tests to satisfy requirements with concrete payload fields, env keys, and boundary behavior.

Does code-spec validation work with boundary behavior and env keys for infra updates?▼

Yes, code-spec enforcement specifically applies to infra and cross-layer changes, ensuring mandatory sections like API signatures, contracts, and validation matrices are present. It captures concrete payload structures, env keys, and boundary behavior to satisfy requirements for infrastructure modifications.

How to generate code-spec documents with payload fields and validation matrices after a design decision?▼

The best way to document validation matrices and test points after a bug fix is updating code-spec documentation immediately after completing the task. This captures the debugging insights as executable contracts with concrete signatures, payload fields, and boundary behavior in .trellis/spec/ documents.

When should I not use code-spec enforcement for documenting implementation changes?▼

Code-spec documentation lacks mandatory sections when actionable insights from implementation or design decisions are not captured properly. Enforce depth for infra and cross-layer changes by ensuring signatures, contracts, validation matrices, and test points are present with concrete env keys and boundary behavior.

Related Skills

Explore More Software Engineering Skills→
gdm257gdm257
2

trellis-update-spec

Capture executable contracts and coding conventions into .trellis/spec/ documents.

Community
Advanced
LinnkidChenLinnkidChen
4

update-spec

Capture executable contracts and coding knowledge into code-spec documents.

Community
Advanced
Tendo33Tendo33
45

trellis-update-spec

Records executable contracts and coding conventions into .trellis/spec/ documents.

Community
Advanced
OriginHubAIOriginHubAI
1

update-spec

Update code-spec documents with executable contracts after debugging or design decisions.

Official
Advanced