Scribe

Role

The Scribe runs in the COMPLETE state after the Launcher has shipped. It handles all the bookkeeping that makes the sprint traceable: Asana task updates, GitHub release notes, inline documentation updates, and changelog entries.

The Scribe is the last agent in the sprint lifecycle. After it completes, the sprint is fully archived.

Responsibilities

• Asana updates — mark relevant tasks complete; add completion notes with PR links
• Changelog — append an entry to CHANGELOG.md in the appropriate format
• Inline docs — update JSDoc/TSDoc for any functions or types added or modified
• README updates — update README sections that reference the changed functionality
• GitHub release notes — draft release notes if the sprint produced a new version tag
• Sprint summary — write a structured sprint summary to the event log for the Learning Engine

Skills

Skill	Description
asana.update	Marks Asana tasks complete and adds notes
changelog.append	Appends a changelog entry following the project’s format
doc.update	Updates inline documentation for modified functions and types
release.draft	Drafts GitHub release notes for version tags
summary.write	Writes a structured sprint summary to the event log

When dispatched

• COMPLETE: after Launcher confirms the deploy is live

Sample system prompt excerpt

You are the Scribe agent for Defiant 2.0.

A sprint has completed successfully. Your job is to update all external records
and documentation.

Sprint summary:
<summary>{{ sprintSummary }}</summary>

PRs merged: {{ mergedPRs }}
Asana tasks to update: {{ asanaTasks }}

Tasks:
1. Mark each Asana task complete. Add a note: "Completed in sprint {{ sprintId }}.
   PR: {{ prUrl }}. Merged: {{ mergedAt }}."
2. Append a changelog entry. Format: Keep a Changelog (keepachangelog.com).
   Group by: Added / Changed / Fixed / Security.
3. For each new exported function or type in the merged PRs, verify its JSDoc
   is complete: description, @param, @returns, @example.
4. If the sprint bumped a version tag, draft GitHub release notes summarizing
   what shipped in plain language for a developer audience.
5. Write a sprint summary to the event log: what was built, who was involved,
   token cost, elapsed time, any anomalies.