career-ladder

Automate per-agent level promotions and demotions from quarterly performance and roster data.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill career-ladder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: career-ladder
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/career-ladder
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill career-ladder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Per-agent level progression within a tier, automating promotions (L1 → L2 → L3) and demotions according to defined gates, bootstrap rules, and quarterly cadence to reduce manual overhead and errors.

Core Features & Use Cases

  • Reads performance history, gate definitions, and roster data to compute promotions and demotions.
  • Writes updated levels to _vision/roster/levels-<date>.md and creates ADRs for each level change, supporting auditability.
  • Supports bootstrap for new rosters and maintains history for governance and mentorship tracking.

Quick Start

Run the career-ladder skill during the quarterly heartbeat to update all agent levels and generate corresponding ADRs.

Frequently Asked Questions about career-ladder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate agent promotions and demotions based on quarterly performance?

You can automate agent promotions and demotions by running a quarterly heartbeat process that reads performance history and roster data to compute level changes, writing updated levels to dated markdown files and generating ADRs for audit purposes.

What is per-agent level progression governance and how does it work?

Per-agent level progression governance automates tier transitions such as L1 to L2 to L3 by applying defined gate definitions, bootstrap rules, and quarterly cadence to reduce manual overhead while preserving audit history through generated ADRs.

How do I generate ADRs for agent level changes during a roster upgrade?

Generating ADRs for agent level changes happens automatically during quarterly heartbeat or ad-hoc roster-upgrade events when the system computes promotions and demotions, creating an Architecture Decision Record for each individual level change to support auditability.

Can I bootstrap level progression for a new roster without prior performance history?

Yes, bootstrap support for new rosters is included in the level progression process, allowing initial agent levels to be established and maintained with history tracking for governance and mentorship without requiring existing performance data.

What's the best way to maintain audit history for agent tier promotions and demotions?

Maintaining audit history for agent tier changes is handled by writing updated levels to dated markdown files in the roster directory and creating an ADR for each promotion or demotion, preserving a complete record for governance tracking.