trellis-update-spec

Name: trellis-update-spec
Availability: InStock
Author: Reborn

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

52|7|Updated Apr 29, 2026

Search Tags:#documentation #engineering #contracts #design-decisions #trellis #code-spec

Ready to run

npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-update-spec-rebornq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/RebornQ/fl_api_hub/tree/main/.cursor/skills/trellis-update-spec
Command: npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-update-spec-rebornq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Creates structured code-specs with concrete signatures, payload fields, environment keys, and boundary behavior.
Documents design decisions, conventions, and patterns to guide future work and cross-team consistency.
Supports triggered updates after feature implementation, bug fixes, or architectural changes to ensure a reliable institutional memory.

Quick Start

Run the trellis update process after finishing a task to capture the latest code-spec.

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?▼

To document executable contracts, you update .trellis/spec/ documents with concrete signatures, payload fields, and validation rules. This preserves debugging insights and coding conventions for future sessions.

What is the best way to capture design decisions into a code-spec for future AI sessions?▼

Capturing design decisions into a code-spec involves formalizing boundary behaviors and test points into structured documents. This ensures AI and developers share a precise, testable specification.

When do I need to update specifications for cross-layer infrastructure changes?▼

You need to update specifications after feature implementations, bug fixes, or architectural changes. Triggering an update ensures reliable institutional memory across infrastructure and code.

Can I use a structured template to formalize code-specs and environment keys?▼

Yes, you can use a structured update template to formalize code-specs. The template guides you in defining environment keys, validation rules, and test points to ensure cross-team consistency.

Does generating code-specs require specific boundary behavior definitions for infrastructure?▼

Generating code-specs requires defining boundary behavior for infrastructure. The specification process captures payload fields and environment keys to create a precise, testable contract.