skills.rest
jlifeng
jlifengCOMMUNITY
Explore all skills by this author →
𝕏@leyfung_GitHub

update-spec

Generate structured code-spec updates with signatures, contracts, and validation matrices.

114|18|Updated May 15, 2026
Search Tags:#validation#contracts#signatures#tests#design-decisions#code-spec#update-spec
One-click install
npx skills add https://github.com/jlifeng/JobPilot --skill update-spec-jlifeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/jlifeng/JobPilot/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/jlifeng/JobPilot --skill update-spec-jlifeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update Code-Spec documentation to reflect new executable contracts, signatures, and validation rules discovered during debugging or design discussions.

Core Features & Use Cases

  • Automatically generate and structure code-spec content for infra/cross-layer changes, including Scope, Signatures, Contracts, Validation & Error Matrix, and Test Points.
  • Provide clear design decisions and conventions to guide future implementations.
  • Ensure consistency across code-specs when updating or adding new contracts.

Quick Start

Run the update-spec process after concluding a feature, bug fix, or design decision to create the corresponding code-spec update.

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 and validation rules for a new feature?▼

Update code-spec documentation to capture executable contracts by structuring sections for Scope, Signatures, Contracts, and Validation. This formalizes design decisions and expected behavior discovered during feature implementation or debugging.

What is the best way to structure code-specs for cross-layer infrastructure changes?▼

Structure infra code-specs by defining Scope, Signatures, Contracts, and a Validation & Error Matrix. Include Good/Base/Bad cases and Wrong vs Correct examples to ensure consistency across cross-layer infrastructure updates.

When do I need to create an executable contract code-spec update?▼

Create an executable contract code-spec update after concluding a feature, bug fix, or design decision. It captures newly discovered signatures and validation rules for infra/cross-layer changes requiring formalized contracts.

Does the code-spec update process include required test points?▼

Yes, the code-spec update process includes a Tests Required section. This ensures executable contracts and validation rules are accompanied by specific test points covering Good/Base/Bad cases to verify expected behavior.

How do I document wrong versus correct implementation examples in a code-spec?▼

Document wrong versus correct examples by using the dedicated Wrong vs Correct section in the code-spec. This clearly contrasts bad implementations against the expected executable contracts and signatures, guiding future development conventions.

Related Skills

Explore More Software Engineering Skills→
OriginHubAIOriginHubAI
1

update-spec

Update code-spec documents with executable contracts after debugging or design decisions.

Official
Advanced
LinXueyuanStdioLinXueyuanStdio
2

Update Code-Spec - Capture Executable Contracts

Captures post-task learnings into executable code-spec documents with verifiable contracts.

Community
Advanced
zineyuzineyu

trellis-update-spec

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

Community
Advanced
johnlindquistjohnlindquist
24

lessons

Capture and organize coding lessons from sessions and reviews into reusable patterns.

Community
Basic