skills.rest
sperictao
sperictaoCOMMUNITY
Explore all skills by this author →
GitHub

trellis-update-spec

Capture debugging and implementation learnings into structured .trellis/spec/ documents.

1|Updated Jan 11, 2026
Search Tags:#templates#debugging#documentation#learning#contracts#tests#code-spec
One-click install
npx skills add https://github.com/sperictao/one-publish --skill trellis-update-spec-sperictao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/sperictao/one-publish/tree/main/.cursor/skills/trellis-update-spec
Command: npx skills add https://github.com/sperictao/one-publish --skill trellis-update-spec-sperictao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Automatically converts learning moments into structured code-spec updates (Scope/Trigger, Signatures, Contracts, Validation & Error Matrix, Good/Base/Bad, Tests Required, Wrong vs Correct).
  • Guides teams when design decisions affect contracts across layers, enabling consistent documentation and future reproducibility.
  • Supports end-to-end updates that reference the seven required sections to ensure testable and auditable specs.

Quick Start

Run a learning moment through the update workflow to generate a complete code-spec entry for the next project session.

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 code conventions and executable contracts after a debugging session?▼

To capture code conventions after debugging, run a learning moment through an update workflow that generates structured code-spec documents in .trellis/spec/ directories for future reference.

What is a code-spec and what sections should it contain?▼

A code-spec is a structured document preserving executable contracts. It must contain seven sections: Scope/Trigger, Signatures, Contracts, Validation & Error Matrix, Good/Base/Bad, Tests Required, and Wrong vs Correct.

How do I document design decisions that affect contracts across multiple layers?▼

Documenting cross-layer design decisions involves generating structured code-spec updates referencing the required seven sections, ensuring consistent documentation and future reproducibility for your team.

Can I generate testable and auditable specs from implementation discussions?▼

Yes, you can generate testable specs from implementation discussions by capturing the learning moment and producing end-to-end code-spec updates that link validation rules and tests to relevant context.

Do I need any specific testing frameworks to write code-specs?▼

No specific testing frameworks are required. The code-spec generation process targets learning moments to define the Tests Required section without mandating a particular testing library.

Related Skills

Explore More Software Engineering Skills→
PorkbuttsPorkbutts
1

reflect

Extract actionable lessons from conversations and persist them to ~/.claude/lessons/.

Community
Basic
LinXueyuanStdioLinXueyuanStdio
2

Update Code-Spec - Capture Executable Contracts

Captures post-task learnings into executable code-spec documents with verifiable contracts.

Community
Advanced
BaSui01BaSui01
3

update-spec

Capture implementation decisions into structured code-spec documents under .trellis/spec/.

Community
Intermediate
answerend42answerend42

trellis-update-spec

Capture technical knowledge and design decisions into structured code-spec documents.

Community
Intermediate