evolution

Orchestrate scanners, filters, proposals, and gate chains for Nova self-evolution.

2|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/TeamSPWK/nova --skill evolution-teamspwk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution
Source: https://github.com/TeamSPWK/nova/tree/main/.claude/skills/evolution
Command: npx skills add https://github.com/TeamSPWK/nova --skill evolution-teamspwk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nova self-evolution orchestrates and accelerates platform improvements by continuously incorporating external trends and internal feedback into Nova's rules, skills, and hooks.

Core Features & Use Cases

  • Orchestrates a structured pipeline: Scanner → Filter → Proposal → Gate Chain to generate, validate, and apply meta-improvements.
  • Supports multiple sources (Claude Code ecosystem, open tooling) to detect version updates and best practices, and translates them into actionable evolution tasks.
  • Enables governance-ready proposals with audit trails, versioning, and gating across environments to maintain stability while evolving.

Quick Start

Invoke /nova:evolve to start the self-evolution pipeline and apply meta-improvements automatically.

Frequently Asked Questions about evolution

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

FAQPage Schema
How do I automate self-improvement pipelines for Claude Code or Nova?

To automate self-improvement pipelines, invoke the /nova:evolve command to trigger the structured workflow. This orchestrates scanners and gate chains to automatically generate, validate, and apply meta-improvements across commands and hooks.

What is a gated deployment workflow for platform evolution?

A gated deployment workflow for platform evolution processes versioned proposals through a gate chain before applying them. This maintains platform stability by validating meta-improvements across environments while preserving audit trails.

How does automated self-evolution handle governance and auditability?

Automated self-evolution ensures governance and auditability through versioned proposals, gated deployments, and clear logging. This tracks all meta-improvements to rules and hooks, maintaining stability while validating changes across environments.

Can I detect external trends and best practices from the Claude Code ecosystem automatically?

Yes, integrated scanners automatically detect external trends, version updates, and best practices from the Claude Code ecosystem and open tooling. These sources are then translated into actionable evolution tasks for the pipeline.

Do I need to manually review proposals generated by the self-evolution pipeline?

Manual review requirements depend on your gate chain configuration. The pipeline generates governance-ready proposals with audit trails and versioning, using automated gating to validate and apply meta-improvements while maintaining stability.

When should I not use an automated evolution pipeline?

You should avoid automated evolution pipelines when your environment lacks support for gated deployments or versioned proposals. The pipeline enforces structured versioning and audit trails, making it unsuitable for rapid, untracked modifications without governance.