update-specification

Update solution specification files into structured Markdown under /spec.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill update-specification-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-specification
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/update-specification
Command: npx skills add https://github.com/selfagency/agentsy --skill update-specification-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you update an existing requirements/specification document so it remains clear, unambiguous, and machine-readable for Generative AI consumption.

Core Features & Use Cases

  • AI-Ready Specification Updates: Converts new or changed requirements into a structured document with requirements, constraints, interfaces, and acceptance criteria.
  • Template-Following, Structured Output: Enforces consistent sections and conventions so the spec can be reliably parsed and reused.
  • Edge-Case and Validation Coverage: Prompts inclusion of examples, edge cases, dependencies, and explicit validation criteria.

Quick Start

Ask the AI to update the file ${file} to reflect the latest requirements and changes found in the relevant codebase, and save the updated specification to the /spec directory using the [a-z0-9-]+.md naming convention.

Frequently Asked Questions about update-specification

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

FAQPage Schema
How do I update an existing specification document for AI consumption?

To update a specification for AI consumption, apply new code requirements to an existing spec file, enforcing structured Markdown sections like constraints, interfaces, and acceptance criteria for machine readability.

What is an AI-ready specification and how does it work?

An AI-ready specification is a structured Markdown document using machine-readable sections for requirements and validation. It works by translating code changes into unambiguous constraints and acceptance criteria for Generative AI parsing.

How do I translate new code requirements into acceptance criteria and interface contracts?

Translate new code requirements into acceptance criteria by updating the specification file, applying the changes to interface contracts and validation rules, then saving the output using a prescribed Markdown naming convention.

Can I use a structured Markdown template for generating requirements documents?

Yes, you can generate requirements documents using a structured Markdown template. The process enforces consistent sections and conventions so the specification can be reliably parsed and reused by AI.

What's the best way to maintain validation criteria and edge cases in a specification?

The best way to maintain validation criteria and edge cases in a specification is to update the document regularly with new requirements, prompting explicit inclusion of examples and dependencies within structured sections.

Does updating requirements specifications work without external dependencies?

Yes, updating requirements specifications works without external dependencies. The process directly modifies an existing Markdown file, applying structured templates and saving the result to a designated directory using a specific filename pattern.