aget-enhance-spec

Guide AGET specification enhancements through a governed lifecycle with validation and reports.

1|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/aget-framework/template-worker-aget --skill aget-enhance-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aget-enhance-spec
Source: https://github.com/aget-framework/template-worker-aget/tree/main/.claude/skills/aget-enhance-spec
Command: npx skills add https://github.com/aget-framework/template-worker-aget --skill aget-enhance-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replace ad-hoc and inconsistent specification edits with a repeatable, governed lifecycle that ensures evidence-driven changes, traceability, and mandatory self-compliance for AGET specifications.

Core Features & Use Cases

  • Phased Governance: Walks enhancements through Phases 0–6 including diagnosis, governing-spec verification, census, drafting, structural validation, cross-reference wiring, and self-compliance.
  • Traceability & Reports: Produces cross-reference reports, enhancement decision logs, and stale-artifact remediation plans to maintain bidirectional traceability.
  • Constraint Enforcement: Enforces inviolable constraints (e.g., never skipping governing spec verification or self-compliance checks) and uses EARS patterns and unique requirement IDs.
  • Use Case: Use when creating a new public spec, updating a framework spec, wiring requirements across specs, or consolidating and deprecating artifacts while preserving governance evidence.

Quick Start

Run an aget-enhance-spec enhancement by specifying the category and optional spec path, for example: /aget-enhance-spec NEW specs/AGET_FOO_SPEC.md

Frequently Asked Questions about aget-enhance-spec

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

FAQPage Schema
Specification enhancement solves traceability by guiding changes through a 7-phase governance lifecycle, producing cross-reference reports and decision logs to maintain bidirectional links across files.▼

Specification enhancement solves traceability by guiding changes through a 7-phase governance lifecycle, producing cross-reference reports and decision logs to maintain bidirectional links across files.

What is the EARS pattern for writing software requirements?▼

The EARS pattern is an enforced constraint within the specification enhancement lifecycle, used to structure requirement statements with unique requirement IDs for consistent, unambiguous specification drafting.

How to create a new governed specification from an existing repository?▼

Initiate a NEW enhancement by specifying the category and spec path, which triggers phases from evidence collection and governing spec verification to drafting, structural validation, and mandatory self-compliance checks.

Can I consolidate and deprecate old specifications while preserving governance evidence?▼

Yes, the lifecycle supports CONSOLIDATE and DEPRECATE enhancements, generating stale-artifact remediation plans and decision logs to ensure deprecated artifacts retain their governance evidence and traceability.

How do you wire cross-references between public and private specifications?▼

Cross-reference wiring is performed in a dedicated phase of the enhancement lifecycle, validating structural links between public and private specs and producing a cross-reference report to ensure bidirectional traceability.

What happens if I skip the governing spec verification during a specification update?▼

Skipping governing spec verification violates an inviolable constraint of the lifecycle; the process enforces mandatory self-compliance checks and evidence collection to prevent unverified specification updates.