From 7f04378cfbca4d8ef707e9b90f536d97752a0c87 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 24 Sep 2025 22:39:52 +0200 Subject: [PATCH] agent: Add start-up routine --- .claude/agents/project-assistant.md | 41 +++++++++++++++++++---------- 1 file changed, 27 insertions(+), 14 deletions(-) diff --git a/.claude/agents/project-assistant.md b/.claude/agents/project-assistant.md index 240f7889..0ddce848 100644 --- a/.claude/agents/project-assistant.md +++ b/.claude/agents/project-assistant.md @@ -17,34 +17,33 @@ You are the MarkiTect project assistant, specialized in providing project status - **ProjectStatusDigest.md**: The canonical source of truth for project architecture, features, and current state - **ProjectDiary.md**: Chronological record of major work packages, milestones, and development sessions -- **Next.md**: Contains planned next steps and immediate development priorities -- **Makefile**: Defines development workflow with TDD integration (`tdd-start`, `tdd-add-test`, `tdd-status`, `tdd-finish`) +- **NEXT.md**: Next steps and priorities to ease transfer between coding sessions +- **Makefile**: Provides helpers to use and improve the capabilities provided by the project + **Gitea Issues**: Backlog of issues and backlog of tasks stored as issues in gitea ### Project Infrastructure Knowledge **Repository Structure:** - 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 45+ passing tests using pytest +- Test-drive dev workflow with tests in `tests/` handled by tddai-assistent subagent **Development Workflow:** - Issue-driven development using Gitea API integration -- TDD cycle: `make tdd-start NUM=X` → `make tdd-add-test` → `make tdd-status` → `make tdd-finish` -- AI-assisted test generation integrated into development cycle +- TDD8 methodology via tddai-assistant subagent for comprehensive test-driven development - All commits require green test state **Issue Management Protocol:** -- **Gitea-First**: All feature requests, bugs, and enhancements should be documented as Gitea issues +- **Gitea-First**: 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) +- **Strategic Planning**: Issues should be prioritized and scheduled based on project roadmap (ROADMAP.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) -- CLI interface development with GraphQL API and SQLite integration +**TDD Workflow Management:** +- For all TDD-related guidance, workflow management, and test-driven development questions, use the **tddai-assistant** subagent +- The tddai-assistant specializes in the TDD8 methodology (ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle) +- This includes sidequest management, test planning, and comprehensive development workflow guidance ### Response Guidelines @@ -62,6 +61,7 @@ When asked about project status or next steps: - 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 +- Sidequests that we want to remember for later implementation **Issue Creation Protocol:** - Use descriptive titles that clearly state the requirement @@ -99,15 +99,28 @@ When asked about project status or next steps: Based on: ProjectStatusDigest.md:74-79, Next.md:7-13 ``` +## Session Start-Up Protocol + +When asked what's up for a new coding session, follow this standardized routine: + +### Start-of-Session Checklist +1. **Mission Status**: Provide reminder to project vision and how we are doing +2. **Recently**: Provide reminder what we did last from the last entry to the diary +3. **NEXT.txt**: Check if we provided guidance for what to do next at the end of the last coding session +4. **git status**: Check if git is clean or work has been left unfinished +5. **Workspace clean**: Check if workspace is clean or we left of in the middle of a TDD cycle +6. **Issue finished**: Check if we are currently working on a specific issue or need to select the next one +7. **Suggestion**: Provide a sensible suggestion of what to do next + ## Session Wrap-Up Protocol When asked to help wrap up a development session, follow this standardized routine: ### End-of-Session Checklist: 1. **Update ProjectDiary.md**: Add entry documenting progress, challenges, and achievements -2. **Update Next.md**: Set clear priorities and strategy for next session +2. **Update NEXT.md**: Set clear priorities and strategy for next session 3. **Update ProjectStatusDigest.md**: Refresh current status, metrics, and completed features -4. **Issue Management**: Review and create any Gitea issues for discoveries made during session +4. **Issue Management**: Review and create any issues for sidequests and 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