skills.rest
SilentFlower
SilentFlowerCOMMUNITY
Explore all skills by this author →
GitHub

update-spec

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

Updated Apr 15, 2026
Search Tags:#template#devops#documentation#specification#contracts#code-spec
One-click install
npx skills add https://github.com/SilentFlower/flower-cli --skill update-spec-silentflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/SilentFlower/flower-cli/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/SilentFlower/flower-cli --skill update-spec-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often forget to capture executable contracts, design decisions, and validation details after implementing features or fixing bugs, leading to missing documentation and inconsistent specifications.

Core Features & Use Cases

  • Guided Process: Step‑by‑step prompts to identify what was learned and where it belongs in the .trellis/spec hierarchy.
  • Standard Templates: Predefined markdown sections for infra, cross‑layer contracts, design decisions, conventions, patterns, and gotchas.
  • Quality Checklist: Ensures updates include signatures, contracts, validation matrices, test points, and proper indexing.
  • Use Cases: Run after feature implementation, bug resolution, design discussions, or when discovering new patterns to keep code‑specs current and reliable.

Quick Start

Run the update-spec skill immediately after completing a task to document the new contracts and decisions.

Frequently Asked Questions about update-spec

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

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

To document design decisions after implementation, you capture executable contracts and validation details into .trellis/spec markdown files using guided prompts and predefined templates for signatures and test points.

What is the best way to keep code specifications current after bug fixes and cross-layer changes?▼

Keeping code specifications current after bug fixes requires updating markdown spec sections with signatures, validation matrices, and guidelines immediately after resolving the bug to ensure consistent documentation.

When should I update .trellis spec files for infra changes and pattern discoveries?▼

You should update .trellis spec files for infra changes and pattern discoveries immediately after completing the task, using a quality checklist to ensure updates include contracts, test points, and proper indexing.

Does this code-spec documentation process work without external dependencies?▼

Yes, this code-spec documentation process works without external dependencies, applying standard markdown templates directly within your project repository to capture infra and cross-layer contracts.

How do I structure validation matrices and test points in specification markdown?▼

To structure validation matrices and test points in specification markdown, apply predefined template sections for design decisions and conventions, ensuring all updates pass a quality checklist for proper indexing.

Why does missing documentation occur after feature implementation and how do I prevent it?▼

Missing documentation occurs after feature implementation because developers forget to capture executable contracts, which you prevent by running a guided step-by-step process to document decisions into .trellis/spec files.

Related Skills

Explore More Software Engineering Skills→
tduck1equacktduck1equack

update-spec

Update code specifications to reflect feature implementations and bug fixes.

Community
Advanced
Jerry-Z07Jerry-Z07
21

update-spec

Capture implementation and design decisions into executable code-spec documents.

Community
Intermediate
LinnkidChenLinnkidChen
4

update-spec

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

Community
Advanced
huangjunsen0406huangjunsen0406
77

trellis-update-spec

Capture technical knowledge and design decisions into structured code-spec markdown documentation.

Community
Intermediate