agent-evolution

Analyze completed GUTTERS work to decide when to create skills or update AGENTS.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/drhayf/GUTTERS --skill agent-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-evolution
Source: https://github.com/drhayf/GUTTERS/tree/main/.agent/skills/agent-evolution
Command: npx skills add https://github.com/drhayf/GUTTERS --skill agent-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This meta-skill helps teams convert recurring insights from completed GUTTERS work into reusable SKILL definitions and governance updates, ensuring consistent process improvement across projects.

Core Features & Use Cases

  • Guides when to create new skills or update AGENTS.md after complex tasks or pattern emergence.
  • Provides a structured Draft Skill template to accelerate future module development and documentation.
  • Aligns team practices with GUTTERS no-mocks, production-ready philosophy to improve velocity.

Quick Start

Review a completed project, extract reusable patterns, and draft a new skill plus an AGENTS.md update.

Frequently Asked Questions about agent-evolution

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

FAQPage Schema
When do I need to create a new skill from completed project work?

You need to create a new skill when pattern recognition across completed modules reveals recurring processes. This meta-skill analyzes finished work against a decision matrix to determine if documentation should crystallize into a reusable skill or just an AGENTS.md update.

How do I extract reusable patterns from completed module development?

Extract reusable patterns by reviewing completed tasks for recurring logic and applying knowledge crystallization. This skill provides a structured Draft Skill template and governance checks to accelerate converting those recognized patterns into standardized documentation.

What is the best way to standardize process improvement documentation across projects?

The best way to standardize process improvement is applying a decision matrix to evaluate completed work and generate structured skill definitions. This ensures consistent documentation updates and enforces governance checks across all recurring modules.

Does this skill creation process work without external dependencies?

Yes, this skill creation process works entirely standalone without external dependencies. It uses an internal decision matrix and draft structure to guide knowledge crystallization directly from your existing project artifacts.

Can I update governance files automatically when new patterns emerge?

You can update governance files by running this analysis after complex tasks. It determines when an AGENTS.md update is sufficient versus when a full skill definition is required, ensuring your governance documentation reflects emerging patterns.

What are the limitations of using a decision matrix for skill creation?

The limitation of using a decision matrix for skill creation is that it relies on analyzing already completed work. It cannot proactively predict future patterns and only enforces governance checks on crystallized knowledge from past module development.