feat: update specialized agents to use new issue-facade system

Updated Claude Code agent configuration and specialized subagents to use the new issue-facade system instead of the deprecated tddai framework:

Agent Updates:
- Updated .claude/settings.local.json with issue-facade CLI permissions
- Removed obsolete tddai_cli.py reference from permissions
- Added permissions for issue-facade CLI commands

Subagent Updates:
- agent-project-management.md: Updated to reference issue-facade for issue management
- agent-requirements-engineering.md: Replaced tddai references with issue-facade
- agent-tdd-workflow.md: Comprehensive update to use issue-facade system
  - Renamed from tddai-assistant to tdd-workflow-assistant
  - Updated all command references to use issue-facade CLI
  - Replaced workspace structure with issue-facade architecture

The specialized subagents now properly leverage the universal issue-facade
system for backend-agnostic issue management across GitHub, GitLab, Gitea,
and local SQLite storage.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
2025-10-25 01:03:04 +02:00
parent a8e5b4b044
commit ce14d3b2de
3 changed files with 25 additions and 23 deletions

View File

@@ -26,11 +26,11 @@ You are the MarkiTect project assistant, specialized in providing project status
**Repository Structure:** **Repository Structure:**
- Main project hosted on Gitea with issue tracking for use cases and tasks - Main project hosted on Gitea with issue tracking for use cases and tasks
- Documentation maintained in `wiki/` submodule - Documentation maintained in `wiki/` submodule
- Test-drive dev workflow with tests in `tests/` handled by tddai-assistent subagent - Test-driven development workflow with comprehensive test coverage
**Development Workflow:** **Development Workflow:**
- Issue-driven development using Gitea API integration - Issue-driven development using Gitea API integration
- TDD8 methodology via tddai-assistant subagent for comprehensive test-driven development - Issue management via universal issue-facade CLI that works with multiple backends
- All commits require green test state - All commits require green test state
**Issue Management Protocol:** **Issue Management Protocol:**
@@ -41,8 +41,8 @@ You are the MarkiTect project assistant, specialized in providing project status
- **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close - **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close
**TDD Workflow Management:** **TDD Workflow Management:**
- For all TDD-related guidance, workflow management, and test-driven development questions, use the **tddai-assistant** subagent - For issue management tasks, use the **issue-facade** system located in `issue-facade/`
- The tddai-assistant specializes in the TDD8 methodology (ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle) - The issue-facade provides unified CLI for GitHub, GitLab, Gitea, and local SQLite backends
- This includes sidequest management, test planning, and comprehensive development workflow guidance - This includes sidequest management, test planning, and comprehensive development workflow guidance
### Response Guidelines ### Response Guidelines

View File

@@ -115,8 +115,9 @@ python tools/requirements_engineering_toolkit.py validate-mocks --test-file test
```makefile ```makefile
# Enhanced Makefile targets # Enhanced Makefile targets
tdd-start: validate-requirements issue-start: validate-requirements
python tddai_cli.py tdd-start $(NUM) # Use issue-facade for issue management
cd issue-facade && python -m cli.main show $(NUM)
validate-requirements: validate-requirements:
python tools/requirements_engineering_toolkit.py analyze python tools/requirements_engineering_toolkit.py analyze
@@ -453,8 +454,9 @@ validate-requirements:
python tools/requirements_engineering_toolkit.py analyze python tools/requirements_engineering_toolkit.py analyze
python tools/requirements_engineering_toolkit.py validate-mocks python tools/requirements_engineering_toolkit.py validate-mocks
tdd-start: validate-requirements issue-start: validate-requirements
python tddai_cli.py tdd-start $(NUM) # Use issue-facade for issue management
cd issue-facade && python -m cli.main show $(NUM)
``` ```
### Tool Dependencies ### Tool Dependencies

View File

@@ -1,12 +1,12 @@
--- ---
name: tddai-assistant name: tdd-workflow-assistant
description: Expert guidance for the TDD8 workflow methodology, specializing in the comprehensive ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle with sophisticated sidequest management and proper test organization. description: Expert guidance for test-driven development workflow, specializing in comprehensive TDD methodology with issue management via the universal issue-facade system.
--- ---
# TDDAi Assistant Agent # TDD Workflow Assistant Agent
## Mission ## Mission
Expert guidance for the TDD8 workflow methodology, specializing in the comprehensive ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle with sophisticated sidequest management and proper test organization. Expert guidance for test-driven development methodology, specializing in comprehensive TDD workflow with integrated issue management using the universal issue-facade system for backend-agnostic issue tracking.
## The TDD8 Cycle Framework ## The TDD8 Cycle Framework
@@ -96,22 +96,22 @@ The **TDD8 cycle** is an 8-step comprehensive development workflow that extends
## Capabilities ## Capabilities
### Core TDD8 Workflow Expertise ### Core TDD8 Workflow Expertise
You are the authoritative guide for the TDD8 workflow using the tddai system. You understand how each step builds upon the previous ones and how sidequests can emerge at any stage of any software development project. You are the authoritative guide for the TDD8 workflow using the issue-facade system for issue management. You understand how each step builds upon the previous ones and how sidequests can emerge at any stage of any software development project.
**Primary TDD Commands:** **Primary Issue Management Commands:**
- `make tdd-start NUM=X` - Start working on an issue (creates workspace) - Issue management via issue-facade: `cd issue-facade && python -m cli.main list`
- `make tdd-add-test` - Add test to current issue workspace - `cd issue-facade && python -m cli.main show ISSUE_NUM` - Show issue details
- `make tdd-status` - Show current workspace state - `cd issue-facade && python -m cli.main create "Title" "Description"` - Create new issue
- `make tdd-finish` - Complete issue work (moves tests to main) - `cd issue-facade && python -m cli.main close ISSUE_NUM` - Close completed issue
**Supporting Commands:** **Supporting Commands:**
- `make test-coverage NUM=X` - Analyze test coverage for an issue - `make test-coverage` - Analyze test coverage
- `make test` - Run all tests - `make test` - Run all tests
- `make list-issues` - Show all Gitea issues with status - Tea CLI: `tea issues list` - Show all Gitea issues with status
- `make show-issue NUM=X` - Show detailed view of specific issue - Tea CLI: `tea issue show NUM` - Show detailed view of specific issue
### Workspace Management Understanding ### Workspace Management Understanding
You understand the workspace structure (default: `.tddai_workspace/`, configurable per project): You understand the project structure with issue-facade for issue management:
``` ```
{workspace_dir}/ {workspace_dir}/
├── current_issue.json # Active issue metadata ├── current_issue.json # Active issue metadata
@@ -152,7 +152,7 @@ You understand the workspace structure (default: `.tddai_workspace/`, configurab
### TDDAi Framework Components ### TDDAi Framework Components
**Core Infrastructure:** **Core Infrastructure:**
- `tddai/` - TDD workflow framework - `issue-facade/` - Universal issue management facade
- `workspace.py` - Workspace management - `workspace.py` - Workspace management
- `issue_fetcher.py` - Issue API integration - `issue_fetcher.py` - Issue API integration
- `issue_writer.py` - Issue updates via PATCH - `issue_writer.py` - Issue updates via PATCH