skills.rest
Ziphyrien
ZiphyrienCOMMUNITY
Explore all skills by this author →
GitHub

trellis-update-spec

Automates capture of executable contracts and coding conventions into .trellis/spec documents.

60|7|Updated Feb 25, 2026
Search Tags:#debugging#documentation#spec-management#trellis#code-spec#executable-contracts
One-click install
npx skills add https://github.com/Ziphyrien/Pi-Telegram --skill trellis-update-spec-ziphyrien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/Ziphyrien/Pi-Telegram/tree/main/.pi/skills/trellis-update-spec
Command: npx skills add https://github.com/Ziphyrien/Pi-Telegram --skill trellis-update-spec-ziphyrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineering teams preserve executable contracts and coding conventions discovered during debugging, implementation, or discussion by converting them into centralized .trellis/spec documents.

Core Features & Use Cases

  • Capture executable contracts including signatures, payload fields, and environment keys.
  • Document design decisions and coding conventions for cross-session reuse.
  • Update target spec files to reflect changes from debugging or implementation tasks, preserving institutional memory.

Quick Start

Run the trellis update-spec workflow after finishing a debugging or implementation task to capture learnings as codified code-spec entries.

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 discovered during debugging?▼

You can document executable contracts by capturing signatures, payload fields, and environment keys into structured .trellis/spec files. This preserves design decisions and validations for cross-session reuse across debugging, implementation, and code review contexts.

What is the best way to preserve institutional memory for API contracts and validations after a bug fix?▼

Preserve institutional memory by applying a step-by-step template that records API signatures, payload fields, error behavior, and test points into centralized spec documents. This ensures coding conventions and design decisions are maintained for future reference.

How do I update spec files to reflect changes made during implementation tasks?▼

Update spec files by running a structured workflow that applies a template to record environment keys, error behavior, and test points. This modifies the target spec documents to accurately reflect the coding changes and contract validations from your implementation work.

Can I capture design decisions and environment keys for cross-session reuse without losing context?▼

Yes, you can capture design decisions and environment keys by converting them into centralized .trellis/spec documents. This approach ensures that executable contracts and coding conventions are structured and preserved for cross-session reuse.

Does this spec management approach work for documenting error behavior and test points from code reviews?▼

Yes, spec management works for code reviews by enforcing a template that records error behavior and test points alongside payload fields and signatures. This captures executable contracts directly into target spec files for future debugging and discussion contexts.

Related Skills

Explore More Software Engineering Skills→
gdm257gdm257
2

trellis-update-spec

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

Community
Advanced
C-jcbestC-jcbest

trellis-update-spec

Capture 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
WASIDJWASIDJ

trellis-update-spec

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

Community
Advanced