trellis-update-spec

Captures executable contracts and coding conventions into .trellis/spec/ documentation files.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-update-spec-hejiajiudeeyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-update-spec
Source: https://github.com/hejiajiudeeyu/delegated-execution-workspace/tree/main/.agents/skills/trellis-update-spec
Command: npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-update-spec-hejiajiudeeyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable lessons learned during debugging, feature implementation, and design discussions are often lost between sessions, forcing developers and AI agents to rediscover the same contracts, conventions, and pitfalls repeatedly. ## Core Features & Use Cases - Executable Contract Capture: Records concrete signatures, request/response fields, environment keys, and validation/error matrices rather than vague principles. - Structured Update Templates: Provides ready-made templates for design decisions, conventions, patterns, forbidden patterns, common mistakes, and gotchas. - Spec vs Guide Classification: Enforces a clear decision rule for placing content in layer-specific code-specs versus thinking checklists in guides/. - Use Case: After fixing a subtle cross-layer API bug, use this Skill to document the endpoint signature, error matrix, good/base/bad cases, and required tests in the relevant .trellis/spec/ file so future sessions implement it safely. ## Quick Start Update the backend code-spec with the error handling contract and validation rules we just discovered while fixing the API bug.

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 design decisions and coding conventions for a project?▼

Record each decision with its context, options considered, and rationale in a structured spec file, including concrete code examples. This Skill provides templates for design decisions, conventions, patterns, and common mistakes under .trellis/spec/.

When should I update a code-spec document after coding?▼

Update specs after implementing a feature, fixing a bug, making a design decision, discovering a pattern, or hitting a gotcha. Any change to command signatures, cross-layer contracts, database schemas, or infra integrations triggers a mandatory spec update.

What is the difference between a code-spec and a guide document?▼

Code-specs live in layer directories and describe how to implement safely with signatures, contracts, and test points. Guides live in guides/ and are short thinking checklists pointing to specs, covering what to consider before writing code.

What sections are required for infra or cross-layer contract changes?▼

Seven sections are mandatory: Scope/Trigger, Signatures, Contracts, Validation & Error Matrix, Good/Base/Bad Cases, Tests Required with assertion points, and at least one Wrong vs Correct pair.

When should I skip updating a spec document?▼

Skip updates for purely one-off implementation details that future developers would not need to understand, maintain, or extend the feature. If the knowledge prevents repeated mistakes or clarifies contracts, it belongs in the spec.