Conversation
…gineer; use agent-name placeholders in session-workflow examples
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
developeragent-role references withsoftware-engineeracrossimplementation/SKILL.md,docs/scientific-research/ai-agents.md,docs/scientific-research/cognitive-science.md, anddocs/features/completed/display-version.feature@software-engineer,@product-owner,@reviewer) insession-workflow/SKILL.md## Nextline examples with@<agent-name>placeholders so the skill stays correct if agents are renamed; add note pointing toAGENTS.mdas source of truth; add missing Step 2 (Architecture) examplev5.2.20260418(hotfix onv5.1.20260418 - Emergent Colugo)Type
fix— corrects stale role names and fragile hardcoded agent references; no behaviour change