Maps CMMI processes to GitHub and Azure DevOps features for requirements traceability, quality gates, configuration management, measurement, and platform migration.
npx claudepluginhub tachyon-beep/skillpacks --plugin axiom-sdlc-engineeringThis skill uses the workspace's default tool permissions.
This skill provides concrete implementation guidance for mapping CMMI process areas to GitHub and Azure DevOps platform features.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
This skill provides concrete implementation guidance for mapping CMMI process areas to GitHub and Azure DevOps platform features.
Core principle: CMMI defines WHAT processes are required. This skill shows HOW to implement them in your platform with production-ready configurations.
Platforms covered:
Reference: See docs/sdlc-prescription-cmmi-levels-2-4.md for CMMI process area definitions.
Use this skill when:
Do NOT use for:
| CMMI Process Area | GitHub Feature | Azure DevOps Feature | Reference Sheet |
|---|---|---|---|
| REQM (Requirements Management) | Issues, Projects, Labels | Work Items, Queries, Backlogs | github-requirements.md, azdo-requirements.md |
| CM (Configuration Management) | Branch Protection, CODEOWNERS | Branch Policies, Required Reviewers | github-config-mgmt.md, azdo-config-mgmt.md |
| VER + VAL + PI (Quality) | Actions, Status Checks, PRs | Pipelines, Gates, Test Plans | github-quality-gates.md, azdo-quality-gates.md |
| MA (Measurement) | Insights, API, Actions | Analytics, Dashboards, OData | github-measurement.md, azdo-measurement.md |
| DAR + RSKM (Governance) | Discussions, Wiki, Issues | Wiki, Custom Work Items | github-audit-trail.md, azdo-audit-trail.md |
Best for:
Strengths:
Limitations:
CMMI Maturity:
Best for:
Strengths:
Limitations:
CMMI Maturity:
Common patterns:
Integration options:
The following reference sheets provide detailed, production-ready implementation guidance for each platform.
When to use: Implementing REQM (Requirements Management) in GitHub
→ See github-requirements.md
Covers:
Implements #123, Closes #456)When to use: Implementing CM (Configuration Management) in GitHub
→ See github-config-mgmt.md
Covers:
When to use: Implementing VER, VAL, PI (Verification, Validation, Integration) in GitHub
→ See github-quality-gates.md
Covers:
When to use: Implementing MA (Measurement & Analysis) in GitHub
→ See github-measurement.md
Covers:
When to use: Compliance and audit requirements in GitHub
→ See github-audit-trail.md
Covers:
When to use: Implementing REQM (Requirements Management) in Azure DevOps
→ See azdo-requirements.md
Covers:
When to use: Implementing CM (Configuration Management) in Azure DevOps
→ See azdo-config-mgmt.md
Covers:
When to use: Implementing VER, VAL, PI (Verification, Validation, Integration) in Azure DevOps
→ See azdo-quality-gates.md
Covers:
When to use: Implementing MA (Measurement & Analysis) in Azure DevOps
→ See azdo-measurement.md
Covers:
When to use: Compliance and audit requirements in Azure DevOps
→ See azdo-audit-trail.md
Covers:
| Mistake | Why It Fails | Better Approach |
|---|---|---|
| Treating platform as CMMI-aware | Platforms don't enforce CMMI; you configure enforcement | Map each CMMI practice to platform feature explicitly |
| Using platform defaults | Defaults are permissive (no quality gates, no reviews) | Configure branch protection, required checks, policies |
| Manual traceability | Spreadsheet traceability becomes stale immediately | Automate with issue/PR links, work item queries, API |
| Skipping audit trail setup | Compliance failures discovered during audit | Configure retention, access logs, history from project start |
| One-size-fits-all configuration | Level 2 project gets Level 4 overhead (or vice versa) | Scale configuration based on CMMI target level |
| Forgetting baselines | No way to freeze requirements or code for releases | Implement baseline tagging, release branches, milestone freezes |
| Ignoring platform limitations | GitHub weak at test management; Azure DevOps weak at code review | Use hybrid approach or third-party tools for gaps |
| No verification automation | Traceability breaks without detection | Scheduled checks for orphaned requirements, missing links |
| Generic metrics | Collecting data nobody uses | GQM approach: Goal → Question → Metric (actionable only) |
| Missing cross-process links | Requirements don't link to risks; tests don't link to design | Document integration patterns in configuration |
| When You're Doing | Also Use | For |
|---|---|---|
| Platform setup for requirements | requirements-lifecycle | REQM/RD process definitions |
| Platform setup for CI/CD | design-and-build | TS/PI process definitions |
| Platform setup for testing | quality-assurance | VER/VAL process definitions |
| Platform setup for metrics | quantitative-management | MA/QPM metrics definitions |
| Platform selection decision | governance-and-risk | Decision analysis for platform choice |
| Initial platform adoption | lifecycle-adoption | Incremental rollout strategy |
Remember: Platforms don't enforce CMMI compliance automatically. You must configure them to implement CMMI practices. This skill provides the configuration patterns to bridge CMMI policy to platform reality.