trellis-update-spec

Capture executable contracts and coding conventions as code-spec documents.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/MrHan-Yd/DdShell --skill trellis-update-spec-mrhan-yd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/MrHan-Yd/DdShell/tree/main/.opencode/skills/trellis-update-spec
Command: npx skills add https://github.com/MrHan-Yd/DdShell --skill trellis-update-spec-mrhan-yd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert debugging or learning moments into concrete, executable code-spec documents that preserve contracts and conventions for future work.

Core Features & Use Cases

  • Structured code-spec updates: captures signatures, payloads, env keys, and error behavior.
  • Cross-layer consistency: ensures contracts stay aligned during refactors or infra changes.
  • Learning preservation: records decisions from debugging or design for reuse in future sessions.

Quick Start

Capture your learning by creating or updating the corresponding .trellis/spec entry for the task you just completed.

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

To document code conventions and executable contracts after debugging, you capture them as structured code-spec documents. This preserves engineering decisions, signatures, and error behaviors for future sessions and code reviews.

What sections should be included in a code-spec document for engineering guidelines?

A code-spec document for engineering guidelines requires sections for scope, signatures, contracts, validation, error handling, test requirements, and wrong versus correct examples to ensure comprehensive coverage.

How do I preserve learning moments from debugging for future development sessions?

You preserve learning moments by converting debugging outcomes into durable .trellis/spec entries. This records design decisions and coding conventions to guide future development sessions across projects.

How do I maintain cross-layer consistency during code refactors?

To maintain cross-layer consistency during refactors, capture executable contracts in code-specs. This ensures aligned signatures, payloads, and error behaviors are preserved and referenced throughout infrastructure changes.

When do I need to create a code-spec document?

You need to create a code-spec document during learning moments from debugging, implementing, or discussing across projects. It captures executable contracts to preserve engineering decisions for future code reviews.