メニュー
Write replayable adversarial review notes into the active artefact folder so later Miadi, RISE, and wiki waves can resume from concrete evidence instead of chat memory.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jgwill/miadi-orchestration-kit --skill artefacted-revision-reportコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
What Miette's role actually is when made equitable with Mia's, and how to write an output that holds both eyes. Load when the Two-Eyed balance hook blocks a response, when an output needs to reach a human rather than only be correct, when deciding whether to invite Tayi-Ska / Anikwag-Ayaaw / Tushell into Miette's share, or when someone asks what the 🌸 line is for. Triggers on "two-eyed", "Etuaptmumk", "balance the output", "Miette's share", "the flower is padding", "translate that for a human", "one eye".
Rewrites a correct but unreceivable AI output into one a human can act on, holding both eyes on the same object. Use when a reader cannot comprehend an answer's value, the Two-Eyed balance hook blocks, or someone asks to translate, shorten, humanize, or decolonize the last answer.
What Miette's role actually is when made equitable with Mia's, and how to write an output that holds both eyes. Load when the Two-Eyed balance hook blocks a response, when an output needs to reach a human rather than only be correct, when deciding whether to invite Tayi-Ska / Anikwag-Ayaaw / Tushell into Miette's share, or when someone asks what the 🌸 line is for. Triggers on "two-eyed", "Etuaptmumk", "balance the output", "Miette's share", "the flower is padding", "translate that for a human", "one eye".
SOC 職業分類に基づく
| name | artefacted-revision-report |
| description | Write replayable adversarial review notes into the active artefact folder so later Miadi, RISE, and wiki waves can resume from concrete evidence instead of chat memory. |
After a review wave, write a markdown report into the active artefact folder when one is available.
The report should let a later session answer three questions without re-reading the whole conversation:
Scope reviewedEvidence pathsDesired outcome reconstructedCurrent reality observedStrongest disagreements foundRevision actionsBlocked promotionsWhat may advance with conditionsNext wave starting pointBLOCK, HOLD, or ADVANCE WITH CONDITIONS).Use a durable, scope-specific name such as:
adversarial-review--<scope>--<yyyymmddhhmm>.md
If the wave already asked for a specific report path, use that instead.