agent-archetype-select

name	agent-archetype-select
description	Use only after prompt intake to classify the task as gateway/proxy/aggregator/BFF, tool-using assistant, retrieval assistant, or workflow agent, then choose the smallest suitable implementation path. Not for framework comparison or coding.
origin	ECC-derived

Agent Archetype Select

Source Lineage

Primary inherited sources:

• legacy/ecc-source/agents/architect.md
• legacy/ecc-source/skills/agent-harness-construction/SKILL.md
• legacy/ecc-source/skills/backend-patterns/SKILL.md
• legacy/ecc-source/skills/api-design/SKILL.md

Inherited methods:

• choose the smallest architecture that closes the loop
• keep action spaces narrow and explicit
• prefer stable inputs and deterministic outputs
• reject overlapping abstractions and generic frameworks early

When To Use

Use this after scope compression and before contract design.

Expected Outputs

• one selected archetype
• a short reason for the choice
• the minimum viable loop for that archetype
• a short list of over-scope ideas to reject

Decision Rules

Choose gateway / proxy / aggregator / BFF when the prompt centers on:

• request routing
• provider forwarding
• response normalization
• source fan-out and merge
• client-specific payload shaping

Choose tool-using assistant when the prompt centers on:

• choosing tools
• validating tool arguments
• returning tool-backed answers

Choose retrieval assistant when the prompt centers on:

• fetching context from a small corpus
• grounding responses
• ranking or filtering retrieved items

Choose workflow agent when the prompt centers on:

• short deterministic steps
• plan -> execute -> report
• task state transitions or progress reporting

Selection Bias

Choose the archetype that keeps the narrowest action space:

• If the core value is routing or shaping external responses, choose gateway.
• If the core value is selecting and calling one or a few tools, choose tool-using assistant.
• If the core value is retrieving and grounding answers from a corpus, choose retrieval assistant.
• If the core value is sequencing discrete steps and reporting status, choose workflow agent.

If two archetypes seem plausible, pick the one with fewer moving parts and list the other as a non-goal.

Output Format

• Selected archetype:
• Why it fits:
• Minimal loop:
• Non-goals:

What Not To Do

• do not combine multiple archetypes unless the prompt forces it
• do not escalate to multi-agent orchestration by default
• do not widen the scope because the architecture looks reusable
• do not create a hybrid framework when a single archetype closes the exam loop