Run any Skill in Manus with one click

fresh-eyes

Stars16

Forks9

UpdatedApril 21, 2026 at 20:38

Reset review context when bead polishing or code review has flatlined. Requires starting a brand-new Claude / Codex session. Use when you're seeing the same small edits round after round.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hoangsonww

hoangsonww/Forge-Agentic-Coding-CLI

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	fresh-eyes
description	Reset review context when bead polishing or code review has flatlined. Requires starting a brand-new Claude / Codex session. Use when you're seeing the same small edits round after round.

/fresh-eyes — break the local minimum

When a session has accumulated too many assumptions, fresh eyes beat tired eyes. Context exhaustion can feel like convergence.

Prerequisite

Start a new Claude Code or Codex session. Don't just /clear.

Two-step prompt

Send, in order, the two prompts at .flywheel/prompts/fresh-eyes.md:

First, a deep context load (AGENTS.md + CLAUDE.md + FLYWHEEL.md + README.md + code investigation).
Then, a review of .beads/beads.jsonl against .flywheel/plans/<PLAN>.md.

When this operator pays off most

Bead polishing flatlined after 3–4 rounds.
Deep code review keeps finding the same class of bug.
A major architectural decision feels locked in but nobody remembers justifying it.

After

If the fresh session finds new issues → back to /polish-beads. If it comes back clean → you're genuinely at convergence. Proceed.

More from this repository

same repository

deep-review

hoangsonww/Forge-Agentic-Coding-CLI

Deep review — random exploration + cross-agent review, alternating. Finds integration bugs that self-review misses. Run every 30–60 min during active implementation.

2026-04-2116

flywheel

hoangsonww/Forge-Agentic-Coding-CLI

Overview of Forge's Agentic Coding Flywheel methodology. Use to route between plan, bead, and code space. See FLYWHEEL.md at the repo root.

2026-04-2116

landing

hoangsonww/Forge-Agentic-Coding-CLI

End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

2026-04-2116

plan

hoangsonww/Forge-Agentic-Coding-CLI

Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.

2026-04-2116

plan-to-beads

hoangsonww/Forge-Agentic-Coding-CLI

Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Every bead must be executable without reopening the plan. Use after the plan has converged.

2026-04-2116

polish-beads

hoangsonww/Forge-Agentic-Coding-CLI

Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.

2026-04-2116

name	fresh-eyes
description	Reset review context when bead polishing or code review has flatlined. Requires starting a brand-new Claude / Codex session. Use when you're seeing the same small edits round after round.

/fresh-eyes — break the local minimum

When a session has accumulated too many assumptions, fresh eyes beat tired eyes. Context exhaustion can feel like convergence.

Prerequisite

Start a new Claude Code or Codex session. Don't just /clear.

Two-step prompt

Send, in order, the two prompts at .flywheel/prompts/fresh-eyes.md:

First, a deep context load (AGENTS.md + CLAUDE.md + FLYWHEEL.md + README.md + code investigation).
Then, a review of .beads/beads.jsonl against .flywheel/plans/<PLAN>.md.

When this operator pays off most

Bead polishing flatlined after 3–4 rounds.
Deep code review keeps finding the same class of bug.
A major architectural decision feels locked in but nobody remembers justifying it.

After

If the fresh session finds new issues → back to /polish-beads. If it comes back clean → you're genuinely at convergence. Proceed.