Skip to content

Evolution queries absent; follow-ups lack a prev-pokemon contextΒ #32

Description

@JarbasAl

πŸ€– Auto-generated by Claude Fable 5 (claude-fable-5) via Claude Code β€” NOT human-reviewed. Verify before acting.

Findings from a five-archetype coverage review (probe + code-read against dev; battle.intent probes matched cleanly and are not at issue):

1. "what does pikachu evolve into" β€” no intent exists (handlers cover info/moves/type/battle only). PokeAPI already exposes evolution_chain; a GetPokemonEvolution Adapt intent (evolve/evolution vocab + pokemon entity) is a natural, genuinely-new addition for the homework crowd.
2. Follow-ups: "what about its moves" after an info lookup β€” nothing stores the last-discussed pokemon. Proposal: set_intent_context("prev_pokemon", name) after each successful lookup; make the pokemon requirement optional on moves/type with a context fallback.
3. Noted risk (no change proposed): battle.intent's open {pokemon_a}/{pokemon_b} slots are the loosest grammar in the default skill set β€” worth an eye during any future template edits.

Accepted changes ship with golden end2end rows including the context-fallback flow and negatives.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions