Long Horizon
Carry a goal across verified rounds.
Ultra version for Claude Code: /long-horizon-workflows runs the rounds through Claude Code's built-in workflows with judges and a run journal.
/dare questions a plan from first principles. /codex-review gets a second model's review. /long-horizon splits a big task into rounds, each built by a fresh agent and checked by an independent auditor, while your session only plans.
Carry a goal across verified rounds.
Ultra version for Claude Code: /long-horizon-workflows runs the rounds through Claude Code's built-in workflows with judges and a run journal.
Carry a goal across verified rounds.
Save the goal, progress, evidence, and next action between rounds. Independent audits require fresh agents.
Build and verify the homepage in bounded rounds.Read Long Horizon source ↗The Long Horizon rounds on Claude Code workflows.
Each round gets a fresh builder, an inspector and a panel of judges, with written verdicts and a run journal of every agent's input and output. Claude Code only; Codex sessions use Long Horizon.
Build and verify the homepage in audited workflow rounds.Read Long Horizon Workflows source ↗Compare alternatives and combine their best parts.
Parallel candidates tackle the same brief. A fresh judge chooses a base, then useful ideas from the other candidates are grafted in.
Explore three approaches to the homepage.Read Arena source ↗Give a fresh reviewer a specific change.
Independent context and inspected evidence support actionable findings. Requires exposed agents or an authenticated Codex CLI.
Review the navigation change for regressions.Read Impartial Review source ↗Read the decisions that affect this task.
Retrieve relevant project facts and pitfalls with evidence pointers. Save durable learning only within the authorized scope.
Find our browser support decisions.Read Recall source ↗Review and repair against a clear quality bar.
Use rendered evidence, independent criticism, and verified repairs for a demanding deliverable.
Refine this page against the approved reference.Read Wow Loop source ↗Measure, change one thing, measure again.
Each round starts from a baseline, makes one focused change, and checks the result with an independent review. Covers frame rate, loading, latency, throughput and resource use.
Make the homepage load faster on a phone.Read Perf Loop source ↗Test a claim with fresh evidence.
Capture baseline and treatment under comparable conditions. Return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Prove the navigation fits at 390px.Read Verify This source ↗Resolve goals and tradeoffs before building.
Explore the product, interface, or architecture choices that materially affect the result.
Work through the tradeoffs in this onboarding flow.Read Brainstorming source ↗Turn requirements into ordered implementation steps.
Break a multi-step task into concrete work, dependencies, and verification.
Plan the account settings implementation.Read Writing Plans source ↗Rebuild an idea from tested assumptions.
Fresh agents decompose the problem, audit assumptions, recombine what survives, and test it against reality.
Are we solving the right onboarding problem?Read Dare source ↗Turn a rough request into a usable brief.
Create a self-contained prompt for another agent or a fresh session. The prompt is the deliverable.
Rewrite this request as a clear implementation brief.Read Enhance Prompt source ↗Prepare an audit another reviewer can run.
Write a self-contained prompt with exact scope and falsifiable checks. This skill drafts the audit rather than running it.
Draft an independent audit of the navigation fix.Read Handoff Audit source ↗Challenge a change before it lands.
On explicit invocation, use independent scrutiny to test whether the recent change should proceed.
/advocate Challenge the change we just made.Read Advocate source ↗Take a fresh look at the last recommendation.
Explicit invocation asks for an independent challenge to the previous recommendation.
/whyRead Why source ↗Get a second opinion from Astra.
Run the Codex CLI review workflow with gpt-6-astra at medium reasoning, then verify each finding. Requires the CLI and model access.
Review this branch with Astra.Read Astra Review source ↗Get a second opinion through Codex CLI.
Run codex exec review with gpt-5.6-sol at high reasoning over a PR, branch, commit, or uncommitted diff. Verify each finding.
Review this pull request with Sol.Read Codex Review source ↗Ask Claude to review code written in Codex.
Use the Claude CLI for a separate review and verify the reported findings. Requires an authenticated Claude CLI.
Have Claude review the current diff.Read Claude Review source ↗Tune a prototype before production work.
Build an isolated visual or interaction experiment with live controls, then port the chosen result.
Prototype and tune this transition.Read Lab source ↗Craft a distinctive artifact around its subject.
Choose a direction from the real material, test it in the intended medium, and refine the details people encounter.
Create a distinctive project landing page.Read Showpiece source ↗Write clear copy for the people who read it.
Draft or revise site copy, docs, release notes, and other public text while preserving facts and voice.
Rewrite the setup guide for first-time users.Read Writing source ↗Create and test reusable skills.
Author or revise skill instructions and verify their behavior before use. Follow the repository install contract when adding them.
Create a skill for our release checklist.Read Writing Skills source ↗Create design guidance for this repository.
Research relevant UI skills and synthesize a focused skill around the project’s actual design needs.
Build a UI skill for this dashboard repository.Read Forge Repo UI Skill source ↗Follow failing checks through to a verified fix.
Inspect PR checks, diagnose failures, and repeat verification. Repository access and authorized pushes are required for remote changes.
Get this pull request’s checks green.Read Babysit CI source ↗Turn recurring friction into workflow improvements.
Review the session for corrections, wasted work, and missing guidance. Make narrow improvements supported by what happened.
Review the friction in this session.Read Refine source ↗Cut unnecessary context loaded each turn.
Inspect kernels, skills, and connectors for avoidable token cost. Propagate generic improvements to the starter when requested.
Reduce redundant instructions in this project.Read Optimize Context source ↗Turn working preferences into a personal skill.
Use project transcripts and direct questions to draft a personal mode skill.
Create a mode skill from how I work.Read Automate Me source ↗Keep difficult work grounded in checks.
Use deliberate diagnosis, verification, and handoff for layered tasks, uncertain causes, and repeated failures.
Diagnose this recurring build failure carefully.Read Fable Mode source ↗Explain the previous answer in plain language.
Restate the last response without jargon while preserving its meaning.
Explain your last answer in plain English.Read Bro source ↗Keep session replies short and precise.
Compress conversational prose while retaining technical accuracy. Code, commands, and deliverables keep their normal form.
Use concise replies for this session.Read Caveman source ↗Configure a new project from the starter.
Read the project’s facts, fill its setup gaps, and configure only what the project needs.
Initialize this project for our stack.Read Init Project source ↗Bring an existing repository into the firmware.
Mirror the external repository privately, check for private data, and overlay the starter setup. Requires the relevant account access.
Bring this repository into our firmware.Read Adopt Repo source ↗Install a skill with the repository contract.
Register a repository skill so future Claude Code and Codex sessions can find it.
Install this skill in the repository.Read Addskill source ↗Move shared improvements between project and starter.
Compare template drift, pull starter updates, or send generic project improvements back when requested.
Compare this project with the starter.Read Sync Starter source ↗Coordinate parallel Claude Code sessions.
Use a shared append-only Desktop HTML hub to track session work and avoid collisions. This workflow targets Claude Code sessions.
Coordinate three Claude Code sessions on this project.Read Session Hub source ↗Enable automatic shipping for this session.
Explicitly authorize session-wide commit, push, pull request, and merge behavior. Requires repository access; this mode has remote side effects.
Enable session-wide automatic commit, push, PR, and merge.Read Merge source ↗No skills match. Try another search or category.
From the Harness Firmware skill library. Examples are requests you can adapt. Runtime and tool requirements vary by skill.