Scan repo for skill creation opportunities and establish skill lifecycle management #43
Description
Summary
Scan the workflows repo for repetitive operations and developer patterns that could be packaged as Claude Code skills. The workflows repo manages schema'd, versioned SDLC preference files — there are likely strong candidates for automation here. Align with the skill lifecycle framework being established across all ACP repos.
Skill Audit: What to Scan For
Examine workflow authoring and management patterns for skill opportunities:
- Workflow authoring: Scaffolding new workflow definitions, schema creation
- Validation: Workflow file linting, schema compliance checks, best-practice enforcement
- Migration: Upgrading workflow schemas between versions, field deprecation handling
- Testing: Workflow execution testing, dry-run validation, edge case generation
- Documentation: Auto-generating workflow docs from schema, capability summaries
- Onboarding: Guided workflow creation for new teams, preference questionnaires
- Diff/Compare: Comparing workflow configurations across teams, environments, or versions
- Publishing: Version bumping, changelog generation, release workflows
Skill Lifecycle Framework
Adopt the cross-repo lifecycle standard being defined in ambient-code/platform:
- Versioning: Semantic versioning in skill frontmatter
- Lifecycle states:
alpha→beta→stable→maintenance→deprecated - Health tracking: Usage metrics, staleness detection
- Deprecation: Explicit
deprecatedfield with replacement pointers
Companion Issues
Acceptance Criteria
- Audit complete: list of candidate skills with priority ranking
- Skill lifecycle frontmatter adopted (version, status fields)
- At least 1 new skill created from audit findings
- Lifecycle alignment confirmed with platform and mcp repos