using-sdlc-engineering

# SDLC Engineering Router

## Overview

This skill routes SDLC-related requests to the appropriate specialist skill within the axiom-sdlc-engineering skillpack. It detects the project's CMMI maturity level and ensures users receive guidance tailored to their context.

**Core Principle**: Match the right process rigor to the project's needs. Not all projects need Level 3 or 4 formality.

## When to Use

Use this skill when requests involve:
- **Requirements management** (tracking, traceability, change control)
- **Design and architecture** (ADRs, design reviews, coding standards)
- **Quality assurance** (testing, code reviews, verification, validation)
- **Governance and risk** (decision documentation, risk management)
- **Metrics and measurement** (what to measure, how to analyze)
- **Process adoption** (implementing CMMI on existing projects)
- **Platform integration** (GitHub, Azure DevOps implementation patterns)
- **General SDLC questions** (where to start, what process to follow)

**When NOT to use**: Implementation details for specific technologies (Python testing → axiom-python-engineering, security → ordis-security-architect).

## CMMI Level Detection

**Priority order** (check in this sequence):

1. **CLAUDE.md configuration**: Look for `CMMI Target Level: X` or `CMMI Level: X`
2. **User message**: Explicit mention ("Level 2", "Level 3", "Level 4", "CMMI L3")
3. **Context clues**:
   - "FDA", "medical device", "royal commission" → Level 3-4 (regulatory rigor)
   - "startup", "small team", "2-3 developers" → Level 2 (lightweight)
   - "audit", "compliance", "SOC 2" → Level 3 (organizational standards)
4. **Default**: Level 3 (good balance of rigor and agility)

**Level Summary**:
- **Level 2 (Managed)**: Minimal viable practices, ~5% overhead, 1-5 person teams
- **Level 3 (Defined)**: Organizational standards, ~10-15% overhead, 5+ person teams, audit-ready
- **Level 4 (Quantitatively Managed)**: Statistical process control, ~20-25% overhead, regulated indust