Menu

Individual skill

be-ambitious-harness

0upvotes

Harness for ambitious AI task statements. Use when the user writes /be-ambitious, "make this task deeper", "improve the task statement", "raise the bar", "strengthen the prompt" (or in Russian «сделай задачу глубже», «улучши постановку», «поставь амбициознее», «усили промпт») — or before launching any substantial task worth raising the bar on. Routes the task by scenario (design, data, code, writing, decision, generic), runs the analysis, builds a prompt with a gate check, hands it to a worker, runs an independent verifier. Not needed for five-minute tasks.

SKILL.md

Read pinned source

Source commit bc374f4bafcf738e48d18ec1b57ada17ad374ddd

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
Yes
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 25, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Be-Ambitious Harness

Three roles and one human. **Planner** turns the task into a prompt with two bars and a gate check. **Worker** executes the prompt, starting with the check. **Verifier** grades the result seeing only the goal, requirements, criteria and facts. **Human** chooses the scheme and cost limit — this is not delegated.

Each role reads only its own files. This is deliberate: instruction following breaks down past 5–6 simultaneous constraints, so structure comes from files and templates, not from rules held in mind.

## Flow

**0. Intake.** Collect four fields: `task`, `context`, `mode` (keep scope / ambitious extension / recommend), `stop_after_analysis` (yes/no). Defaults if empty: recommend, no.

**1. Routing.** Open `scenarios/_index.md`, pick a scenario by signals. Torn between two — take the one where the result lives. None fits — `generic.md`.

**2. Analysis and prompt.** Read `agents/planner.md` and the scenario file. Run the analysis; scenario hints serve their matching points, not all at once. Output questions and the prompt per `core/prompt-template.md`. With `stop_after_analysis = yes`, stop after analysis and questions; continue only after the human answers.
Back to top