trellis-update-spec

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

Updated May 2, 2026
One-click install
npx skills add https://github.com/lihaoze123/Inkline --skill trellis-update-spec-lihaoze123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/lihaoze123/Inkline/tree/main/.agents/skills/trellis-update-spec
Command: npx skills add https://github.com/lihaoze123/Inkline --skill trellis-update-spec-lihaoze123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers document and preserve executable contracts and coding conventions, ensuring clarity and consistency in codebase maintenance and future development.

Core Features & Use Cases

  • Capture Executable Contracts: Document code specifications for future reference.
  • Coding Conventions: Record coding standards and best practices.
  • Use Case: After implementing a new feature or fixing a bug, use this Skill to update the relevant code-spec documents, ensuring that knowledge is preserved for future sessions.

Quick Start

After completing a task, run the update-spec command to document the learned insights.

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 fixing a bug?

To document executable contracts and coding conventions after fixing a bug, run the update-spec command to classify learned insights into .trellis/spec/ documents, preserving knowledge for future sessions.

What is the best way to preserve debugging knowledge for future code maintenance?

The best way to preserve debugging knowledge is documenting executable contracts and coding conventions in .trellis/spec/ documents, requiring manual identification of learned insights to update relevant code-spec files.

How does updating code specification documents help with knowledge preservation?

Updating code specification documents helps knowledge preservation by capturing executable contracts and coding conventions, ensuring clarity and consistency in codebase maintenance and future development.

Do I need to manually classify insights when updating code specification documents?

Yes, you need to manually identify learned insights from debugging and implementation, then classify them into appropriate spec sections within .trellis/spec/ documents to ensure accurate contract documentation.

When should I use a tool to update code specification and contract documentation?

You should update code specification and contract documentation after implementing a new feature or fixing a bug, running the update-spec command to document the learned insights for future reference.