agent-workflowslisted

# Reusable Agent Workflow Patterns One-off agent sessions don't scale; workflows do. The reusable patterns are: subagents (scoped workers with briefs), hooks (event-triggered automations), slash commands (parameterized task templates), and session management (state that survives across runs). ## Overview Think of workflows as the operating system layer above individual agent sessions. Subagents let a coordinator delegate bounded work without context contamination. Hooks automate responses to events — a file changes, a check runs. Slash commands turn repeated task shapes into invokable templates with arguments. Session management — persistent notes, handoffs, resumable state — makes long work survive interruptions. Together they turn "ask the agent" into a reliable production practice. ## When to use - The same agent task recurs: research briefs, code reviews, weekly reports. - Coordinating multiple agents on one objective without tangling their contexts. - Automating routine responses: lint-on-save, test-on-commit, summarize-on-arrival. - Long projects that span many sessions and must resume cleanly. ## Core concepts - **Subagents**: child agents spawned with a scoped brief — goal, boundaries, output contract. Isolation keeps their context clean; the brief keeps their work useful. - **Hooks**: event → action mappings. File saved → run formatter; task completed → update the log. Keep hooks fast, idempotent, and observable. - **Slash commands**: named, parameteri