diff --git a/.claude/agents/claude-expert.md b/.claude/agents/agent-claude-documentation.md similarity index 100% rename from .claude/agents/claude-expert.md rename to .claude/agents/agent-claude-documentation.md diff --git a/.claude/agents/refactoring-assistant-optimized.md b/.claude/agents/agent-code-refactoring.md similarity index 100% rename from .claude/agents/refactoring-assistant-optimized.md rename to .claude/agents/agent-code-refactoring.md diff --git a/.claude/agents/kaizen-optimizer.md b/.claude/agents/agent-kaizen-optimization.md similarity index 100% rename from .claude/agents/kaizen-optimizer.md rename to .claude/agents/agent-kaizen-optimization.md diff --git a/.claude/agents/priority-assistant.md b/.claude/agents/agent-priority-evaluation.md similarity index 100% rename from .claude/agents/priority-assistant.md rename to .claude/agents/agent-priority-evaluation.md diff --git a/.claude/agents/project-assistant.md b/.claude/agents/agent-project-management.md similarity index 100% rename from .claude/agents/project-assistant.md rename to .claude/agents/agent-project-management.md diff --git a/.claude/agents/repository-assistent.md b/.claude/agents/agent-repository-structure.md similarity index 100% rename from .claude/agents/repository-assistent.md rename to .claude/agents/agent-repository-structure.md diff --git a/.claude/agents/tddai-assistant.md b/.claude/agents/agent-tdd-workflow.md similarity index 100% rename from .claude/agents/tddai-assistant.md rename to .claude/agents/agent-tdd-workflow.md diff --git a/.claude/agents/test-fixing-agent.md b/.claude/agents/agent-test-maintenance.md similarity index 100% rename from .claude/agents/test-fixing-agent.md rename to .claude/agents/agent-test-maintenance.md diff --git a/.claude/agents/tooling-optimizer.md b/.claude/agents/agent-tooling-optimization.md similarity index 100% rename from .claude/agents/tooling-optimizer.md rename to .claude/agents/agent-tooling-optimization.md diff --git a/.claude/agents/fortune-wisdom-guide.md b/.claude/agents/agent-wisdom-encouragement.md similarity index 100% rename from .claude/agents/fortune-wisdom-guide.md rename to .claude/agents/agent-wisdom-encouragement.md diff --git a/RelevantClaudeIssues.md b/RelevantClaudeIssues.md index 6191a0d5..56a4213e 100644 --- a/RelevantClaudeIssues.md +++ b/RelevantClaudeIssues.md @@ -14,7 +14,7 @@ This document tracks Claude Code issues that directly impact our development wor - 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 claude-expert subagent as part of issue tracking responsibilities +- 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. @@ -37,8 +37,8 @@ The custom subagent system appeared completely broken, with agents not being rec **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 -- ✅ `claude-expert` - Specialized for Claude Code documentation and features -- ✅ `project-assistant` - Specialized for MarkiTect project status and development planning +- ✅ `agent-claude-documentation` - Specialized for Claude Code documentation and features +- ✅ `agent-project-management` - Specialized for MarkiTect project status and development planning **Resolution Confirmation Steps:** 1. ✅ Custom agents now appear as valid `subagent_type` options in Task tool @@ -50,8 +50,8 @@ The custom subagent system appeared completely broken, with agents not being rec **Restored Workflows:** - **Specialized Task Delegation**: ✅ Custom subagents working for domain-specific tasks -- **Project Management**: ✅ project-assistant subagent functional for status tracking and planning -- **Documentation Assistance**: ✅ claude-expert subagent operational for Claude Code expertise +- **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 @@ -72,4 +72,4 @@ The custom subagent system appeared completely broken, with agents not being rec ## Monitoring Schedule -This document should be reviewed weekly to check for issue resolution and update status. The claude-expert subagent is responsible for maintaining this tracking and updating the project team when workflows can resume normal operation. +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. diff --git a/history/ProjectDiary.md b/history/ProjectDiary.md index 6536daf1..3fc3990b 100644 --- a/history/ProjectDiary.md +++ b/history/ProjectDiary.md @@ -182,7 +182,7 @@ This diary tracks major work packages, events, and milestones in the MarkiTect p **Time Estimate:** ~1-2 hours of refactoring and test cleanup **AI Resources:** ~15-20 Claude Sonnet 4 conversations, estimated 30K+ tokens -**FRAMEWORK MATURITY:** Successfully transformed tddai from a MarkiTect-specific tool into a truly project-agnostic Test-Driven Development framework. Removed all MarkiTect-specific references from core tddai modules (`coverage_analyzer.py`, `config.py`, `tddai_cli.py`) and updated the tddai-assistant agent definition to use generic examples applicable to any software project. The framework now uses configurable environment variables (`TDDAI_WORKSPACE_DIR`, `TDDAI_GITEA_URL`, `TDDAI_REPO_OWNER`, `TDDAI_REPO_NAME`) allowing deployment across different projects and platforms. +**FRAMEWORK MATURITY:** Successfully transformed tddai from a MarkiTect-specific tool into a truly project-agnostic Test-Driven Development framework. Removed all MarkiTect-specific references from core tddai modules (`coverage_analyzer.py`, `config.py`, `tddai_cli.py`) and updated the agent-tdd-workflow agent definition to use generic examples applicable to any software project. The framework now uses configurable environment variables (`TDDAI_WORKSPACE_DIR`, `TDDAI_GITEA_URL`, `TDDAI_REPO_OWNER`, `TDDAI_REPO_NAME`) allowing deployment across different projects and platforms. **CONFIGURATION SYSTEM:** Implemented flexible project configuration system that defaults to sensible generic values while supporting per-project customization. Created `.env.tddai` and `tddai-setup.sh` for MarkiTect-specific configuration, demonstrating how any project can configure tddai for their needs. The configuration system validates required fields while maintaining clean separation between framework defaults and project-specific settings. @@ -203,11 +203,11 @@ This diary tracks major work packages, events, and milestones in the MarkiTect p **SIDEQUEST ACHIEVEMENT:** Successfully implemented IssueWriter functionality that emerged as a natural sidequest during development work. Created `tddai/issue_writer.py` with comprehensive authenticated PATCH capabilities for updating Gitea issues via API. Implementation includes full authentication support via `GITEA_TOKEN` environment variable, robust error handling for API failures and authentication issues, and clean API design with specific methods for updating titles, bodies, and issue states. Added 13 comprehensive tests in `tests/test_issue_writer.py` covering all authentication scenarios, PATCH operations, error conditions, and edge cases. All tests pass and integrate seamlessly with existing 45+ test suite. -**METHODOLOGY BREAKTHROUGH:** Formalized the project's actual development workflow as the **TDD8 cycle** - a comprehensive 8-step methodology extending traditional TDD: **ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH**. This framework captures the complete transformation from requirements to production-ready functionality. Created comprehensive tddai-assistant subagent (.claude/agents/tddai-assistant.md) with detailed guidance for each TDD8 step, sophisticated sidequest management strategies, and project-specific knowledge including workspace management, Gitea integration, and test coverage standards. +**METHODOLOGY BREAKTHROUGH:** Formalized the project's actual development workflow as the **TDD8 cycle** - a comprehensive 8-step methodology extending traditional TDD: **ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH**. This framework captures the complete transformation from requirements to production-ready functionality. Created comprehensive agent-tdd-workflow subagent (.claude/agents/agent-tdd-workflow.md) with detailed guidance for each TDD8 step, sophisticated sidequest management strategies, and project-specific knowledge including workspace management, Gitea integration, and test coverage standards. **WORKFLOW ENHANCEMENT:** The TDD8 framework addresses the reality that development involves more than just RED-GREEN-REFACTOR cycles. It includes upfront issue analysis (ISSUE), comprehensive test design (TEST), traditional TDD core (RED-GREEN-REFACTOR), and crucial production-readiness steps (DOCUMENT-REFINE-PUBLISH). Integrated sidequest management recognizes that blocking and supporting sidequests naturally emerge at different cycle phases and provides specific strategies for each scenario. -**INFRASTRUCTURE MATURITY:** This session demonstrates the project's evolution from basic TDD to a sophisticated development methodology. The IssueWriter implementation showcases clean separation of concerns, comprehensive test coverage, and proper integration patterns. The tddai-assistant provides authoritative guidance for maintaining these standards while adapting to the dynamic nature of software development through intelligent sidequest management. +**INFRASTRUCTURE MATURITY:** This session demonstrates the project's evolution from basic TDD to a sophisticated development methodology. The IssueWriter implementation showcases clean separation of concerns, comprehensive test coverage, and proper integration patterns. The agent-tdd-workflow provides authoritative guidance for maintaining these standards while adapting to the dynamic nature of software development through intelligent sidequest management. ---