skills.rest
gongzeq
gongzeqCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

trellis-update-spec

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

Updated May 7, 2026
Search Tags:#documentation#engineering-process#trellis#code-spec#update-spec#spec-contracts
One-click install
npx skills add https://github.com/gongzeq/VAPT3 --skill trellis-update-spec-gongzeq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/gongzeq/VAPT3/tree/main/.agents/skills/trellis-update-spec
Command: npx skills add https://github.com/gongzeq/VAPT3 --skill trellis-update-spec-gongzeq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures executable contracts and coding conventions into .trellis/spec/ documents after debugging, implementing, or discussion, preserving institutional memory for future sessions.

Core Features & Use Cases

  • Turn learnings into concrete, testable code-specs (signatures, payload fields, env keys, and expected behavior).
  • Centralize contracts and conventions to guide future changes and audits across teams.
  • Use Case: After a debugging session, generate an updated code-spec to align team expectations and prevent regressions.

Quick Start

Run the update-spec command after completing a feature or debugging session to record the code-spec changes.

Frequently Asked Questions about trellis-update-spec

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

FAQPage Schema
How do I capture executable contracts into spec documents after a debugging session?▼

You can use this Skill to automate capturing executable contracts and coding conventions into .trellis/spec documents, preserving decisions as structured, testable code-specs after debugging or implementation sessions.

What is an executable code-spec and when do I need to create one?▼

An executable code-spec defines signatures, payload fields, environment keys, and expected behavior. You need to create one after debugging or design discussions to preserve institutional memory and prevent future regressions.

How do I document coding conventions so they can be validated and audited across teams?▼

This Skill centralizes coding conventions and contracts into structured .trellis/spec files that can be validated, versioned, and audited, aligning team expectations and guiding future code changes.

Do I need clearly defined function signatures to generate a trellis spec document?▼

Yes, generating a trellis spec document requires clearly defined signatures, contracts, and environment details as input to produce a structured spec file that accurately captures the expected behavior.

What's the best way to turn design discussion decisions into testable code-specs?▼

The best way is to run the update-spec command after your design discussion to automatically transform decisions into concrete, testable code-specs containing signatures, payload fields, and environment keys.

Related Skills

Explore More Software Engineering Skills→
gdm257gdm257
2

trellis-update-spec

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

Community
Advanced
21ess21ess

trellis-meta

Guide customization of local .trellis architecture and platform directories.

Community
Intermediate
yuanjing-hashyuanjing-hash
8

trellis-update-spec

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

Community
Advanced
TECNBTECNB
2

trellis-update-spec

Document executable contracts and coding conventions into .trellis/spec/ files.

Community
Intermediate