update-spec

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

3.9k|339|Updated Feb 3, 2026

Search Tags:#documentation #validation #contracts #signatures #infra #code-spec

Ready to run

npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill update-spec-zhukunpenglinyutong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/zhukunpenglinyutong/desktop-cc-gui/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill update-spec-zhukunpenglinyutong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. It 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.

Core Features & Use Cases

Code-spec as living contracts: captures signatures, contracts, and validation rules.
Traceable decisions: links changes to spec revisions and test points.
Use Case: After delivering a feature, update the relevant code-spec to ensure governance and reproducibility.

Quick Start

Trigger the update-spec workflow after completing a feature or bug fix to generate and append the relevant code-spec documents.

Frequently Asked Questions about update-spec

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

FAQPage Schema

How do I capture executable contracts and coding knowledge after implementation?▼

Capture executable contracts and coding knowledge by triggering a structured workflow that appends signatures, contracts, and validation matrices into .trellis/spec/ documents after completing a feature or bug fix.

What should be included in code-spec documentation for infra and cross-layer changes?▼

Code-spec documentation for infra and cross-layer changes must include mandatory sections for scope, signatures, contracts, validation matrices, test cases, and wrong-versus-correct examples to ensure governance and reproducibility.

When do I need to update code-spec documents for design decisions?▼

Update code-spec documents for design decisions when a feature is delivered, a bug is fixed, a new pattern is discovered, or cross-layer contracts change to maintain traceable links between revisions and test points.

How do I enforce a stepwise template for validation matrices and test points?▼

Enforce a stepwise template for validation matrices and test points by using a structured update workflow that requires mandatory sections for signatures, contracts, validation rules, and cases before finalizing the spec.

Does this code-spec workflow require any external dependencies or components?▼

This code-spec workflow operates without external dependencies or components, relying entirely on its internal structured template to capture signatures, contracts, and validation rules into .trellis/spec/ documents.

Why maintain living contracts and validation rules after debugging?▼

Maintain living contracts and validation rules after debugging to ensure that infra and cross-layer changes remain traceable to spec revisions and test points, preserving governance and reproducibility across the codebase.