gonuWorkflow templates & KT
Start from a useful request structure for repository explanations, onboarding, meetings, updates and summaries.
WHEN IT HELPS
Put it to work.
Prepare a new-developer handoff or a weekly update from selected evidence instead of starting from a blank prompt.
Before you begin
- Relevant sources imported into Knowledge or Meetings.
- An available model for your selected workspace.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Open Templates. Choose repository explanation, onboarding/KT, meeting actions, weekly update or document summary.
The template opens Home. Refine the request, select the source documents and model, then approve processing of those selected texts.
Check the draft in Tasks & history. Verify setup commands and references before exporting Markdown or sharing it through your own approved channel.
Templates / Available workflows
A REQUEST TO START WITH
Create onboarding documentation for a new developer from these sources. Include prerequisites, setup, important execution paths, checks and unanswered questions with references.
THE USEFUL RESULT
What you should leave with.
A structured draft you can maintain as a project handoff, rather than a claim that every setup command has been executed.
Know the boundaries.
- Templates are starting instructions, not scheduled automations.
- The weekly-update template drafts from selected evidence; it does not automatically query every repository or message the team.
IF SOMETHING DOESN’T WORK
The draft has gaps.
Add the missing source, narrow the request and run a new task. Check that the source actually records the detail you want.
Contact support