feat: add QA-gated epic workflow with business analyst and QA specialist agents#27
Merged
feat: add QA-gated epic workflow with business analyst and QA specialist agents#27
Conversation
…ist agents - Added requirements-gatherer agent: Business analyst role using BABOK principles - Added overseer agent: QA specialist with mandatory quality checkpoints - Added epic-workflow skill: Manages epic-based development with automatic feature progression - Updated developer agent to integrate QA gates throughout workflow - Enhanced architect agent with pattern selection and industry terminology - Modified TODO.md template to support current feature tracking within epics - Added EPICS.md template for epic tracking and management The new workflow enforces quality at 4 mandatory checkpoints: 1. Requirements completeness review 2. Test quality review 3. Implementation SOLID/DRY/KISS review 4. Final approval before feature completion BREAKING CHANGE: Projects now use epic-based workflow with mandatory QA gates
- Removed model specifications from all 7 agents (5 in generated projects, 2 in template) - Removed model specification from create-agent skill example - Updated AGENTS.md to accurately document all template components: - Listed all 5 generated project agents (added overseer and requirements-gatherer) - Added all skills to template structure (session-workflow, epic-workflow, create-skill, create-agent) - Documented template's own agents and skills (repo-manager, git-release, pr-management) - Clarified roles: template-manager handles template tasks, repo-manager handles git/GitHub - Added Template Management Workflow section to explain agent usage This ensures the template is model-agnostic and documentation accurately reflects what exists.
Owner
Author
Update: Model specifications removed and documentation fixedThis PR has been updated with an additional commit that addresses:
The template is now fully model-agnostic and the documentation accurately reflects what exists in the repository. |
- Updated agent descriptions to use industry-standard role titles: - developer.md: Development Lead specializing in TDD - architect.md: Software Architect specializing in design patterns - overseer.md: QA Specialist enforcing quality standards - requirements-gatherer.md: Business Analyst using BABOK methodology - repo-manager.md: Release Engineer managing Git workflows - Updated template's own agents (template-manager, repo-manager): - Changed from 'meta agent/repository management' to DevOps Engineer/Release Engineer - Fixed version reference (template uses semantic versioning) - Removed themed naming (for generated projects only) - Added proper GitFlow methodology and CI/CD standards - Updated AGENTS.md: - Added 'Enterprise Development Framework' section - Documented proper team structure roles - Clarified template vs generated project agent responsibilities - Updated README.md: - Added QA gates and epic workflow to features - Updated workflow to 10-step with mandatory QA gates - Removed multi-language template support (not planned) - Updated quick start to show requirements-gatherer workflow
Resolved conflicts in:
- AGENTS.md: Kept our version with all 5 agents and QA-gated workflow
- architect.md: Kept our version with Software Architect title
- developer.md: Kept our version with Development Lead title
- overseer.md: Kept our version (add/add conflict)
- requirements-gatherer.md: Kept our version (add/add conflict)
- {{cookiecutter.project_slug}}/AGENTS.md: Kept our version with new workflow
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
This PR introduces a comprehensive QA-gated epic workflow system that mirrors enterprise development practices with dedicated business analyst and QA specialist agents.
Type of Change
Changes Made
New Workflow Features
Epic-Based Development
Projects now follow an epic-based workflow where features are organized into epics, tracked in EPICS.md, and automatically progress through features after QA approval.
Mandatory QA Gates
The workflow enforces quality at 4 checkpoints:
Industry Standard Roles
Testing
Quality Checklist
Breaking Changes
Projects now use epic-based workflow with mandatory QA gates. This changes the development flow from linear to epic-based with QA checkpoints.
Migration Notes
Existing projects can adopt the new workflow by:
Example Usage