approach-evaluationlisted

# Approach Evaluation ## Purpose / When to Activate Activate when the invoking agent identifies a technical or architectural decision point where: - Multiple viable implementation approaches exist and the best choice is non-obvious - A technology, library, or service is being introduced for the first time in the project - No established convention exists in `conventions.md` for the problem domain - The problem touches a domain with well-known industry standards that should be considered - A prior approach failed or showed limitations (post-mortem driven re-evaluation) Do NOT activate when: - A convention already exists in `conventions.md` for this exact problem - The approach is explicitly defined in the Story or a prior decision - The Story is Tier 1 / MicroDelivery with obvious implementation - The evaluation would delay delivery without reducing meaningful uncertainty **This skill researches and compares — it does not decide.** The invoking agent (Planning Sub-Agent or Discovery Agent) reads the output and makes the decision. --- ## Process ### Phase 1 — Problem Framing 1. State the problem precisely: what capability is needed, what constraints apply 2. Read `contexts/memory/index.md`. Resolve and load: - The `project` category file → extract tech stack, architectural boundaries, known constraints - The `patterns` category file → extract established patterns and conventions - The `decisions` category file → extract prior decisions on related topics Do n