Carnegie Quality Strategy

Transforms your AI agent into an elite Software Quality Director with a tailored Software Quality Test Strategy.

Install
cmdop skills install agensi-carnegie-quality-strategy

Carnegie Quality Strategy is an AI agent skill published by agensi that configures an agent to act as a Software Quality Director for a given codebase. It follows a four-step workflow: repository inspection, maturity assessment, Carnegie principle mapping, and strategy generation.

During the inspection phase, the skill analyzes dependency manifests, CI/CD pipeline configurations, existing test suites, and high-risk code areas such as authentication and payment flows. This produces a Product Understanding Report that grounds all subsequent recommendations in specific file paths, frameworks, and identified gaps rather than generic advice.

The maturity assessment categorizes the project on a scale from Level 0 to Level 5, so the resulting plan is calibrated to the actual state of the codebase rather than an idealized baseline. The skill then maps twenty Carnegie human-centered principles to the findings, producing recommendations that address both technical debt and engineering culture, including stakeholder engagement guidance.

The final output is a quality-strategy.md file covering test engineering, defect management, and a 30-60-90 day execution plan. This document is structured for presentation to CTOs or Engineering Managers. The skill is appropriate when a team needs a written, evidence-based quality strategy rather than ad-hoc testing advice. It is not a runtime testing tool and does not execute tests or modify code directly.

Use cases

  • Generate a repository-aware test strategy document for a new engineering engagement
  • Assess a codebase's quality maturity level before planning a testing overhaul
  • Identify gaps in CI/CD pipelines and test suites with references to specific files
  • Produce a 30-60-90 day quality execution plan to present to engineering leadership
  • Map human-centered engineering culture recommendations to an existing codebase
  • Audit high-risk code areas such as auth or payments for testing coverage gaps

When to use it

  • A team needs a structured, written quality strategy grounded in their actual repository state
  • Engineering leadership requires a presentable strategy document for CTOs or Engineering Managers
  • A project is being assessed for quality maturity before committing to a testing roadmap
  • Generic AI testing advice has proven too abstract to be actionable for the team

When not to use it

  • The goal is to execute tests or generate test code directly rather than produce a strategy document
  • No repository is available for the skill to inspect, as it requires a codebase to analyze
  • The need is for real-time or runtime quality monitoring rather than a one-time strategy report
  • The team wants automated CI integration rather than a static markdown deliverable