Dev Team Maturity Performance Skills — Data skill for Claude Code

Dev Team Maturity & Performance — Claude Skills

[](https://docs.claude.com/en/docs/claude-code/skills) [](LICENSE)

Three [Claude Agent Skills](https://docs.claude.com/en/docs/claude-code/skills) that turn a raw Jira export into a governed, explainable engineering-maturity analysis — no dashboards, no BI setup, no spreadsheet gymnastics. Point Claude at your data and ask.

Built as part of an MBA thesis prototype on AI-assisted engineering management. The skills are generic and reusable — no organization-specific data is included in this repo.

---

The problem

Engineering leaders are asked "how healthy is this team, really?" constantly, and usually answer it with one of three unsatisfying options:

• Gut feel — whoever talks to the team most often sets the narrative
• A BI dashboard someone built eighteen months ago that nobody trusts or maintains
• A one-off spreadsheet pull that takes an afternoon and goes stale the moment the sprint ends

None of these hold up when a board, a VP, or a thesis committee asks "show me the evidence." And when an LLM is dropped in to "just analyze the Jira data," it tends to invent plausible-sounding numbers when fields are missing, and invents interventions that sound reasonable but aren't grounded in anything repeatable.

How this solves it

These three skills turn that into a governed, repeatable workflow:

1. maturity-onboarding — a one-time (or per-change) setup wizard that captures how your organization actually tracks work in Jira, and produces versioned config files.
2. maturity-engine — reads those config files plus your Jira export and produces a maturity report: facts (computed KPIs), signals (rule-based patterns), and interventions (from a fixed catalog) — never blended together, never invented.
3. **`matu