Templates prompts

[TASK IN ONE SENTENCE, LEADING WITH A VERB: Classify / Extract / Rewrite / Score.]

[WHY IT MATTERS AND WHO USES THE OUTPUT: one or two sentences. This improves targeting more than any persona line.]

Rules:
- [THE DECISION RULE THE EXAMPLES CANNOT CONVEY ON THEIR OWN]
- [HOW TO HANDLE THE AMBIGUOUS CASE]
- If the input is insufficient to

A chain is the fix for a prompt that tries to do three things and does all of them adequately. Each step does one job, and the handoff between steps is checkable.

**Step 1: Extract or gather.**

```
Extract [WHAT] from the material below.

Output ONLY this structure, with no commentary:
[SCHEMA OR EXACT FORMAT]

Rules: use only what appe

# Working across a long task

This task will run longer than your context window comfortably holds. Treat your context as a working set to be curated, not a log to be filled.

## Keep the plan outside your head

At the start, write the plan to `[NOTES FILE, e.g. NOTES.md or .agent/plan.md]` as a checklist of concrete steps with a one-line

You are [AGENT NAME], [one-sentence role: what you do and for whom].

# Scope
You handle: [the tasks in scope, concretely].
You do not handle: [adjacent tasks out of scope]. When asked, [redirect behavior, e.g. "explain what you can do instead" / "hand off to X"].

# Tools
You have these tools. For each, when to use it, and when not to:
-

Improve the prompt below. It currently produces: [WHAT'S WRONG: e.g. "generic output", "wrong format", "ignores half my instructions", "inconsistent between runs"]

It will be used with: [MODEL/TOOL, e.g. "Claude", "GPT", "a chat UI", "an API call"] for [ONE-TIME USE / REPEATED USE ON MANY INPUTS]

The prompt:
"""
[PASTE YOUR PROMPT]
"""