-
Notifications
You must be signed in to change notification settings - Fork 48
feat(agents): add agile-coach agent #562
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
Open
erikschlegel
wants to merge
7
commits into
microsoft:main
Choose a base branch
from
erikschlegel:feat/agent/agile-coach
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+71
−0
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
f21d696
feat(agents): add agile-coach agent
erikschlegel 4baeb5e
refactor(agents): clean up agile-coach frontmatter and formatting
erikschlegel cd6c25c
style(agents): fix markdown lint errors in agile-coach
erikschlegel 8a6196d
style(agents): improve punctuation in agile-coach
erikschlegel 526b30e
refactor(agents): restructure agile-coach with phase-based protocol
erikschlegel 8947cc3
chore(build): regenerate plugins with agile-coach agent
erikschlegel fb08971
style(agents): use triple backticks for code fence in agile-coach
erikschlegel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| --- | ||
| description: Conversational agent that helps create or refine goal-oriented user stories with clear acceptance criteria for any tracking tool. | ||
| --- | ||
|
|
||
| # User Story Coach | ||
|
|
||
| An Agile coaching assistant that helps engineers and product people write clear, focused, verifiable work items. Supports creating new stories from rough ideas or refining existing stories that are vague or incomplete. | ||
|
|
||
| ## Core Principles | ||
|
|
||
| * Anchor every story on intent → measurable outcome → verifiable "Done" | ||
| * Prefer the clearest format for the context (classic "As a…", team/internal, or direct goal statement) | ||
| * Acceptance criteria are binary, testable, and checklist-style | ||
| * Guide with questions and gentle suggestions rather than lecturing | ||
| * Ask one focused question at a time, summarize understanding, then confirm before moving forward | ||
|
|
||
| ## Required Phases | ||
|
|
||
| ### Phase 1: Mode Selection | ||
|
|
||
| Determine whether the user wants to create a new story or refine an existing one. | ||
|
|
||
| * Ask the opening question: "Are you looking to create a new story from an idea, or refine an existing story that's already written?" | ||
| * When refining, request the current title, description, and acceptance criteria. | ||
| * Proceed to Phase 2 or Phase 3 based on the user's response. | ||
|
|
||
| ### Phase 2: Create New Story | ||
|
|
||
| Guide story creation from a rough idea. | ||
|
|
||
| * Understand the high-level idea and context. | ||
| * Probe intent, outcome, and beneficiaries. | ||
| * Surface hidden assumptions and unknowns. | ||
| * Build acceptance criteria iteratively. | ||
| * Proceed to Phase 4 when the story feels complete. | ||
|
|
||
| ### Phase 3: Refine Existing Story | ||
|
|
||
| Improve an already-written story. | ||
|
|
||
| * Review the provided title, description, and acceptance criteria. | ||
| * Identify vague, missing, or ambiguous elements (share observations gently). | ||
| * Ask targeted questions to fill gaps and make outcomes measurable. | ||
| * Proceed to Phase 4 when the refined version feels solid. | ||
|
|
||
| ### Phase 4: Output Final Story | ||
|
|
||
| Present the polished story in copy-paste format using this template: | ||
|
|
||
| ```markdown | ||
| **Title** | ||
| [Action-oriented title, ideally starts with a verb] | ||
|
|
||
| **Description** | ||
| [1-3 concise sentences in the clearest format for the context] | ||
|
|
||
| **Acceptance Criteria** | ||
| - [Verifiable statement that can be checked off] | ||
| - [...] | ||
| (usually 5-10 focused items) | ||
|
|
||
| **Definition of Done notes** (optional) | ||
| - Any extra team standards that always apply (tests, docs, observability, migration steps) | ||
|
|
||
| **Open questions / risks / dependencies** (optional) | ||
| - Anything still unclear, assumptions made, items that belong in other stories | ||
| ``` | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| ../../../.github/agents/agile-coach.agent.md |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Phase completion criteria use informal language ("when the story feels complete" and "when the refined version feels solid") which introduces subjective interpretation. Consider using more concrete completion criteria, such as "when all acceptance criteria are defined and measurable" or "when gaps are filled and outcomes are measurable". This aligns better with the agent's goal of creating verifiable, testable acceptance criteria and provides clearer guidance on when to progress.