trellis-update-spec

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

Updated Mar 24, 2026

Search Tags:#debugging #documentation #learning #contracts #ai-assisted #trellis #code-spec

Ready to run

npx skills add https://github.com/C-jcbest/agent --skill trellis-update-spec-c-jcbest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/C-jcbest/agent/tree/main/.agents/skills/trellis-update-spec
Command: npx skills add https://github.com/C-jcbest/agent --skill trellis-update-spec-c-jcbest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures executable contracts and coding conventions into .trellis/spec/ documents to preserve learning from debugging, implementation, or discussion for future sessions.

Core Features & Use Cases

Code-spec preservation: converts learnings into concrete, testable contracts including signatures, payload fields, env keys, and error behavior.
Rapid knowledge retention: creates standardized docs that guide future implementations and reviews.
Use Case: after debugging a tricky integration, update the code-spec to lock in decisions and test points.

Quick Start

Run the update flow to capture new executable contracts and design decisions into the .trellis/spec/ directory.

Frequently Asked Questions about trellis-update-spec

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

FAQPage Schema

How do I save executable contracts and coding conventions after debugging a tricky integration?▼

You can capture executable contracts and coding conventions into .trellis/spec documents to preserve debugging learnings for future sessions. This converts integration decisions into concrete, testable rules including signatures, payload fields, and error behavior.

What are executable contracts in code specifications and when do I need them?▼

Executable contracts are concrete, testable specifications that define function signatures, payload fields, validation rules, and error behavior. You need them during debugging, implementation, or discussions to lock in design decisions and guide future code reviews.

How to update code-spec documents to retain knowledge from implementation sessions?▼

Run the update flow to capture new executable contracts and design decisions into the .trellis/spec/ directory. This creates standardized docs that convert session learnings into testable contracts, ensuring future implementations follow validated rules.

Does capturing code-specs work without existing .trellis/spec directory structures?▼

The skill applies during debugging, implementation, or discussions to output code-spec sections within the .trellis/spec structure. It requires no external dependencies to generate documents containing signatures, contracts, validation rules, and test points.

What's the best way to preserve validation rules and test points for future AI-assisted coding sessions?▼

The best way is capturing executable contracts into .trellis/spec documents, which preserves validation rules and test points as standardized docs. This ensures future AI-assisted sessions reference concrete specifications rather than losing prior debugging context.

Why do my coding conventions get lost between debugging sessions and how can I prevent it?▼

Coding conventions get lost when session context expires without durable documentation. Prevent this by capturing executable contracts into .trellis/spec documents, which locks in decisions, signatures, and validation rules for rapid knowledge retention across sessions.