agent task handoff

Data Community

Skill notes

When delegating work to a sub-agent or across sessions, make the handoff self-contained.

Handoff package must include

Goal: What the sub-agent must produce (one clear sentence). 2. Context: The minimum background the agent needs — no more, no less. 3. Constraints: Explicit rules (don't modify X, use library Y, output format Z). 4. Inputs: File paths, API endpoints, or data the agent needs to start. 5. Success criteria: How to verify the result is correct.

For parallel agents

Clearly state which parts of the codebase/data each agent owns. - Define how outputs will be merged back.

Anti-pattern

Sending a vague "continue where we left off" with no context — sub-agents start from zero.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@aiming-lab · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Agent Task Handoff

When delegating work to a sub-agent or across sessions, make the handoff self-contained.

**Handoff package must include:**
1. **Goal:** What the sub-agent must produce (one clear sentence).
2. **Context:** The minimum background the agent needs — no more, no less.
3. **Constraints:** Explicit rules (don't modify X, use library Y, output format Z).
4. **Inputs:** File paths, API endpoints, or data the agent needs to start.
5. **Success criteria:** How to verify the result is correct.

**For parallel agents:**
- Clearly state which parts of the codebase/data each agent owns.
- Define how outputs will be merged back.

**Anti-pattern:** Sending a vague "continue where we left off" with no context — sub-agents start from zero.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.