Scan repo for skill creation opportunities and establish skill lifecycle management

[jeremyeder]

Summary

The platform repo has 10 project skills in .claude/commands/ (speckit suite, acp-compile, jira.log) but no systematic process for discovering new skill opportunities or managing skill lifecycle. We need to audit the repo for automation gaps and establish a lifecycle framework that works across all ACP repos.

Skill Audit: What to Scan For

Examine developer workflows and repetitive operations that could become skills:

• Deployment: make deploy, make kind-up, environment setup — no skill exists today
• Debugging/Troubleshooting: Operator log analysis, session failure triage, pod status checks
• Backend development: Handler scaffolding, CRD field additions, API endpoint creation
• Frontend development: Component scaffolding, page creation with loading/error states
• Testing: E2E test authoring, test data setup, coverage gap analysis
• Release: Changelog generation, version bumping, image tagging
• Operator workflows: CRD schema changes, reconciler modifications, watch handler additions
• Documentation: ADR creation, context file updates, MkDocs page scaffolding
• Code review: Security pattern checks, RBAC compliance, pre-commit validation

Current Skills (for reference)

Skill	Purpose
speckit.* (8 skills)	Feature specification lifecycle
acp-compile	Submit plan to ACP for execution
jira.log	Log Jira issues to RHOAIENG

Skill Lifecycle Framework

Establish a standard for managing skills across their full lifecycle:

1. Discovery & Proposal

• Convention for proposing new skills (issue template? RFC?)
• Criteria for when a workflow warrants a skill vs. staying ad-hoc

2. Versioning

• Add version field to .claude/commands/ skill frontmatter
• Semantic versioning (MAJOR.MINOR.PATCH)

3. Lifecycle States

• Define states: alpha → beta → stable → maintenance → deprecated
• Add status field to skill frontmatter

4. Health & Usage Tracking

• Mechanism to track skill usage (invocation counts, error rates)
• Staleness detection (skills that haven't been updated in N months)

5. Deprecation

• deprecated: true and replacement: new-skill-name in frontmatter
• Deprecation warnings when invoking deprecated skills

6. Cross-Repo Coordination

• Shared lifecycle standards across ambient-code/platform, ambient-code/mcp, and ambient-code/workflows
• Companion issues: filed in mcp and workflows

Acceptance Criteria

• Audit complete: list of candidate skills with priority ranking
• Skill lifecycle standard documented (states, versioning, deprecation)
• At least 2 new high-value skills created from audit findings
• Cross-repo lifecycle alignment confirmed with mcp and workflows repos

[jeremyeder]

Companion issues:

• Scan repo for skill creation opportunities and establish skill lifecycle management mcp#30
• Scan repo for skill creation opportunities and establish skill lifecycle management workflows#43