update-spec

Capture executable contracts and scope into code-spec documents after task completion.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MaShouo/CodexAuthExchange --skill update-spec-mashouo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/MaShouo/CodexAuthExchange/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/MaShouo/CodexAuthExchange --skill update-spec-mashouo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After debugging, implementing, or discussing, this skill helps you capture and formalize executable contracts into code-spec documents to preserve institutional memory and ensure accuracy.

Core Features & Use Cases

  • Create precise code-spec updates after feature work, bug fixes, or design decisions, including scope, signatures, contracts, validation, and tests.
  • Provide a structured process with templates and decision guidance to keep infra and cross-layer specs coherent.
  • Enable onboarding and audits by preserving decisions and contracts in a centralized, update-ready format.

Quick Start

Run this skill after finishing debugging or design review to update the relevant code-spec documents with executable contracts.

Frequently Asked Questions about update-spec

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

FAQPage Schema
How do I update code-specs after debugging or implementing a new feature?

Update code-specs by capturing and formalizing executable contracts, scope, and signatures from debugging or implementation sessions. This ensures your documentation accurately reflects current behavior, preserving institutional memory across infra and cross-layer boundaries.

What is the best way to document design decisions and executable contracts?

Document design decisions by applying a structured process with templates to capture scope, signatures, contracts, validation, error handling, and required tests. This formalizes decisions into a centralized, update-ready format for onboarding and audits.

When do I need to update code-spec documents in my software engineering workflow?

Update code-spec documents after completing feature work, bug fixes, or design discussions. Applying this process ensures your code-spec remains aligned with current behavior and satisfies requirements to document validation and error handling.

How to keep infra and cross-layer documentation coherent after code changes?

Keep infra documentation coherent by applying structured decision guidance and templates to update specs across cross-layer boundaries. This captures executable contracts and required tests to maintain alignment between implemented behavior and documented scope.

Does updating code-specs manually work for preserving institutional memory during audits?

Manually updating code-specs works for preserving institutional memory by capturing executable contracts, scope, and signatures into centralized files. This provides a structured, update-ready format that satisfies requirements for documenting validation and error handling.