メニュー
Summarize the current Cadenza phase state from STATUS.yaml and trace files. Use this when the user asks for current phase status, open batches, blockers, exit criteria, or the next actionable Cadenza batch.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Best-practice authoring guidance for Cadenza decks. Use this skill whenever the user asks to create, revise, debug, validate, or review a Cadenza deck, Cadenza TSX, Cadenza skills, render-safe components, typed slide APIs, speaker notes, motion timing, browser preview behavior, or diagnostics-driven repair, even if they do not explicitly say "skill" or "best practices."
Run Cadenza Builder implementation work across phases. Use this skill whenever the user asks for Builder, a SPEC_TEST_MATRIX batch, TDD, RED GREEN REFACTOR, remediation implementation, trace update, or package/test work in Cadenza, even when they only name a phase kick file. This skill requires the phase kick file and frozen specs for concrete scope.
Run Cadenza Architect work across phases. Use this skill whenever the user asks for Architect, Stage A, Stage B, specs, Freeze Candidates, contract design, ADR routing, or phase contract freeze work in Cadenza, even when they only name a phase kick file. This skill preserves phase-specific kick files as the concrete task entrypoints.
Prepare Cadenza Wizard handoffs at workflow boundaries. Use this skill whenever the user asks for Wizard work, a next Architect kick file, phase-boundary handoff, Phase 0 bootstrap from Scout to Architect, Scout-to-Architect planning, or any Cadenza handoff that must summarize accepted inputs without changing specs, production code, or phase pointers.
Run an independent Cadenza review after Builder work, phase closeout, or maintainer-selected high-risk changes. Use this skill whenever the user asks for reviewer, review Builder output, audit implementation against frozen specs, validate phase closeout, or produce remediation findings for Cadenza, even if they do not explicitly name the skill.
Lint Cadenza spec files and surface structural findings. Use this when the user invokes cadenza-spec-lint, asks to validate spec structure, edits spec/**/*.md, or needs the spec:lint completion gate.
| name | cadenza-phase-status |
| description | Summarize the current Cadenza phase state from STATUS.yaml and trace files. Use this when the user asks for current phase status, open batches, blockers, exit criteria, or the next actionable Cadenza batch. |
Use this skill to report Cadenza's current phase without inventing missing
fields. If a value is absent from the source files, write not recorded.
STATUS.yaml to resolve current_phase, owners, start date, and exit gate.trace/<current-phase>/status.yaml for machine-readable deliverable and
exit-criteria status. If the file is empty or missing, report that.trace/<current-phase>/tracker.md for timeline entries, open batches,
blockers, and decisions.Return exactly this structure:
Phase: <current_phase> - <name> (<status>)
Owners: <comma-separated list>
Started: <date or "not recorded">
Exit gate: <path to exit criteria doc>
Open batches:
- <ID> <name> [<status>] <blocker if any>
Recently completed (last 3 timeline entries):
- <date> - <summary>
Blockers:
- <item from tracker.md Blockers section>, or "none"
Exit criteria:
- <ID> <description> - <met | partial | not_met | not recorded>
After the report, add one line:
Next actionable batch (lowest-blocker): <ID>
If every open batch is blocked, instead write:
All open batches are blocked; resolve <blocker-description> first.
Do not summarize files outside this read list unless the user asks.