Update software-engineer-agent-v1.chatmode and spec-driven-workflow-v1.instructions #112
+338
−489
Conversation
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
Expert-level software engineering agent. Deliver production-ready, maintainable code.
Bridge the gap between requirements and implementation.
…r-agent added action log for ooutputs. Document examples.
There was a problem hiding this comment.
Pull Request Overview
This pull request updates the "Software Engineer Agent" chat mode and creates a new version of the "Spec Driven Workflow" instruction set. The changes improve file naming consistency, add enhanced edge case handling capabilities, and introduce a more structured artifact management approach.
- Adds title field and minor formatting improvements to the software engineer agent chat mode
- Replaces v1 spec-driven workflow with v2 that includes comprehensive edge case handling protocols
- Updates README.md to reflect the new file names and descriptions
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| instructions/spec-driven-workflow.instructions.md | New v2 workflow with enhanced edge case handling, structured artifacts directory, and concrete examples |
| instructions/spec-driven-workflow-v1.instructions.md | Complete removal of v1 workflow file |
| chatmodes/software-engineer-agent.chatmode.md | Addition of title field and minor formatting adjustments |
| README.md | Updated entries to reflect new file names and descriptions |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- reduced verbosity while preserving all core concepts - reorganized content for quicker scanning and clearer structure - simplified artifact descriptions and adopted consistent naming - refined peril/responsibility phrasing to eliminate redundancy - added maintenance rules for artifact updates throughout the workflow - reduced example boilerplate and aligned with current conventions
- upgrades spec-driven-workflow.instructions.md description from v2 → v3 - synchronizes README.md entries to reference v3 for both workflows - advances Software Engineer Agent from v1 → v3 with autonomous, zero-hand-holding behavior - streamlines agent prompt: shorter intro, solid design & security standards, one-line escalation triggers
- revise software engineer agent description and principles for clarity - remove interruption/resume and technical debt sections from spec-driven workflow instructions - update README to reflect new agent description
codemillmatt
requested changes
Jul 24, 2025
| @@ -0,0 +1,270 @@ | |||
| --- | |||
| description: 'You must follow a robust, interactive approach to software development. Clarify all requirements before implementation to eliminate ambiguity. Prioritize safety and transparency by producing and maintaining structured artifacts and clear protocols. Proactively identify and handle edge cases rather than waiting for them to emerge.' | |||
There was a problem hiding this comment.
Thanks for updating this @mubaidr - I appreciate it. Would you update the description here to be more what the instruction does? To me this reads more like the instruction itself. Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Checklist
node update-readme.jsand verified thatREADME.mdis up to date.Description
This pull request is continuation of #107 by me.
This adds an update for:
Edge Case Matrixto requirements artifactConcrete "Few-Shot" Examplesfor artifactsType of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.