update-spec

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

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/deepresearch --skill update-spec-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/MaplumeX/deepresearch/tree/main/.agents/skills/update-spec
Command: npx skills add https://github.com/MaplumeX/deepresearch --skill update-spec-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture precise, executable contracts and coding knowledge into code-spec documents after implementation, debugging, or design decisions, ensuring changes are codified and auditable.

Core Features & Use Cases

  • Enforces code-spec depth for infra and cross-layer changes by mandating sections for signatures, contracts, validation matrices, and test points.
  • Provides a structured process to document features, bug fixes, design decisions, and new patterns with clear templates.
  • Use case: after implementing a feature, update-spec ensures the resulting code changes are documented and auditable for future maintenance.

Quick Start

Follow the update-spec workflow after completing a task to generate the appropriate code-spec documentation.

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 coding knowledge after implementation?

You can document executable contracts and coding knowledge by capturing signatures, validation matrices, and test points into structured code-spec documents after implementation, debugging, or design decisions.

What is the best way to structure code-spec updates for infra and cross-layer changes?

The best way to structure code-spec updates for infra and cross-layer changes is to enforce documentation depth by mandating specific sections for signatures, contracts, validation matrices, and test points, ensuring changes are auditable.

When do I need to generate code-spec documentation for bug fixes and features?

You need to generate code-spec documentation for bug fixes and features immediately after completing a task. This ensures resulting code changes are documented and auditable for future maintenance and design decisions.

Does update-spec require any external dependencies or components to work?

No, update-spec does not require any external dependencies or components to function. It provides a structured workflow and templates natively to guide the documentation process from learning to final code-spec generation.

Can I use templates to document new patterns and design decisions in my code-spec?

Yes, you can use templates to document new patterns and design decisions. The process provides clear templates to structure features, bug fixes, and new patterns, ensuring precise and executable contracts are captured.

Why does my code-spec documentation lack depth for cross-layer changes?

Your code-spec documentation lacks depth for cross-layer changes if it omits mandated sections for signatures, contracts, validation matrices, and test points. Enforcing these specific sections ensures precise, executable contracts and proper auditability.