Add AI Agent Skills & Rules as sub-category of Software Resources

[justinb-dfw]

Feature Request

User Story

As an infrastructure team member managing AI-driven automation,
I want AI Agent Skills and Rules tracked as a sub-category of Software Resources,
so that I can inventory, version, and relate agent configurations (skills, rules, prompts) to the software systems and teams that depend on them.

Proposed Solution

Add two new sub-category types under the existing Software Resources category:

1. AI Agent Skills — Tracks individual skill definitions (name, description, trigger conditions, associated tooling). Each skill record links to the software project or service it supports.
2. AI Agent Rules — Tracks rule sets and instruction files (e.g., CLAUDE.md, .claude/rules/*.md, global rules) that govern agent behavior. Each rule record can be linked to one or more projects, teams, or environments.

Integration points:

• Skills and Rules should be linkable to existing Software Resource entities (repos, services, containers) via Elder's relationship graph
• Support versioning so teams can track when rules/skills changed
• Tags/labels for scope: global, project-specific, user-specific

Alternatives Considered

• Flat tagging on existing Software Resources — simpler but loses the distinction between a skill (behavioral capability) and a rule (governance/constraint). Sub-categories preserve semantics.
• Separate top-level category — too heavy; skills and rules are tightly coupled to software projects and belong under the Software Resources umbrella.

Acceptance Criteria

• "AI Agent Skills" available as a sub-category when creating/editing a Software Resource
• "AI Agent Rules" available as a sub-category when creating/editing a Software Resource
• Skills and Rules can be linked to existing Software Resources via relationships
• Version tracking supported for skill/rule records
• Scope tags (global, project-specific, user-specific) available
• Tests pass (unit + integration)
• Linting passes
• Security scan passes

Component

backend

Priority

medium

Business Value

As organizations adopt AI coding agents (Claude Code, Copilot, Cursor, etc.), the skills and rules that govern these agents become critical infrastructure artifacts. They affect code quality, security posture, and developer workflow. Tracking them in Elder alongside the software they support provides visibility into what rules are active, which projects they apply to, and how they evolve over time — closing a gap in infrastructure asset management.

License Tier

• Community (free)
• Professional
• Enterprise