Skip to content
cccskills
FreePublished on GitHub

artifact-lifecycle

Unified lifecycle management for all framework artifacts (skills, agents, hooks, workflows, templates, schemas)

The English summary is being prepared. Showing the original description.

See how to install

Files included (10)

  • SKILL.md6.4 KB
  • commands/artifact-lifecycle.md118 B
  • hooks/post-execute.cjs314 B
  • hooks/pre-execute.cjs431 B
  • references/research-requirements.md398 B
  • rules/artifact-lifecycle.md299 B
  • schemas/input.schema.json584 B
  • schemas/output.schema.json262 B
  • scripts/main.cjs1.1 KB
  • templates/implementation-template.md192 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Artifact Lifecycle Skill

Convenience wrapper for the unified artifact lifecycle workflow.

Overview

This skill provides a simplified interface to the comprehensive artifact lifecycle management workflow at .claude/workflows/core/skill-lifecycle.md.

When to Use

Use this skill when you need to:

  • Create a new artifact (skill, agent, hook, workflow, template, schema)
  • Update an existing artifact
  • Deprecate an artifact with migration guidance
  • Check if an artifact already exists

Quick Start

// Invoke this skill
Skill({ skill: 'artifact-lifecycle' });

Workflow Reference

Full Workflow: .claude/workflows/core/skill-lifecycle.md

Phases

Phase 1: Discovery

Check if artifact exists, compare versions.

Agent: architect Output: Discovery report with recommendations

Phase 2: Decision

Determine action: CREATE, UPDATE, or DEPRECATE.

Agent: planner Output: Action plan with tasks

Phase 3: Action

Execute the determined action.

Agent: developer + appropriate creator skill Tools:

  • Skill({ skill: "skill-creator" }) for skills
  • Skill({ skill: "agent-creator" }) for agents
  • Skill({ skill: "hook-creator" }) for hooks
  • Skill({ skill: "workflow-creator" }) for workflows

Phase 4: Integration

Update registries, catalogs, and CLAUDE.md.

Agent: developer Updates:

  • creator-registry.json
  • skill-catalog.md (for skills)
  • CLAUDE.md Section 3 (for agents) or Section 8.5/8.6 (for skills/workflows)

Phase 5: Validation

Test integration and verify references.

Agent: qa Checks:

  • Artifact invocable
  • References valid
  • No broken cross-references

Usage Examples

Create New Skill

User: "Create a skill for Kubernetes deployment"

Router spawns with:
Skill({ skill: "artifact-lifecycle" })

Workflow determines: CREATE mode
Invokes: skill-creator
Updates: registry, catalog, CLAUDE.md
Validates: skill invocable

Update Existing Agent

User: "Update the devops agent to support Terraform Cloud"

Router spawns with:
Skill({ skill: "artifact-lifecycle" })

Workflow determines: UPDATE mode
Version: 1.0.0 → 1.1.0
Updates: agent file, CHANGELOG
Validates: agent referenced correctly

Deprecate Workflow

User: "Deprecate the old deployment workflow"

Router spawns with:
Skill({ skill: "artifact-lifecycle" })

Workflow determines: DEPRECATE mode
Adds: deprecation notice, migration guide
Updates: CLAUDE.md with replacement reference
Validates: no broken references

Configuration

ParameterValuesDefault
artifact_typeskill, agent, hook, workflow, template, schemaauto-detect
operationcreate, update, deprecate, integrateauto-detect
version_bumpmajor, minor, patchminor

Iron Laws

  1. ALWAYS use type-specific creator skills — never treat artifact-lifecycle as a shortcut that bypasses research-synthesis, companion-check, or validation; each phase exists for a reason.
  2. ALWAYS determine operation mode before starting action (CREATE/UPDATE/DEPRECATE) — never begin Phase 3 without a confirmed Phase 2 decision; wrong operation = wasted or dangerous work.
  3. NEVER skip Phase 5 validation — artifacts must be verified as invocable before the lifecycle task is marked complete; broken artifacts delivered as complete are worse than none.
  4. ALWAYS update catalog and CLAUDE.md in Phase 4 — artifacts without catalog/routing entries are invisible to agents and the router; integration without registration is incomplete.
  5. NEVER use artifact-lifecycle for simple single-artifact updates — use type-specific updaters (skill-updater, agent-updater, workflow-updater); lifecycle is for multi-phase orchestration only.

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Skipping research-synthesis before CREATERisk of creating a duplicate or outdated artifactAlways run research-synthesis first
Starting action before Phase 2 decisionWrong operation applied; CREATE when UPDATE neededComplete Phase 2 before Phase 3
Skipping Phase 5 validationBroken artifacts delivered as completeAlways run invocability check
No catalog/registry update in Phase 4Artifact is invisible to agents and routerAlways update catalog, registry, and CLAUDE.md
Using artifact-lifecycle for simple version bumpsHeavyweight process for lightweight workUse skill-updater/agent-updater for UPDATE mode
Not specifying artifact_typeWrong creator skill invoked silentlyAlways specify or verify artifact_type in Phase 1

Memory Protocol

  1. Read .claude/context/memory/learnings.md before starting
  2. Record decisions to .claude/context/memory/decisions.md
  3. Record issues to .claude/context/memory/issues.md

Related Skills

  • skill-creator - Direct skill creation
  • agent-creator - Direct agent creation
  • workflow-creator - Direct workflow creation
  • codebase-integration - External artifact integration

Related Workflows

  • .claude/workflows/core/skill-lifecycle.md - Full lifecycle workflow
  • .claude/workflows/core/external-integration.md - External artifact integration
  • .claude/workflows/core/router-decision.md - Router decision flow

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Ensure accessibility in UI components including semantic HTML, ARIA attributes, keyboard navigation, and WCAG 2.2 AA compliance.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Use when you want to improve response quality through meta-cognitive reasoning. Applies 15+ reasoning methods to reconsider and refine initial outputs.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

N-round opposing-stance debates for trade-off analysis. Assigns pro/con roles to agents, runs structured debate rounds with quality scoring, and produces a moderator synthesis with confidence-rated recommendation. Generalizable to architecture, technology, security, and design decisions.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Force adversarial code review stance that eliminates confirmation bias — reviewer must find issues or re-analyze

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Creates specialized AI agents on-demand when no existing agent matches a request. Use when the Router cannot find a suitable agent for a task. Enables self-evolution by generating persistent agents.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

LLM-as-judge evaluation framework with 5-dimension rubric (accuracy, groundedness, coherence, completeness, helpfulness) for scoring AI-generated content quality with weighted composite scores and evidence citations

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

See all skills by oimiragieo

Report a problem with this skill