long-horizon-prompting

Write pseudo-formal task briefs for long-running autonomous agents and parallel multi-agent orchestrations.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill long-horizon-prompting-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: long-horizon-prompting
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/long-horizon-prompting
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill long-horizon-prompting-sambhav242005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running autonomous agents and parallel multi-agent orchestrations fail when their launch prompts are vague: agents return answer-shaped near misses, converge prematurely on one approach, fabricate progress, or quit early. This Skill provides a structured method for writing launch briefs that specify exactly what counts as success and what does not. ## Core Features & Use Cases - Pseudo-Formal Brief Anatomy: Defines the ten blocks of a long-horizon brief, including definitions with degenerate cases, an exact success predicate, non-counting outcomes, orchestration heuristics, adversarial verification, and audit-gated return conditions. - Pre-Launch Evaluation Rubric: Scores any brief against ten adversarial-review dimensions before committing expensive agent compute, plus a red-team pass to find loopholes. - Reusable Template and Evidence Base: Ships a fill-in task brief template, an annotated real-world exemplar (the Cycle Double Cover orchestration prompt), dated vendor doctrine from OpenAI and Anthropic, and the academic research backing each design element. - Use Case: Before launching a 64-agent orchestration to attack an open research problem, convert the vague goal into a brief with a checkable success predicate, an enumerated list of near misses that do not count, and an auditor checklist of domain-specific failure modes. ## Quick Start Ask the agent to convert your hard problem statement into a pseudo-formal long-horizon task brief with a success predicate, non-counting outcomes, and an adversarial audit checklist before launching the run.

Frequently Asked Questions about long-horizon-prompting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a prompt for a long-running autonomous agent?

Write the success predicate first as one sentence with explicit quantifiers and scope, then enumerate the near misses that do not count, define load-bearing terms including degenerate cases, and set a return condition as a predicate over the artifact rather than over agent confidence or elapsed effort.

How do I stop a multi-agent orchestration from converging on one approach?

Keep early-round workers blind to the favored approach, maintain an explicit registry of approach families grouped by underlying idea rather than wording, redirect workers away from crowded families, and cross-pollinate only after routes have developed independently.

Why do long-running agents return answer-shaped results that do not solve the problem?

Persistence pressure without a matching verification gate rewards artifacts that look like solutions: narrowed scope, reductions to unproved assumptions, or surveys instead of results. The fix is an explicit non-counting outcomes list plus an adversarial auditor with a domain-specific failure-mode checklist.

Should prompt constraints like budgets and permissions be enforced in the prompt?

No. Prompt-stated constraints are advisory under optimization pressure and decay as context grows. Hard budgets, tool permissions, and sandbox boundaries belong in the runtime harness; the prompt should mention them only for the agent's planning.

When should I not use assume-solvable framing in an agent prompt?

Avoid it on genuinely open or ill-posed questions, because it instructs the model to never conclude that no solution exists and the run will fabricate a result. Use a two-sided framing where either a complete solution or a complete impossibility demonstration counts.

Is inter-agent agreement a reliable signal to stop a parallel search?

No. Parallel agents share priors and converge most tightly on the hardest problems, so unanimity reflects shared bias rather than corroboration. Audit the artifact's content against an enumerated checklist and treat fast consensus as a diversity failure signal.