agy-staffer

1<!-- Generated from skills/staffer/SKILL.md; run npm run generate:opencode. Do not edit here. -->
2 
3# agy staffer
4 
5The general-purpose persona: a clean entry point for tasks that none of the specialists fit. Its prompt template is deliberately minimal — the task text, the environment (cwd, branch, date), the shared working rules, and the safety guardrails, nothing else. No role framing or fixed body format: the task defines its own deliverable, and no domain-specific template context can pull the run off course.
6 
7Prefer a specialist when one fits: `researcher` for surveys and deep dives, `reviewer` for second opinions on code or plans, `implementer` for edits to the working tree, `ask` for a cheap one-shot question.
8 
9staffer is also the route to agy-native tools no specialist covers — notably **image generation**: agy ships a `generate_image` tool (verified on v1.1.15; a 1024×1024 PNG in ~30s). Name the output path in the task, e.g. `staffer --prompt "generate a pixel-art robot mascot, save it as assets/mascot.png"`.
10 
11<!-- BEGIN SHARED PERSONA RULES -->
12<!-- Generated from templates/persona-skill-rules.md; run npm run generate:skills. Do not edit this block. -->
13## Dispatch
14 
15- Continue a completed job with `continue --job <id> --prompt "..."` when the task and persona are the same and prior context helps, even if the user does not say "continue". Keep each job ID with its assignment; if the target is unclear, check known jobs before asking the user.
16…