eforge-extendlisted

# /eforge:extend Author eforge TypeScript extensions from a natural-language request using the existing extension tooling, docs, and examples. The workflow is conversational: classify the requested behavior, scaffold with `eforge_extension`, edit the returned file with normal file tools, validate, optionally replay-test, reload, and summarize trust/security notes. ## Workflow ### Step 1: Argument intake - If `$ARGUMENTS` is missing or empty, ask what eforge behavior the user wants to add and stop until they answer. - Generate a kebab-case extension name from the request. - Ask for a name only when the generated name is ambiguous or conflicts with an existing extension. ### Step 2: Required context read Before scaffolding or editing, read these required eforge docs. Prefer the repository-local paths below when they exist; in an installed consumer project where they are not present, use the same documents from https://eforge.build/docs/extensions, https://eforge.build/docs/extensions-api, and https://github.com/eforge-build/eforge/tree/main/examples/extensions. - `docs/extensions.md` - `docs/extensions-api.md` - `examples/extensions/README.md` Then read relevant examples based on the classified capability: - `examples/extensions/minimal-event-logger.ts` for event hooks. - `examples/extensions/slack-webhook-notifier.ts` for webhook/notification hooks. - `examples/extensions/agent-context.ts` for prompt context. - `examples/extensions/agent-tools.ts` for custom agent too