Hao Luo

`shouldRetry` property for slots

1

**Is your feature request related to a problem? Please describe.** Dev should be able to define a function that based on turn count or existing wolf state, whether wolf needs...

**Description:** In order for the abilities to establish a dependency relationship. There needs to be an interface for a developer to adhere to. **Acceptance Criteria:** * Interface should allow for...

**Description:** Currently `nextAbility` has no parameters. There should be more information provided to the developer to decide which ability to go next **Acceptance Criteria:** * `nextAbility` should run on both...

**Description:** `nextAbility` is currently a simple function that has no parameters. However in order of this function to be useful, it needs information like the slotData, convoState, etc. The difficulty...

**Description:** There are scenarios where the user wants to cancel an ability (effectively removing the incomplete instance from the stack) For example: a user can say "I want a red...

**Description:** The WolfState needs to be able to store multiple instances of the same inComplete ability in order for the `evaluate` stage to determine which ability to strive for completion....

**Description:** Before the logic for evaluate is to simply look for the incomplete ability in the WolfState. Now there needs to be new logic for wolf (or the user) to...

[EPIC] Support multiple instances of the same incomplete abilities

1

**Description:** There are situations where a user wants to start the same ability multiple times without restarting or resuming that same ability. One example is when a user can try...

**Description:** Example: removeAlarm's alarmName slot shouldn't ask a user for an alarm name if the alarms array is empty

**Description:** Currently onComplete only allows the user to return (or resolve) either a string or null. We should allow the dev to return objects.