skill-ops-planner

Define governance frameworks for live Claude Code skill portfolios.

2|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/s977043/plangate --skill skill-ops-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-ops-planner
Source: https://github.com/s977043/plangate/tree/main/.claude/skills/skill-ops-planner
Command: npx skills add https://github.com/s977043/plangate --skill skill-ops-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It enables teams to define, govern, and evolve a live portfolio of Claude Code skills, ensuring consistent ownership, lifecycle management, and measurable governance across repositories.

Core Features & Use Cases

  • Portfolio inventory and ownership mapping
  • Lifecycle policy definition (proposed, experimental, production, deprecated, retired)
  • Evaluation, rollout, and retirement governance
  • Periodic review cadence and documentation standards

Quick Start

Assess your current skill portfolio and draft a starter governance plan for active skills.

Frequently Asked Questions about skill-ops-planner

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

FAQPage Schema
How do I set up governance for a portfolio of Claude Code skills?

Portfolio governance for Claude Code skills is established by defining a framework that specifies portfolio structure, ownership, lifecycle stages, and evaluation policy. This framework ensures consistent ownership and measurable governance across multiple repositories.

What is the lifecycle policy for managing live skills across teams?

A lifecycle policy for live skills defines stages including proposed, experimental, production, deprecated, and retired. This policy manages how skills evolve and eventually phase out across teams or repositories.

How do I audit and measure the effectiveness of existing Claude Code skills?

Auditing and measuring existing Claude Code skills requires applying an evaluation policy and periodic review cadence. This process maps portfolio inventory and ownership to ensure skills meet documented governance standards.

When do I need a formal retirement policy for deprecated skills?

A formal retirement policy for deprecated skills is needed when scaling a live portfolio across teams or repositories. It defines the governance rules for safely retiring skills that are no longer effective or relevant.

Can I use this governance framework to organize skills across multiple repositories?

Yes, you can use this governance framework to organize skills across multiple repositories. It applies directly to scenarios involving portfolio inventory mapping and consistent ownership measurement across distributed team environments.