Repository navigation
feat: resilient multi-channel messaging #641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -51,7 +51,13 @@ After the implementation works: | |||||
| Run the validation command from the wish. Record output. Confirm each acceptance criterion is met. | ||||||
|
|
||||||
| ## 7. Report Completion | ||||||
| After completing all deliverables and validation, call `genie done <slug>#<group>` to report completion. The slug and group are in your initial prompt. This signals the orchestrator that your work is finished so it can advance to the next wave. | ||||||
| After completing all deliverables and validation: | ||||||
| 1. Run validation commands from the wish | ||||||
| 2. Commit and push your work | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Making Useful? React with 👍 / 👎. |
||||||
| 3. Call: `genie done <slug>#<group>` — marks the group complete in state (source of truth) | ||||||
| 4. Call: `genie send 'Group <N> complete. <summary>' --to team-lead` — sends durable notification | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For consistency and to reduce ambiguity for the agent, it would be better to use
Suggested change
|
||||||
|
|
||||||
| The slug and group are in your initial prompt. Both commands are mandatory — state is how the orchestrator tracks progress, the message is how team-lead gets notified. | ||||||
| </process> | ||||||
|
|
||||||
| <success_criteria> | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency and to reduce ambiguity for the agent, it would be better to use
<group>here instead of<N>. Thegenie donecommand on the preceding line uses<group>, and the correspondinginitialPromptindispatch.tsis constructed with the actual group number. Using<group>makes it explicit which value should be substituted.