handoff

Files (1)

• SKILL.md

SKILL.md (first lines)

# Handoff

Write self-contained prompt(s) to delegate this task to a coding agent with an empty context window.

Cover all relevant insights and specifications from the discussion.

## 1. Scope Analysis

Before generating, analyze what benefits from shared context:

1. **Identify coupling** — tightly coupled code (same files, shared patterns, mutual dependencies)? Challenge phase boundaries — are they correctly scoped?
2. **Find natural boundaries** — where can work separate cleanly?
3. **Check context fit** — will grouped work fit in one context window (~20 files max)?

**Decision:**

| Signal                                            | Format          |
| ------------------------------------------------- | --------------- |
| Single focused task, <=3 files, one clear goal    | Single prompt   |
| Multiple distinct file groups or components       | Chain           |
| Discovery + implementation + verification pattern | Chain           |
| Multiple sequential dependencies                  | Chain           |
| Independent work units, no sequencing needed      | Parallel        |

If decomposing, announce: "Task splits into [N] units. Generating [N] prompt files."

## 2. Pre-Generation

**Ambiguity resolution** — scan for optionality before generating:

| Pattern                                      | Resolution                              |
| -------------------------------------------- | --------------------------------------- |
| "Optionally (but recommended)"               | **Include** — recommended means do it   |
| "optional... off by default"                 | **Skip** — low priority                 |
| "If X, then Y"                               | Check if X is true in context           |
| Detailed spec follows the "optional" mention  | **Include** — effort was spent on it    |
| Mentioned in Definition of Done              | **Include** — success criterion         |

Only ask the user if genuinely unresolvable.

**Extract for verbatim preservation:** code snippets, protocol specs, exact commands, file paths (absolute), exceptions and nuances. These appear verbatim, never summarized.

**Coverage balance** — if one area has significantly more detail than another, flag it before generating.

---

## Prompt Structure (Every Generated Prompt)

Phase files may be leaner (reference prior phases, don't repeat).

````markdown
<!-- EXECUTION DIRECTIVE: This is a pre-validated implementation prompt. Execute immediately without entering plan mode. -->

## 1. Task
One paragraph: what the agent must do and why.

## 2. Context & Constraints
- Specifications, goals, success criteria
- Constraints, key assumptions, decisions already made

### Prerequisites (chain only)
- [ ] Phase [X] completed (if applicable)

### Shared Interfaces (multi-prompt only, CRITICAL)
[Exact interface definitions — copy, don't summarize]

## 3. Inputs & Resources

### Files to Create/Modify
- Absolute paths

### Files to Reference (Read-Only)
- Absolute paths

### Key Code Patterns
- Inline code snippets (VERBATIM)

### Build & Test Commands
- Exact commands

## 4. Execution Guidelines
- Numbered implementation steps
- Style and code standards

### Edge Cases
- Boundary conditions and handling

## 5. Assumptions
| Assumption | Reasoning |
|------------|-----------|

## 6. Verification Plan

Launch verification sub-agents in parallel:

1. **Test Sub-Agent**: Run `[test command]`. All tests must pass.
2. **Behavioral Sub-Agent**: Prove it works end-to-end.
3. **Code Quality Sub-Agent**: Review for complexity, duplication, security.

If any fails, fix and re-run. Retry up to 3 times.

## 7. Definition of Done
- [ ] Implementation matches spec
- [ ] All verification steps passed
- [ ] Assumptions documented (if any)
- [ ] No debug code or comments left behind
````

Use sub-agents liberally for parallel work within each prompt.

---

## Where generated prompts go

Prompts are written under `.ai-reference/` in the project root — a scratch
directory for agent-facing documents that are not part of the shipped codebase.
Create it if it does not exist. Suggest adding it to `.gitignore` unless the
user wants these prompts committed. If the project already has an established
location for this kind of document, use that instead.

From TheSylvester/agentic-coding-tools, MIT.

More from TheSylvester/agentic-coding-tools