skills.rest
gmelli
gmelliCOMMUNITY
Explore all skills by this author →
Website𝕏@gmelliGitHub

aget-enhance-spec

Manage AGET specification lifecycle across seven governed phases.

1|Updated Oct 4, 2025
Search Tags:#specification#validation#compliance#governance#traceability#ears#project-plan
One-click install
npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-enhance-spec-gmelli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aget-enhance-spec
Source: https://github.com/gmelli/public-OpenAI-DeepResearch-aget/tree/main/.claude/skills/aget-enhance-spec
Command: npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-enhance-spec-gmelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill replaces ad-hoc specification updates with a repeatable, governed seven-phase lifecycle that ensures evidence-based changes, governance compliance, and traceable requirements for AGET specifications.

Core Features & Use Cases

  • Governance-first workflow: Enforces governing spec verification, project plan checks, and CAP requirement citations before edits.
  • End-to-end spec handling: Supports NEW, UPDATE, ADD-REQ, WIRE, CONSOLIDATE, and DEPRECATE flows across Phases 0–6 including drafting, structural validation, cross-reference wiring, and self-compliance.
  • Traceability and validation: Produces census tables, cross-reference reports, enhancement decision logs, and mandatory self-compliance checks to prevent bootstrapping paradoxes.

Quick Start

Invoke the skill with a 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
How do I enforce EARS-pattern requirements and traceability in specification updates?▼

A specification lifecycle workflow replaces ad-hoc edits with a repeatable seven-phase process, enforcing EARS-pattern requirements, semantic versioning, and mandatory self-compliance checks to ensure governance and traceability.

What is the best way to wire bidirectional cross-references between framework and agent specs?▼

The WIRE scenario within the seven-phase lifecycle handles bidirectional cross-references by validating semantic links and generating cross-reference reports to ensure structural consistency between framework and agent specifications.

How do I add new requirements to an existing specification without breaking compliance?▼

The ADD-REQ scenario verifies governing spec citations and project plan checks, applying semantic versioning and mandatory self-compliance validation to prevent bootstrapping paradoxes when adding new requirements.

When do I need to use the DEPRECATE scenario for specification lifecycle management?▼

Use the DEPRECATE scenario when retiring AGET specifications to maintain structural validation, traceability reporting, and semantic versioning compliance throughout the governed lifecycle.

Can I consolidate multiple framework specifications into a single governed spec?▼

The CONSOLIDATE scenario supports merging multiple framework specifications by enforcing governing spec verification, producing census tables, and validating structural compliance across the unified output.

Related Skills

Explore More Software Engineering Skills→
aget-frameworkaget-framework
1

aget-enhance-spec

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

Official
Advanced
maxenergymaxenergy

goal-pipeline

Generate REQUIREMENTS.md, DESIGN.md, and TASKS.md from a one-line idea.

Community
Intermediate
windyskywindysky

moai-workflow-spec

Orchestrate SPEC workflows with EARS format and Plan-Run-Sync lifecycle.

Community
Basic
geezerrrrgeezerrrr
117

mcporter

Manage MCP servers and tools via CLI with authentication and configuration.

Community
Intermediate