메뉴
Must use this skill when user triggers /ezfl:reflect or requests viewing metrics / overrides / improvement suggestions. Aggregates .harness/metrics/ and .harness/overrides.log, outputs a retrospective report.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Scans project-level agent directories before subagent dispatch, recommends based on phase keywords, lets user choose, and persists results to disk for anti-corruption
Must use this skill when user triggers /ezfl:audit or requests auditing of implementation outputs. Executes Constitution compliance check (injection point D) + 5 scorer scripts, results written to .harness/metrics/<timestamp>-metrics.json.
Must use this skill when user triggers /ezfl:build or requests implementation / execution of tasks.md. Selects implementer subagent, which executes /opsx:apply in its own session — main agent is forbidden from directly writing implementation code.
Must use this skill when user triggers /ezfl:constitution or /openspec:constitution, or requests creation / amendment / viewing of the project constitution. Manages CREATE / AMEND / SHOW modes for openspec/memory/constitution.md.
Must use this skill when user triggers /ezfl:design or requests entering the design phase. Only responsible for design discussion, Reframe, Premise Challenge, and producing pre_design.md.
Must use this skill when user triggers /ezfl:lock, or requests engineering review / locking plan / review architecture / tech review, or describes a non-trivial change (>3 files, new components, cross-module changes) and is clearly in the pre-coding phase. Reviews plans/proposals from an engineering-manager perspective with adversarial rigor (architecture, data flow, edge cases, test coverage, performance), aiming to find holes rather than go through the motions. **Do NOT** use for: simple bug fixes / single-file changes / pure documentation or configuration changes / requesting 'review of already written code' (that's code review, not plan review).
| name | reflect |
| description | Must use this skill when user triggers /ezfl:reflect or requests viewing metrics / overrides / improvement suggestions. Aggregates .harness/metrics/ and .harness/overrides.log, outputs a retrospective report. |
Must output on startup: [easy-flow] entering phase: reflect — using easy-flow:reflect skill.
Metrics retrospective skill. Aggregates historical data under .harness/metrics/, analyzes trends, generates improvement suggestions.
/ezfl:reflect — outputs current project metrics overview/ezfl:reflect monthly — outputs monthly retrospective report.harness/metrics/*-metrics.json — scorer results from each audit (global aggregation view: includes history merged back from worktrees during the ship phase; cross-change trend analysis directly uses glob). Stable contract: this path is the sole data source for reflect's global view; metrics copies under the archive subdirectory are only for "per-change_id lookback", must not be treated as redundant and cleaned from the top-level directory — otherwise cross-change trend analysis is broken. Each metrics JSON top-level carries a change_id field (since v0.3.7); reflect can bucket by change attribution; missing or empty string is treated as "unattributed", displayed in its own bucket.harness/overrides.log — all override records (team mode; includes worktree override appends merged back during ship).harness/workflow.yaml — global workflow cursor (active_changes lists changes not yet shipped, each with phase / worktree_path / started_at).harness/changes/<change_id>/state.yaml — in-progress change business archive (design→audit phase artifacts).harness/archive/<change_id>/ — complete snapshots of shipped changes (optional traceback entry):
state.yaml — the change's design→ship final-state archivemetrics/*-metrics.json — copies of metrics produced during the changeoverrides.log — override slices produced during the changepre_design.md — design phase output (including worktree revisions)Cross-change trend analysis still uses data source 1 (top-level
metrics/), no need to traversearchive/*; archive is only for "per-change_id lookback at a single change".
[MACHINE_VERIFIED][LLM_SELF_CHECK]