tegwick
35eebc0c1b
Implemented consistent naming convention for all Claude Code agents: - Prefix: All agents now start with 'agent-' - Format: agent-[function]-[specialty].md - Descriptive: 2-3 words describing primary purpose Agent Renames: • claude-expert.md → agent-claude-documentation.md • fortune-wisdom-guide.md → agent-wisdom-encouragement.md • kaizen-optimizer.md → agent-kaizen-optimization.md • priority-assistant.md → agent-priority-evaluation.md • project-assistant.md → agent-project-management.md • refactoring-assistant-optimized.md → agent-code-refactoring.md • repository-assistent.md → agent-repository-structure.md • tddai-assistant.md → agent-tdd-workflow.md • test-fixing-agent.md → agent-test-maintenance.md • tooling-optimizer.md → agent-tooling-optimization.md Updated References: - ProjectDiary.md: Updated agent references to new names - RelevantClaudeIssues.md: Updated agent tracking references Benefits: - Improved discoverability with consistent prefix - Clear functional categorization - Better organization and maintenance - Enhanced readability for development team 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
4.0 KiB
Relevant Claude Code Issues
Introduction
This document tracks Claude Code issues that directly impact our development workflows for the MarkiTect project. Each issue section provides a clear problem description, affected workflows, related GitHub issues for monitoring, available workarounds, and resolution tracking information.
Purpose:
- Document blocking Claude Code issues affecting project development
- Provide centralized tracking of GitHub issues to monitor for fixes
- Maintain awareness of workarounds and their trade-offs
- Enable quick assessment of when normal workflows can resume
Maintenance:
- Update when new blocking issues are discovered
- Check GitHub issue status weekly and update resolution monitoring
- Remove resolved issues after confirming fixes work in our environment
- Maintained by the agent-claude-documentation subagent as part of issue tracking responsibilities
🎯 CRITICAL WORKFLOW REMINDER: When discussing project issues (not Claude Code issues), ALWAYS fetch from Gitea first. Gitea is the source of truth for all issue assessment, feasibility evaluation, and implementation planning. Local files are insufficient for decision-making about issues. See ISSUE_WORKFLOW_REMINDER.md for complete workflow.
Resolved Issues
✅ RESOLVED: Custom Subagents Not Available
Problem Description (Historical)
Custom subagents defined in .claude/agents/ directory were not being detected or made available as subagent_type options in the Task tool. This prevented the intended workflow of using specialized subagents for domain-specific tasks like project management, documentation, or Claude Code expertise.
The custom subagent system appeared completely broken, with agents not being recognized despite proper YAML frontmatter configuration.
Resolution Details
Resolved Date: 2025-09-23 Resolution Method: Issue appears to have been fixed in current Claude Code version Verification: Successfully tested the following subagents:
- ✅
general-purpose- Full tool access for complex multi-step tasks - ✅
agent-claude-documentation- Specialized for Claude Code documentation and features - ✅
agent-project-management- Specialized for MarkiTect project status and development planning
Resolution Confirmation Steps:
- ✅ Custom agents now appear as valid
subagent_typeoptions in Task tool - ✅ Successfully invoked custom subagents for specialized tasks
- ✅ All intended multi-agent workflows are now functional
- ✅ No workarounds needed - normal operation restored
Impact of Resolution
Restored Workflows:
- Specialized Task Delegation: ✅ Custom subagents working for domain-specific tasks
- Project Management: ✅ agent-project-management subagent functional for status tracking and planning
- Documentation Assistance: ✅ agent-claude-documentation subagent operational for Claude Code expertise
- Task Decomposition: ✅ Full subagent ecosystem available
- Workflow Automation: ✅ Multi-agent collaborative workflows enabled
Workarounds No Longer Needed:
- No need to downgrade Claude Code versions
- No need to use only built-in general-purpose agent
- No need for manual role assignment
Related GitHub Issues (Historical Reference)
- #4623 - Custom agents not being detected
- #4728 - Agent discovery mechanism broken
- #4626 - Custom agents missing from UI
- #5185 - Agent configuration not working
- #4182 - Task tool limitations for nested agents
Monitoring Schedule
This document should be reviewed weekly to check for issue resolution and update status. The agent-claude-documentation subagent is responsible for maintaining this tracking and updating the project team when workflows can resume normal operation.