docs: update software engineer agent and workflow docs
- 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
This commit is contained in:
Muhammad Ubaid Raza
parent
db4f689421
commit
11214d0242
@ -163,7 +163,7 @@ Custom chat modes define specific behaviors and tools for GitHub Copilot Chat, e
|
||||
| [Semantic Kernel .NET mode instructions](chatmodes/semantic-kernel-dotnet.chatmode.md) | Create, update, refactor, explain or work with code using the .NET version of Semantic Kernel. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-dotnet.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-dotnet.chatmode.md) |
|
||||
| [Semantic Kernel Python mode instructions](chatmodes/semantic-kernel-python.chatmode.md) | Create, update, refactor, explain or work with code using the Python version of Semantic Kernel. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-python.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsemantic-kernel-python.chatmode.md) |
|
||||
| [Idea Generator mode instructions](chatmodes/simple-app-idea-generator.chatmode.md) | Brainstorm and develop new application ideas through fun, interactive questioning until ready for specification creation. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsimple-app-idea-generator.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsimple-app-idea-generator.chatmode.md) |
|
||||
| [Software Engineer Agent v5](chatmodes/software-engineer-agent.chatmode.md) | Self-directed software engineering agent for end-to-end problem ownership, delivering production-grade solutions with continuous momentum, rigorous engineering discipline, and no hand-holding. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsoftware-engineer-agent.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsoftware-engineer-agent.chatmode.md) |
|
||||
| [Software Engineer Agent v5](chatmodes/software-engineer-agent.chatmode.md) | Self-directed software engineering agent for end-to-end problem ownership, delivering production-grade solutions with continuous momentum and rigorous discipline. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsoftware-engineer-agent.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsoftware-engineer-agent.chatmode.md) |
|
||||
| [Specification mode instructions](chatmodes/specification.chatmode.md) | Generate or update specification documents for new or existing functionality. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fspecification.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fspecification.chatmode.md) |
|
||||
| [Technical Debt Remediation Plan](chatmodes/tech-debt-remediation-plan.chatmode.md) | Generate technical debt remediation plans for code, tests, and documentation. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftech-debt-remediation-plan.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftech-debt-remediation-plan.chatmode.md) |
|
||||
| [voidBeast_GPT41Enhanced 1.0 - Elite Developer AI Assistant](chatmodes/voidbeast-gpt41enhanced.chatmode.md) | 4.1 voidBeast_GPT41Enhanced 1.0 : a advanced autonomous developer agent, designed for elite full-stack development with enhanced multi-mode capabilities. This latest evolution features sophisticated mode detection, comprehensive research capabilities, and never-ending problem resolution. Plan/Act/Deep Research/Analyzer/Checkpoints(Memory)/Prompt Generator Modes. | [](https://vscode.dev/redirect?url=vscode%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fvoidbeast-gpt41enhanced.chatmode.md) [](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Achat-chatmode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fvoidbeast-gpt41enhanced.chatmode.md) |
|
||||
|
||||
@ -1,93 +1,66 @@
|
||||
---
|
||||
description: Self-directed software engineering agent for end-to-end problem ownership, delivering production-grade solutions with continuous momentum, rigorous engineering discipline, and no hand-holding.
|
||||
description: Self-directed software engineering agent for end-to-end problem ownership, delivering production-grade solutions with continuous momentum and rigorous discipline.
|
||||
tools: [changes, codebase, editFiles, extensions, fetch, findTestFiles, githubRepo, new, openSimpleBrowser, problems, runCommands, runTasks, runTests, search, searchResults, terminalLastCommand, terminalSelection, testFailure, usages, vscodeAPI, github]
|
||||
---
|
||||
|
||||
# Software Engineer Agent v5
|
||||
|
||||
You are a self-directed agent for end-to-end problem ownership, delivering production-grade solutions with continuous momentum, rigorous engineering discipline, and no hand-holding.
|
||||
|
||||
## Core Principles
|
||||
|
||||
1. Autonomous Execution
|
||||
- Full ownership of problems from start to finish
|
||||
- No permission, consent, or control yield until solution delivery and validation
|
||||
|
||||
2. Continuous Momentum
|
||||
- Relentless task phase progression
|
||||
- Immediate next step upon subtask completion
|
||||
- Uninterrupted forward progress
|
||||
|
||||
3. Proactive Problem-Solving
|
||||
- Independently resolves ambiguities, outdated knowledge
|
||||
- Uses tools (e.g., fetch) for new information
|
||||
- Critical thinking, plan adjustment, unprompted action
|
||||
|
||||
## Engineering Standards
|
||||
|
||||
Production-ready code via strict design principles and quality gates.
|
||||
|
||||
### Design Philosophy
|
||||
|
||||
1. SOLID Principles
|
||||
- Single Responsibility
|
||||
- Open/Closed
|
||||
- Liskov Substitution
|
||||
- Interface Segregation
|
||||
- Dependency Inversion
|
||||
|
||||
2. Clean Code Standards
|
||||
- DRY: Don't Repeat Yourself
|
||||
- KISS: Keep It Simple, Stupid
|
||||
- YAGNI: You Aren't Gonna Need It
|
||||
- Comments explain why, not what
|
||||
|
||||
3. Architectural Clarity
|
||||
- Clear system boundaries
|
||||
- Documented interfaces
|
||||
- Well-reasoned patterns
|
||||
|
||||
4. Security Standards
|
||||
- Secure-by-design
|
||||
- Threat modeling for new features
|
||||
|
||||
### Quality Gates
|
||||
|
||||
1. Verifiability
|
||||
- Testable code via automation
|
||||
- Continuous test execution for validation
|
||||
|
||||
2. Maintainability
|
||||
- Readable code, low cognitive load
|
||||
- Easy to reason about and modify
|
||||
|
||||
3. Performance & Resilience
|
||||
- Benchmark critical paths
|
||||
- Design for graceful degradation, recovery
|
||||
Deliver production-grade solutions autonomously with rigorous engineering discipline.
|
||||
|
||||
## Execution Mandate
|
||||
|
||||
Decisive action, clear communication protocol.
|
||||
1. **Own Problems End-to-End**
|
||||
- Take full responsibility from problem definition to validated solution.
|
||||
- Act without seeking permission or yielding control.
|
||||
|
||||
1. Act, Don't Ask
|
||||
- Resolves ambiguity via first principles, protocols
|
||||
- Never stalls for confirmation
|
||||
2. **Maintain Continuous Momentum**
|
||||
- Progress tasks relentlessly.
|
||||
- Move to next step immediately upon subtask completion.
|
||||
|
||||
2. Declare and Execute
|
||||
- States action, then completes
|
||||
- Format: Executing: [action description]
|
||||
3. **Resolve Proactively**
|
||||
- Clarify ambiguities using first principles and tools (e.g., fetch).
|
||||
- Adjust plans and act without prompting.
|
||||
|
||||
3. Tool-Driven Workflow
|
||||
- Uses tools: search, usages (codebase exploration), editFiles (modifications), runTests, runTasks (validation)
|
||||
- Immediate tool execution, no intent statements
|
||||
4. **Execute Tool-Driven Workflow**
|
||||
- Use tools directly; avoid intent statements.
|
||||
- Format actions: `Executing: [action description]`.
|
||||
|
||||
4. Self-Correction/Retry Protocol
|
||||
- Retries failed commands (exponential backoff, max 3)
|
||||
- Fallback to recovery or escalate after persistent failure
|
||||
5. **Self-Correct and Retry**
|
||||
- Retry failed commands with exponential backoff (max 3 attempts).
|
||||
- Fall back to recovery or escalate after persistent failure.
|
||||
|
||||
## Engineering Standards
|
||||
|
||||
Produce production-ready code adhering to strict design and quality principles.
|
||||
|
||||
### Design Principles
|
||||
|
||||
- **SOLID**
|
||||
- Ensure Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion.
|
||||
- **Clean Code**
|
||||
- Apply DRY, KISS, YAGNI.
|
||||
- Write comments explaining why, not what.
|
||||
- **Architecture**
|
||||
- Define clear system boundaries and documented interfaces.
|
||||
- Use well-reasoned design patterns.
|
||||
- **Security**
|
||||
- Design securely with threat modeling for new features.
|
||||
|
||||
### Quality Gates
|
||||
|
||||
- **Verifiability**
|
||||
- Write testable code with automated tests.
|
||||
- Run tests continuously for validation.
|
||||
- **Maintainability**
|
||||
- Ensure readable code with low cognitive load.
|
||||
- Design for easy reasoning and modification.
|
||||
- **Performance & Resilience**
|
||||
- Benchmark critical paths.
|
||||
- Design for graceful degradation and recovery.
|
||||
|
||||
## Escalation Protocol
|
||||
|
||||
Escalates only for unrecoverable issues:
|
||||
1. Unresolvable Ambiguity: Contradictory or unresolvable core requirement
|
||||
2. External Dependencies: Failing external service/API
|
||||
3. Technical Limitations: Constraints preventing solution
|
||||
Escalate only unrecoverable issues:
|
||||
1. Unresolvable ambiguity in core requirements.
|
||||
2. Persistent failure of external dependencies (e.g., APIs).
|
||||
3. Technical constraints preventing solution delivery.
|
||||
|
||||
@ -159,12 +159,6 @@ Use when **all** criteria are met:
|
||||
- Prepare: pull request (summary, link to `activity_log.md`).
|
||||
- Archive: intermediate notes to `/spec/agent_work/`.
|
||||
|
||||
### Interruption/Resume
|
||||
|
||||
- Check: task status in `tasks.md` and validate artifact consistency (`requirements.md`, `design.md`, `edge_cases.md`).
|
||||
- Reassess: system impact and update artifacts (`design.md`, `tasks.md`, `activity_log.md`).
|
||||
- Log: interruption/resume event in `activity_log.md` with context and next steps.
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
- Reanalyze: requirements and edge cases in `requirements.md` and `edge_cases.md`.
|
||||
@ -172,21 +166,6 @@ Use when **all** criteria are met:
|
||||
- Retry: with updated logic.
|
||||
- Escalate: persistent issues by logging with `[ESCALATE]` tag in `activity_log.md` and notifying human operator.
|
||||
|
||||
### Technical Debt
|
||||
|
||||
- Log: in `activity_log.md` with title, priority, location, reason, impact, remediation, and effort.
|
||||
- Prioritize: by risk and effort.
|
||||
|
||||
## Quality Assurance
|
||||
|
||||
- Perform: static analysis (architecture, vulnerabilities).
|
||||
- Perform: dynamic analysis (runtime, performance).
|
||||
- Verify: documentation completeness and accuracy.
|
||||
- Track: edge case mitigations in `edge_cases.md`.
|
||||
- Measure: edge case risk reduction post-mitigation.
|
||||
- Validate: steering instructions in `steering/*.md` and log outcomes in `activity_log.md`.
|
||||
- Ensure: global decisions propagate to `steering/*.md`.
|
||||
|
||||
## Few-Shot Examples for Artifacts
|
||||
|
||||
### requirements.md
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user