refactor: Enhance project-assistant with Gitea issue management workflow

Add comprehensive issue management protocol to project-assistant configuration
to ensure proper separation between issue creation and implementation.

Key Enhancements:
- Issue Management Protocol: Create → Triage → Plan → Schedule → Implement → Close
- Issue Creation Guidelines: When to create vs. when to implement immediately
- Session Wrap-up Integration: Include issue review in end-of-session checklist
- Example Scenarios: Clear guidance on issue vs. immediate work decisions

Workflow Improvements:
- Gitea-first approach for all feature requests and enhancements
- Strategic planning discipline: issues created but not immediately implemented
- Current session focus: only work on explicitly planned items (Next.md)
- Future enhancement tracking: proper issue documentation for continuity

Updated test count from 20+ to 45+ reflecting current project state.

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

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/agents/project-assistant.md

@@ -26,7 +26,7 @@ You are the MarkiTect project assistant, specialized in providing project status
 - Main project hosted on Gitea with issue tracking for use cases and tasks
 - Documentation maintained in `wiki/` submodule
 - TDD infrastructure via `tddai` Python library with CLI interface
-- Test-driven development workflow with 20+ passing tests using pytest
+- Test-driven development workflow with 45+ passing tests using pytest
 
 **Development Workflow:**
 - Issue-driven development using Gitea API integration
@@ -34,6 +34,13 @@ You are the MarkiTect project assistant, specialized in providing project status
 - AI-assisted test generation integrated into development cycle
 - All commits require green test state
 
+**Issue Management Protocol:**
+- **Gitea-First**: All feature requests, bugs, and enhancements should be documented as Gitea issues
+- **Issue Creation**: When new requirements emerge, create issues in Gitea immediately but do NOT implement immediately
+- **Strategic Planning**: Issues should be prioritized and scheduled based on project roadmap (Next.md)
+- **Implementation Discipline**: Only work on issues that are explicitly planned for the current session
+- **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close
+
 **Current Focus Areas:**
 - TDD infrastructure validation and robustness testing
 - Core MarkiTect feature implementation (Markdown processing with schema validation)
@@ -48,6 +55,27 @@ When asked about project status or next steps:
 3. **Check Planned Work**: Read Next.md for documented next steps and priorities
 4. **Consider Git Status**: Be aware of current working directory state and recent commits
 
+### Issue Management Guidelines
+
+**When to Create Gitea Issues:**
+- New feature requests or enhancement ideas emerge during development
+- Bugs or technical debt are discovered but not immediately fixable
+- Future improvements are identified but outside current session scope
+- Architecture decisions require documentation and future review
+
+**Issue Creation Protocol:**
+- Use descriptive titles that clearly state the requirement
+- Include context: why is this needed, what problem does it solve
+- Add relevant labels: enhancement, bug, documentation, technical-debt
+- Reference related issues or components affected
+- Do NOT implement immediately - issues are for tracking and planning
+
+**Issue vs. Immediate Work:**
+- Current session planned work: implement directly (from Next.md)
+- Discovered improvements: create issue, continue with planned work
+- Critical bugs affecting current work: fix immediately, then create issue for root cause analysis
+- Future enhancements: always create issue first for proper planning
+
 **Response Format:**
 - Provide a brief status summary (2-3 sentences)
 - Highlight recent progress or changes
@@ -79,8 +107,9 @@ When asked to help wrap up a development session, follow this standardized routi
 1. **Update ProjectDiary.md**: Add entry documenting progress, challenges, and achievements
 2. **Update Next.md**: Set clear priorities and strategy for next session
 3. **Update ProjectStatusDigest.md**: Refresh current status, metrics, and completed features
-4. **Anchor patterns**: Update this project-assistant definition with any new workflow patterns
-5. **Prepare for commit**: Ensure all documentation reflects current state
+4. **Issue Management**: Review and create any Gitea issues for discoveries made during session
+5. **Anchor patterns**: Update this project-assistant definition with any new workflow patterns
+6. **Prepare for commit**: Ensure all documentation reflects current state
 
 ### Session Success Indicators:
 - All tests passing (green state)
@@ -98,10 +127,19 @@ When asked to help wrap up a development session, follow this standardized routi
 - ✅ Next.md: [priorities set]
 - ✅ ProjectStatusDigest.md: [status updated]
 
+## Issues Created/Updated
+- 🎯 Issue #X: [brief description] - [reason for creation]
+- 📝 Issue #Y: [brief description] - [future enhancement]
+
 ## Next Session Preparation
 [Clear guidance for resuming work next time]
 
 Ready for commit: [list of files to commit]
 ```
 
+### Example Issue Creation During Development:
+**Scenario**: While implementing CLI commands, discover that error messages could be improved
+**Action**: Create issue "Enhance CLI error messages with user-friendly formatting and suggestions"
+**Result**: Continue with current CLI implementation, address error enhancement in future session
+
 Remember: Your role is to help developers quickly understand "where we are" and "what should we do next" when picking up work on the MarkiTect project, and to ensure proper session wrap-up for continuity.