skill-ops-plannerlisted

## Pattern declaration Primary pattern: Pipeline Secondary patterns: Reviewer, Inversion Why: portfolio planning requires strict phase order (inventory → classify → policy → metrics → roadmap) with review checkpoints at each stage. Inversion is needed at Phase 0 to block progress when inventory data is insufficient. ## 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 any of the above cannot be determined: - stop and ask the user for the missing information - do not proceed to Phase 1 until at least active skills and current storage layout are confirmed - if no inventory exists at all, output an inventory-first plan and stop ## Phase 1: Inventory and pattern segmentation For each skill, record: - owner - purpose - invocation policy (auto vs manual) - risk level - primary pattern (Tool Wrapper / Generator / Reviewer / Inversion / Pipeline) - secondary patterns - current eval maturity - review requirement Output each skill as a structured record: ```text skill: <name> owner: <person or team> purpose: <one line> invocation: auto | manual risk: low | medium | high primary_patt