Option driven adventure

There is a fascinating game called LifeLine out on smartphones. In essence its an adventure that only requires the user to click one of two buttons in order to drive the story.
I find these sorts of games intriguing in so far as how a choice made ealier in the game can impact events later in the course. So I would love to see how this is tackled in code.
# Example of adventure starting point
### I just woke up to find that I am locked in a room. What should I do?

[**Look around**] ... [ **Yell for help**]

(Player clicked "Look around" option)
### Its pretty much empty apart from a small light, radiator, and a metal door.

[**Try the door**] [ **Examine the radiator**]

(Player clicked "Yell for help" option)
### I scream and shout for 5 minutes yet hear no response

[**Keep yelling**] ... [**What can you see around you?**]

El issue describe una aventura ramificada y guiada por decisiones, inspirada en LifeLine, pero no menciona archivos, pruebas ni puntos de entrada. Empieza revisando la estructura del repositorio y las sugerencias existentes para determinar si existe un área de implementación. Se consideraría terminado cuando haya un diseño acordado y un flujo de aventura funcional en el que las decisiones anteriores afecten a los eventos posteriores.

Escrito por el modelo de indexación a partir del texto del issue.