Feature/1133abe3 remove bug triage workflow#12
Merged
Conversation
…th AI memory integration
- Rename workflow from implement_feature_workflow to implementation_workflow for clarity
- Add comprehensive AI memory-based configuration system
- Support global and project-specific preferences
- Implement branch naming variable system ({task-id-short}, {description}, etc.)
- Add work type detection (bug/feature/enhancement/hotfix)
- Clarify template validation vs procedural step override distinction
- Include memory configuration setup helper for first-time users
- Document variable expansion and sanitization rules
- Support team-specific workflow customization without code changes
Breaking Change: Workflow name changed from implement_feature_workflow to implementation_workflow
Users invoking the old name will need to update to the new name.
This enables teams to customize workflows through AI memory while maintaining simple
defaults that work out of box. Custom workflow steps override template procedural
guidance while template validation requirements remain enforced.
Task: 70490b4d-f412-4c20-93f1-cacf038a2ee8
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
…ross all documentation Updated workflow name references in all documentation files to reflect the rename from implement_feature_workflow to implementation_workflow. Updated descriptions to clarify the workflow handles tasks, features, and bugs (not just features). Files updated: - docs/workflow-prompts.md - docs/ai-guidelines.md - docs/api-reference.md - docs/templates.md - docs/developer-guides/architecture.md - README.md All references now use the new workflow name with accurate scope descriptions. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…ntation
Added comprehensive documentation for the branch naming variable system in the
implementation_workflow prompt including:
- Complete variable reference table with descriptions and examples
- Description sanitization rules (lowercase, hyphenation, special char removal)
- Default branch naming patterns for all work types (bug/feature/hotfix/enhancement)
- Team-specific pattern examples (Jira, Linear, priority-based, feature-grouped)
- Step-by-step variable expansion process
- Commit message variable support
- Added {feature-id-short} variable for feature-grouped patterns
This provides clear guidance for AI agents on how to expand branch naming
variables and allows teams to customize workflows through memory configuration.
Related to Task a2a36aeb-324c-4ff6-8008-361d1a1d77ef
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added comprehensive 300+ line documentation section to workflow-prompts.md covering memory-based workflow customization with: - Overview of memory-based customization capabilities - Minimal configuration example (just PR preference) - Complete memory configuration schema - Branch naming variables reference table - Template validation vs procedural override explanation - 4 real-world configuration examples: 1. Startup team (minimal setup) 2. Jira integration with custom branch naming 3. Enterprise team with staging deployment 4. Priority-based branch naming - Natural language customization examples - Global vs project-specific configuration explanation - Getting started guide - Best practices (DO/DON'T) - Cross-references to related documentation This provides comprehensive guidance for teams to customize implementation workflows through AI memory without modifying code. Related to Task 12bf786d-0bb6-4638-b322-3be116733025 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Added 330+ line section to ai-guidelines.md documenting memory-based workflow customization patterns for AI agents including: - Memory architecture (global vs project-specific, priority rules) - When to check memory (before branches, PRs, workflow steps) - Configuration schema for AI agents to parse - Variable expansion pattern with sanitization algorithm - 4 complete interaction flow examples: 1. First-time workflow (no config) 2. Workflow with global preferences 3. Workflow with project overrides 4. Natural language customization - Best practices for AI agents (DO/DON'T lists) - Template validation vs procedural override rules - Interactive setup flow guidance - Clear communication patterns - Integration points with workflows - Troubleshooting common issues This provides comprehensive guidance for AI agents on how to use memory-based customization to respect user preferences and enable team-specific workflows. Related to Task dbc9ddf9-f3e0-4d26-83c0-c7a7a5b63496 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Created docs/examples/ directory with 5 ready-to-use memory configuration examples for different team types and use cases: 1. memory-minimal.md - Minimal setup for getting started 2. memory-startup.md - Fast-moving startup workflow 3. memory-enterprise.md - Enterprise with compliance and quality gates 4. memory-jira.md - Jira integration with ticket references 5. memory-bugfix.md - Custom bug fix workflow with staging deployment Each example includes: - Use case description and best-for scenarios - Complete configuration ready to copy/paste - Detailed explanation of behavior - Branch and commit examples - Customization tips - Trade-offs analysis - Team size recommendations Also created README.md index with: - Quick reference to all examples - Usage instructions - Storage location guidance - Progressive enhancement path - Example combining instructions Related to Task f012ae36-8082-4950-85a0-10254a2c2994 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…ion_workflow Remove the redundant bug_triage_workflow prompt, as it delegates to implementation workflows at Step 6. Bug handling is now integrated directly into implementation_workflow, which will be enhanced in the next task to provide bug-specific guidance and mandatory regression testing requirements. **Code Changes**: - Remove addBugTriageWorkflowPrompt function from WorkflowPromptsGuidance.kt - Remove function call from configureWorkflowPrompts - Update workflow count from 6 to 5 in README.md **Documentation Updates**: - Remove bug_triage_workflow section from workflow-prompts.md - Remove from ai-guidelines.md references (2 locations) - Remove from README.md (update count to 5 workflows) - Remove from developer-guides/architecture.md - Remove from templates.md - Remove from api-reference.md - Update McpServerAiGuidance.kt (also fix missed implement_feature_workflow rename) - Update TaskOrchestratorResources.kt (remove 4 references, update workflow numbering) **Verification**: - Build succeeds with no compilation errors - No references to bug_triage_workflow remain in codebase - All workflow counts updated to reflect 5 prompts 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…mandatory regression testing Add comprehensive bug handling capabilities to implementation_workflow, including mandatory regression test requirements to prevent bugs from recurring. This addresses the user's requirement: "ensure the workflow creates tests to prevent the issue from coming back again." **Step 3 Enhancement - Bug Detection**: - Detect task-type-bug from tags - Check if Bug Investigation template is applied - Offer to apply template if not present - Verify investigation sections documented before implementation - Ensure root cause is documented before starting fix **Bug-Specific Implementation Guidance** (Step 5): - Reproduce bug in tests first (test should fail) - Document reproduction steps - Implement fix addressing root cause - Verify test passes with fix - Create comprehensive regression tests **Regression Testing Requirements Section** (NEW - 156 lines): Comprehensive mandatory requirements for bug fixes including: 1. **Bug Reproduction Test** (Required): - Test fails with old code, passes with fix - Documents what broke and how 2. **Edge Case Tests** (Required if applicable): - Boundary conditions that led to bug - Scenarios not previously tested 3. **Integration Tests** (Required if bug crossed boundaries): - Component interaction testing - Realistic scenarios - No cascading failures 4. **Performance Tests** (Required if performance-related): - No performance regressions - Load testing if load-related **Test Documentation Requirements**: - Test names must reference task ID - BUG/ROOT CAUSE/FIX comments required - Proper assertions **Common Test Patterns**: - Null/Empty input handling - Race conditions - Boundary values - State management **Enhanced Validation** (Step 7): - Bug reproduction test mandatory - Regression tests for all scenarios - Test documentation complete - Test names reference task ID - Code coverage increased - CRITICAL warning: Cannot complete without tests **Acceptance Criteria Met**: ✅ Bug detection works (task-type-bug tag) ✅ Regression testing section added with examples ✅ Bug Investigation template integration ✅ Root cause required before implementation ✅ Test examples for all types (unit, integration, performance) ✅ Clear error if completing without tests 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…ting requirements Enhance implementation_workflow documentation to reflect consolidated architecture with comprehensive bug handling and mandatory regression testing enforcement. **implementation_workflow Enhancement**: "What It Covers" expanded from 5 to 8 steps: - Added memory-based configuration loading - Added work type detection (task, feature, bug) - Added bug-specific investigation and root cause verification - Added mandatory regression testing for bug fixes "Key Decisions" enhanced with bug-specific guidance: - When bug investigation is complete - What regression tests are needed "Special Features" expanded with: - Bug Investigation Integration - Regression Testing Enforcement **New "Bug Handling" Subsection** (29 lines): Comprehensive 4-phase process for bugs: 1. Investigation Phase - template application, root cause verification 2. Implementation Phase - reproduce bug, document, fix, verify 3. Regression Testing - 4 required test types 4. Completion Validation - cannot complete without tests **New "Regression Testing Requirements" Section** (175 lines): Comprehensive mandatory requirements with: - When Required: All bug fixes, hotfixes - 4 Required Test Types with examples: 1. Bug Reproduction Test (fails old, passes fix) 2. Edge Case Tests (boundary conditions) 3. Integration Tests (cross-component) 4. Performance Tests (if relevant) - Test Naming Convention with format and examples - Test Documentation Requirements (BUG/ROOT CAUSE/FIX) - Completion Checklist (9 items) - Common Patterns (4 patterns with code examples) - Enforcement explanation All examples in Kotlin with proper test naming, comments, and assertions. **Acceptance Criteria Met**: ✅ bug_triage_workflow already removed (Task 1) ✅ implementation_workflow enhanced with bug guidance ✅ Regression testing comprehensively documented ✅ Internal link added to new section ✅ Ready for memory customization updates (Tasks 3-4) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…ensive memory patterns Enhance ai-guidelines.md with detailed memory integration patterns for all workflows and comprehensive bug handling guidance. **Feature Creation Workflow Memory Integration** (NEW - 46 lines): - Configuration schema for default templates, tag conventions, auto-task creation - Memory integration pattern (5-step process) - Complete example showing automatic template application and task creation - Enables teams to standardize feature creation process **Project Setup Workflow Memory Integration** (NEW - 59 lines): - Configuration schema for standard features, foundation tasks, documentation - Memory integration pattern (6-step process) - Complete example showing automated project initialization - Enables teams to standardize project structure and setup **Bug Handling Pattern** (NEW - 112 lines): Comprehensive bug handling workflow with 4 phases: 1. Bug Detection (4-step process) 2. Investigation Phase (3-step guidance) 3. Implementation Phase (5-step approach) 4. Regression Testing Requirements (MANDATORY): - 4 required test types with descriptions - Completion validation checklist (9 items) - CRITICAL enforcement note Complete example bug workflow showing: - Template application offering - Investigation guidance - Root cause identification - Regression test creation (5 tests) - Test naming and documentation **Best Practices Enhancement**: Added 2 new items for AI Agents: 6. "Handle bugs with regression testing" (6 bullet points): - Bug detection process - Template offering - Root cause verification - MANDATORY regression testing - Test documentation enforcement - Cannot complete without tests 7. "Use implementation_workflow for all work types" (4 bullet points): - Unified workflow for tasks/features/bugs - Automatic adaptation based on work type - Bug-specific guidance integration - Memory configuration applies to all **Summary of Changes**: - Other Workflow Integration section expanded from 9 lines to 217 lines - Added comprehensive memory patterns for create_feature and project_setup - Added complete bug handling pattern with regression testing enforcement - Added 2 new AI agent best practices - All acceptance criteria met 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…for bugs Replace outdated "Follow the bug triage workflow" reference with "Use the implementation workflow for this bug fix" to reflect consolidated architecture where implementation_workflow handles all work types including bugs. **Change**: - Line 64: "Follow the bug triage workflow" → "Use the implementation workflow for this bug fix" **Context**: Part of workflow consolidation effort. The bug_triage_workflow has been removed and its functionality integrated into implementation_workflow with enhanced bug-specific guidance and mandatory regression testing. **Files Verified**: ✅ No remaining bug_triage references in codebase (grep verified) ✅ All workflow counts updated (5 workflows) ✅ All documentation consistent with consolidated architecture **Task Completion**: All documentation files have been updated to reflect the consolidated workflow architecture. No broken references remain. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Enhanced create_feature_workflow with comprehensive memory-based customization: **Memory Configuration Support**: - Step 1: Load feature creation configuration from memory - Supports global (user-wide) and project-specific configuration - Configuration schema for default templates, tag conventions, auto-task creation **Step Updates**: - Step 4 (Create the Feature): Apply memory-based defaults for templates and tags - Uses feature_default_templates from memory if configured - Applies feature_tag_prefix and feature_tags_auto_add conventions - Falls back to manual selection if no configuration found - Step 6 (Create Associated Tasks): Auto-create initial tasks if configured - Uses feature_create_initial_tasks flag - Applies feature_initial_task_templates from memory - Inherits feature tags and adds task-specific tags - Added "Saving Memory Configuration" section before Best Practices - Guides users in saving preferences for future workflows - Provides complete configuration schema example **Workflow Improvements**: - Renumbered steps correctly (was 7 steps, now 8) - Fixed duplicate Step 3 numbering issue - Added tag convention examples - Enhanced template selection guidance This provides consistent customization capability matching implementation_workflow. Related to feature: Workflow Architecture Consolidation and Enhancement (44359986) Task: Add memory integration to create_feature_workflow (d9c4dcd0) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Enhanced project_setup_workflow with comprehensive memory-based customization: **Memory Configuration Support**: - Step 1: Load project setup configuration from memory - Supports global (user-wide) and project-specific configuration - Configuration schema for standard features, foundation tasks, documentation standards **Step Updates**: - Step 5 (Feature Planning): Auto-create standard features from memory - Uses project_standard_features list if configured - Falls back to manual feature identification if no configuration found - Step 6 (Initial Task Creation): Auto-create foundation tasks from memory - Uses project_foundation_tasks with templates - Applies memory-configured templates to tasks - Falls back to manual task creation if no configuration found - Added "Saving Memory Configuration" section before Best Practices - Guides users in saving preferences for future projects - Provides complete configuration schema example **Workflow Improvements**: - Renumbered steps correctly (was 9 steps, now 10) - Step 1 (Initialize AI) → Step 2 - Step 2 (Project Foundation) → Step 3 - Step 3 (Documentation) → Step 4 - Step 4 (Feature Planning) → Step 5 - Step 5 (Initial Tasks) → Step 6 - Step 6 (Template Strategy) → Step 7 - Step 7 (Dev Workflow) → Step 8 - Step 8 (Dependencies) → Step 9 - Step 9 (Monitoring) → Step 10 **Memory Configuration Schema**: - project_standard_features: List of standard features to create - project_foundation_tasks: List of foundation tasks with templates - project_documentation_sections: Standard documentation section titles This provides consistent customization capability across all workflows, completing the memory integration feature for workflow architecture consolidation. Related to feature: Workflow Architecture Consolidation and Enhancement (44359986) Task: Add memory integration to project_setup_workflow (99956df3) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Workflow Architecture Consolidation and Enhancement
Summary
This PR consolidates the workflow architecture by removing the redundant bug_triage_workflow and enhancing implementation_workflow to intelligently handle all work types (tasks,
features, and bugs) with specialized guidance. It also extends memory-based customization to create_feature_workflow and project_setup_workflow for consistent team preferences across
all workflows.
Key Achievement: Mandatory regression testing for all bug fixes to prevent recurrence.
Changes Made
🔧 Workflow Architecture
Removed bug_triage_workflow (Redundant)
Enhanced implementation_workflow with Smart Bug Handling
🧠 Memory Integration (New Capability)
create_feature_workflow Memory Integration (127 additions)
project_setup_workflow Memory Integration (134 additions)
📚 Documentation Updates
docs/workflow-prompts.md (227 additions)
docs/ai-guidelines.md (232 additions)
Other Documentation Files Updated:
Key Improvements
✅ Simpler Architecture
✅ Better Bug Handling
✅ Team Customization
✅ Quality Enforcement
✅ Comprehensive Documentation
Breaking Changes
specialized guidance including mandatory regression testing.
Migration Path: No action required. AI agents will automatically use implementation_workflow for bug fixes, which now includes all the functionality of the removed bug_triage_workflow
plus enhanced regression testing requirements.
Testing
Related Work
Feature: Workflow Architecture Consolidation and Enhancement (44359986-3a52-4206-9f8b-b643cb05a08f)
Tasks Completed (7/7):
Commits: 7 commits
Reviewer Notes
Focus Areas:
Questions for Discussion: