promote

ADD Promote Command v{{VERSION}}

Assess readiness and promote the project's maturity level. Maturity is the master control for all ADD behavior — promotion is intentional, evidence-based, and deliberate.

• --check (default) — Gap analysis: scan evidence against next level's requirements
• --execute — Gap analysis + promotion interview + apply level change

---

Pre-Flight

1. Read .add/config.json — extract maturity.level, promoted_from, promoted_date, next_promotion_criteria
   • If not found: abort with "No ADD project found. Run /add:init first."
2. Read ${CLAUDE_PLUGIN_ROOT}/references/maturity-matrix.md — load cascade matrix + promotion process (source of truth for level requirements)
3. Read docs/prd.md — project context, maturity references
4. Read CLAUDE.md — check for maturity references

Edge Cases

Already at GA: "Project is at GA — the highest maturity level. No further promotion available. Run /add:verify to check compliance."

--target below current level: Trigger demotion flow (see below).

--target skips a level (e.g., poc → beta): "Cannot skip levels. Progression is sequential: poc → alpha → beta → ga. Next available: {next_level}."

No --target: Default to next level in sequence.

---

Command: /promote --check (default)

Scan project evidence and present readiness report. No file modifications.

Step 1: Determine Target

Current maturity: {CURRENT}
Assessing readiness for: {TARGET}

Step 2: Evidence Scan

Use Glob, Grep, Bash, Read to gather real data across these categories:

#	Category	How to Check
1	Feature specs	Glob specs/*.md, count files, check for acceptance criteria
2	Test coverage	Run test command from config quality.test.unit with coverage flag. If no test command configured, score as MISSING. If command fails, score as PARTIAL and note the error.
3	CI/CD pipeline	Glob .github/workflows/*.yml, .gitlab-ci.yml, Jenkinsfile
4	PR workflow	git log --merges --oneline -20 — check for merge commits
5	Environments	Read config environments — count tiers with non-null URLs
6	Conventional commits	git log --oneline -20 — check feat:/fix:/docs: compliance %
7	TDD evidence	Compare test vs implementation file timestamps
8	Branch protection	Check .github/settings.yml or gh api if available
9	Release tags	git tag -l 'v*' — check for semver tags
10	Quality gates	Check .pre-commit-config.yaml, .husky/, CI check configs
11	Milestones completed	Glob docs/milestones/*.md — count COMPLETE milestones
12	Learnings captured	Read .add/learnings.json — count entries
13	PRD depth	Read docs/prd.md — assess completeness for target level
14	Stability	git log --since="30 days ago" --oneline — check for hotfix-free stability