メニュー
The feature-wide final audit. Re-runs the five lenses across ALL groups together, then two extra passes — Dreamland (dream perfection, then make it real) and Simulation (realistic scale testing). Runs after every group is accepted.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.
| name | Final — The F-Pass |
| description | The feature-wide final audit. Re-runs the five lenses across ALL groups together, then two extra passes — Dreamland (dream perfection, then make it real) and Simulation (realistic scale testing). Runs after every group is accepted. |
| argument-hint | [feature-name] [--stage f1..f7] |
After all groups are accepted, the feature gets one final, feature-wide audit pass. The per-group audits caught drift within a group; the F-pass catches what only shows up when the whole feature is viewed at once — cross-group inconsistency, integration gaps, and quality that no single group owned.
Gate: every group must be accepted in approvals/master.json before the F-pass begins. This is the mandatory next step after the last group-accept — never skip straight to closure.
The F-pass is seven stages, run in order. The same Double Gate physics apply: the deeper stages cannot begin until the consistency stage (F1) is clean.
| Stage | Lens | Scope |
|---|---|---|
| F1 | Design + master-spec consistency (A1, feature-wide) | all groups |
| F2 | Spec review — FR/AC compliance (A2, feature-wide) | every FR/AC in the spec |
| F3 | Polish (A3, feature-wide) | all code/content |
| F4 | North Star direction (A4, feature-wide) | the whole feature vs the vision |
| F5 | Web audit (A5, feature-wide) | the whole stack |
| F6 | Dreamland | dream perfection, then make it real |
| F7 | Simulation | realistic scale testing |
Run each lens exactly as its per-group skill defines it (/genesis-a1…/genesis-a5), but scoped to the entire feature rather than one group. Findings, reports, the zero-tolerance loop, and conviction are identical — see docs/the-audit-system.md. Reports go to audits/final-f{N}.md. F3 cannot start until F1 is at zero findings.
Step back from what was built and describe the feature at its dream-perfect best — not constrained by what exists, not by the spec, just: what would make this genuinely excellent? Then take each dream and ask whether it can be made real now. Every realizable dream becomes a finding (fix now) or a tracked design input. Dreamland is where the kit reaches past "meets the spec" toward "is actually great." Record the report to audits/final-f6.md.
Run the feature against realistic scale and stress. Load the group simulation scenarios (simulations/g{N}-scenarios.md) and exercise the feature as a whole: realistic data volumes, concurrent use, mid-stream entry, failure and recovery, the unhappy paths. Each scenario is PASS (the feature handles it) or GAP (it doesn't); every gap becomes a finding. Record the report to audits/final-f7.md.
When all seven stages are clean, run the feature review, then /genesis-accept (the review phase), then /genesis-closure to open the PR to main.
- "run the final audits"
- "f-pass"
- "final feature audit"
- "dreamland" / "simulation"