skill-ops-plannerlisted

## Purpose Plan how a team should operate a set of skills over time. Your job is to define: - portfolio structure - ownership - lifecycle stages - evaluation policy - rollout policy - retirement policy - review cadence ## Phase 0: Portfolio gate Before planning, identify: - active skills - target users or teams - current pain points - risk level by skill category - current review process - current storage layout - current evaluation maturity If the current inventory is missing: - create an inventory-first plan - do not pretend portfolio governance already exists ## Phase 1: Inventory and segmentation Group skills by type: - knowledge - workflow automation - investigation / read-only - review / verification - side-effecting operational tasks For each group, define: - owner - auto vs manual invocation policy - tool restriction level - validation requirement - retirement signals ## Phase 2: Lifecycle policy Define lifecycle stages: 1. proposed 2. experimental 3. team-approved 4. production 5. deprecated 6. retired For each stage, define: - entry criteria - required eval coverage - review requirement - allowed blast radius - logging requirement ## Phase 3: Metrics and governance Define portfolio metrics: - trigger precision - task success rate - review pass rate - rollback rate - mean tool count - failure recurrence - stale skill count Also define: - monthly review cadence - change approval policy - emergency disable policy - documentation freshness policy