Write an artefact-friendly markdown record of Miadi promotion decisions so later RISE and wiki waves can resume from explicit layer choices and blockers.
Installs into .claude/skills of the current project.
Are you the author of Promotion Decision Record?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/jgwill-promotion-decision-record)
---
name: promotion-decision-record
description: 'Write an artefact-friendly markdown record of Miadi promotion decisions so later RISE and wiki waves can resume from explicit layer choices and blockers.'
---
# Promotion Decision Record
After making promotion decisions, write a concise markdown record into the active artefact folder or working note.
## Purpose
The record should make later waves able to answer:
1. what candidates were considered
2. which layer each candidate belongs to
3. what blocked promotion
4. what draft work can happen next
5. whether any touched wiki repo was actually committed and pushed
## Required sections
1. `Scope`
2. `Evidence paths`
3. `Promotion matrix`
4. `Context-layer boundary notes`
5. `Blocked or deferred items`
6. `Draftable next steps`
7. `Publication status`
## Promotion matrix format
| Candidate | Decision | Target surface | Evidence | Rationale | Blockers |
| --- | --- | --- | --- | --- | --- |
Decisions should use the same vocabulary as the promotion architect:
- `keep in provenance`
- `promote to spec`
- `promote to wiki`
- `keep as context-layer note`
- `defer`
Prefer exact paths and compact rationale over broad summary language.
When a wiki repo was edited, record the repo path plus commit and push status, or the blocker that prevented publication.
