Agent skill · Documentation

aget-enhance-spec

Guide through the 7-phase specification enhancement lifecycle (Phases 0-6 from L622). Governs creating, updating, wiring, and validating AGET specifications.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill aget-enhance-spec-aget-framework-template-analyst-age --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 15 KB
Bundled scripts: none
Version: 1.1.0
Path: skills/agent/aget-enhance-spec-aget-framework-template-analyst-age/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /aget-enhance-spec Guide agents through the core specification enhancement lifecycle. Provides governed workflow for spec creation, updates, cross-reference wiring, and validation. ## Purpose Replace ad-hoc specification enhancement with a repeatable, governed 7-phase process derived from 5 independent plans across 3 agents (L622). This is the Generator layer (ADR-008 step 3), built on SOP_specification_enhancement.md (Advisory) and SKILL-041 spec (Strict). ## Input $ARGUMENTS - Enhancement category and optional spec path. Format: `<CATEGORY> [spec-path] [--version <target-version>]` Categories: NEW, UPDATE, ADD-REQ, WIRE, CONSOLIDATE, DEPRECATE Examples: - `/aget-enhance-spec NEW specs/AGET_FOO_SPEC.md` - `/aget-enhance-spec UPDATE aget/specs/AGET_SOP_SPEC.md --version 1.2.0` - `/aget-enhance-spec WIRE aget/specs/SKILL_NAMING_CONVENTION_SPEC.md` - `/aget-enhance-spec ADD-REQ aget/specs/AGET_SOP_SPEC.md` ## Phase Selection Not all categories require all phases. Use this table to determine which phases to execute: | Category | Required Phases | |----------|:---------------:| | NEW | 0, 1, 2, 3, 4, 5, 6 (all) | | UPDATE | 0, 1, 2, 3, 4, 5, 6 (all) | | ADD-REQ | 0, 1, 2, 3, 4, 5, 6

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Phase Selection
  4. Execution
  5. Step 1: Parse Input
  6. Step 2: Phase 0 — Trigger & Diagnosis
  7. Step 2.5: Phase 0.5 — Maturity Assessment (L682)
  8. Step 3: Phase 1 — Governing Spec Verification
  9. Step 4: Phase 2 — Census & Classification
  10. Step 5: Phase 3 — Draft/Update Spec
  11. Step 6: Phase 4 — Structural Validation
  12. Step 7: Phase 5 — Cross-Reference Wiring
  13. Step 8: Phase 6 — Self-Compliance Check
  14. Step 9: Produce Outputs
Ships with 1 file
  • metadata.json
Commands it runs
grep -l "<topic_keywords>" .aget/evolution/L*.md
ls specs/ aget/specs/ 2>/dev/null | grep -i "<topic>"
test -f "<referenced_path>" && echo "OK" || echo "STALE: <path>"
python3 .aget/patterns/sync/validate_spec_compliance.py <spec_path> 2>/dev/null
More from claude-skill-registry
All skills →
About this skill
What does the aget-enhance-spec skill do?

Guide through the 7-phase specification enhancement lifecycle (Phases 0-6 from L622). Governs creating, updating, wiring, and validating AGET specifications.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill aget-enhance-spec-aget-framework-template-analyst-age --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going