skills.rest
LinnkidChen
LinnkidChenCOMMUNITY
Explore all skills by this author →
GitHub

update-spec

Capture executable contracts and coding knowledge into code-spec documents.

4|1|Updated Aug 9, 2025
Search Tags:#documentation#contracts#software-engineering#infra#cross-layer#code-spec
One-click install
npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill update-spec-linnkidchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/LinnkidChen/Stock-Tracker/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill update-spec-linnkidchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures executable contracts and coding knowledge into code-spec documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points.

Core Features & Use Cases

  • Centralizes executable contracts and design decisions into .trellis/spec/ to preserve institutional memory.
  • Ensures infra/cross-layer changes are documented with concrete signatures, payload definitions, and validation matrices.
  • Use after implementing a feature, fixing a bug, making a design decision, discovering a new pattern, or updating cross-layer contracts.

Quick Start

After completing a task, update the relevant code-spec documents to capture the signatures, contracts, validation matrices, and test points.

Frequently Asked Questions about update-spec

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

FAQPage Schema
How do I document executable contracts after implementing a feature?▼

To document executable contracts after feature implementation, you capture signatures, payload definitions, and validation matrices into code-spec documents within the .trellis/spec/ directory to preserve institutional memory.

What is the best way to document cross-layer infrastructure changes?▼

The best way to document cross-layer infrastructure changes is to enforce code-spec depth by recording concrete signatures, payload definitions, and validation matrices in centralized specification documents.

When do I need to update code-spec documents?▼

You need to update code-spec documents after implementing a feature, fixing a bug, making a design decision, discovering a new pattern, or updating cross-layer contracts to maintain accurate institutional memory.

Can I use code-spec documentation for bug fixes and design decisions?▼

Yes, code-spec documentation applies across software engineering workflows to capture knowledge after bug fixes and design decisions, ensuring concrete signatures and test points are recorded.

What mandatory sections are required for infra code-spec documents?▼

Mandatory sections for infra code-spec documents include signatures, contracts, validation matrices, and test points to ensure comprehensive documentation of executable contracts.

Does code-spec documentation work without external dependencies?▼

Yes, code-spec documentation operates without external dependencies, centralizing executable contracts and design decisions directly into the .trellis/spec/ directory structure.

Related Skills

Explore More Software Engineering Skills→
SilentFlowerSilentFlower

update-spec

Document executable contracts and design decisions into .trellis/spec files.

Community
Intermediate
MaplumeXMaplumeX

update-spec

Capture executable contracts and coding knowledge into code-spec documents.

Community
Advanced
C-jcbestC-jcbest

trellis-update-spec

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

Community
Advanced
TECNBTECNB
2

trellis-update-spec

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

Community
Intermediate