trellis-update-spec

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

8|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/yuanjing-hash/OhMyCine --skill trellis-update-spec-yuanjing-hash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/yuanjing-hash/OhMyCine/tree/main/.agents/skills/trellis-update-spec
Command: npx skills add https://github.com/yuanjing-hash/OhMyCine --skill trellis-update-spec-yuanjing-hash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps software engineers capture and document code contracts, improving development consistency and enabling future developers and AI systems to implement code safely and reliably.

Core Features & Use Cases

  • Contract Documentation: Stores executable contracts in .trellis/spec/ documents.
  • Feature Implementation Updates: Documents new features after development.
  • Bug Fixes and Code Patterns: Records learnings from debugging sessions.
  • Use Case: After fixing a bug, document the issue and its fix to avoid similar issues in the future.

Quick Start

Use the trellis:update-spec command to record the code changes made in fixing the bug 'ID-1234'.

Frequently Asked Questions about trellis-update-spec

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

FAQPage Schema
What is the best way to document code contracts and debugging learnings after fixing a bug?

Documenting code contracts and debugging learnings is best achieved by capturing executable contracts, coding conventions, and design decisions into code-spec documents for future reference and maintainability.

How do I record code changes and design decisions for future reference?

You record code changes and design decisions by using the trellis:update-spec command to store new features, bug fixes, and project conventions as structured documentation within the .trellis/spec/ directory.

How does capturing executable contracts improve developer efficiency?

Capturing executable contracts improves developer efficiency by providing clear documentation of project conventions and code patterns, enabling future developers and AI systems to implement code safely and reliably.

Can I use this approach to document coding conventions for AI systems to implement code reliably?

Yes, you can use this approach to document coding conventions. It stores executable contracts and design decisions in code-spec documents, which directly supports AI systems and future developers in implementing code reliably.

When do I need to update code-spec documents during software development?

You need to update code-spec documents after completing feature implementations or fixing bugs to record the specific issue and its resolution, preventing similar issues from occurring in the future.

Are there limitations to maintaining project conventions through code-spec documents?

Maintaining project conventions through code-spec documents requires consistent updates after bug fixes and feature development; failing to document changes continuously will reduce the clarity and maintainability of the executable contracts.