skills.rest
XiaSanw
XiaSanwCOMMUNITY
Explore all skills by this author →
GitHub

trellis-update-spec

Record executable contracts and coding conventions into .trellis/spec documentation.

2|Updated May 25, 2026
Search Tags:#documentation#engineering#contracts#coding-conventions#knowledge-retention#trellis#codespec
One-click install
npx skills add https://github.com/XiaSanw/LLM-WIKI-Xiasanw --skill trellis-update-spec-xiasanw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/XiaSanw/LLM-WIKI-Xiasanw/tree/main/.claude/skills/trellis-update-spec
Command: npx skills add https://github.com/XiaSanw/LLM-WIKI-Xiasanw --skill trellis-update-spec-xiasanw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

To prevent knowledge loss, this skill captures executable contracts and coding conventions into centralized .trellis/spec documents during debugging, implementation, or discussion.

Core Features & Use Cases

  • Records concrete signatures, payload fields, env keys, and boundary behavior as code-spec artifacts.
  • Guides teams to preserve decisions, patterns, and validation rules for future sessions and cross-team collaboration.
  • Use case: after debugging a tricky integration, update the code-spec so future engineers can reproduce and verify behavior.

Quick Start

After finishing a debugging session, run the trellis update-spec flow to record executable contracts into the .trellis/spec documentation.

Frequently Asked Questions about trellis-update-spec

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

FAQPage Schema
How do I document executable contracts and coding conventions after a debugging session?▼

Yes, you can capture environment keys and payload fields as code-spec artifacts during discussions. The skill records decisions and validation rules into .trellis/spec documents, preserving concrete signatures for cross-team collaboration and future reference.

What is the best way to retain knowledge of API signatures and boundary behavior across modules?▼

You should update the code-spec documentation whenever a task is completed or a design decision is finalized. Fitting this flow after implementation ensures env keys and boundary behavior are recorded before context is lost.

Does this code-spec documentation tool require any specific dependencies to run?▼

No specific dependencies are required to run this code-spec documentation tool. It operates independently to update .trellis/spec documents, allowing teams to preserve executable contracts without external component installations.

When should I update trellis spec documentation for coding conventions?▼

You should update trellis spec documentation immediately after finishing a debugging session or implementation task. Recording executable contracts at these points ensures future engineers can reproduce and verify the exact boundary behavior and validation rules.

Related Skills

Explore More Software Engineering Skills→
Jerry-Z07Jerry-Z07
21

update-spec

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

Community
Intermediate
Tendo33Tendo33
45

trellis-update-spec

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

Community
Advanced
ianyimiianyimi
1

Global Tech Stack

Enforce coding standards for the global tech stack in Claude Code.

Community
Basic
Brite-NitesBrite-Nites

compound-learnings

Record decisions, gotchas, and conventions to CLAUDE.md and auto-memory.

Official
Advanced