Migrate all repos into monorepo context folders
Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)
Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
---
|
||||
description: Review and update the assistant system prompt (docs/assistant_system_prompt.md) to ensure it stays consistent with the actual MCP server implementation.
|
||||
---
|
||||
|
||||
## System Prompt Maintenance
|
||||
|
||||
The file `docs/assistant_system_prompt.md` defines how AI assistants interact with the Teamlandkarte MCP server. It must stay in sync with the actual implementation.
|
||||
|
||||
### What to Check
|
||||
|
||||
1. **Tool inventory**: Every `@mcp.tool()` in `src/teamlandkarte_mcp/mcp_server.py` must be documented in the "Tools and when to use them" section.
|
||||
2. **Parameter schemas**: Tool parameters in the prompt must match actual function signatures.
|
||||
3. **Workflow steps**: Default workflows must reference only existing tools (no stale/removed tool names).
|
||||
4. **Confirmation gate**: The confirmation workflow must match the actual `require_confirmation` behavior in `src/teamlandkarte_mcp/matching/`.
|
||||
5. **Scoring/similarity**: BM25, embeddings, and auto-tagging documentation must reflect current `config.toml.example` options.
|
||||
6. **Consistency with Kiro agent**: `.kiro/agents/teamlandkarte.md` should mirror the system prompt content.
|
||||
|
||||
### Sync Targets
|
||||
|
||||
When updating the system prompt, also update:
|
||||
- `.kiro/agents/teamlandkarte.md` (Kiro agent definition)
|
||||
- `.github/prompts/teamlandkarte-matching-assistant.prompt.md` (Copilot skill)
|
||||
|
||||
### Validation Steps
|
||||
|
||||
1. Read `src/teamlandkarte_mcp/mcp_server.py` — list all `@mcp.tool()` functions
|
||||
2. Compare against the "Tools and when to use them" section in the prompt
|
||||
3. Check for stale references (tools that were removed or renamed)
|
||||
4. Check for missing tools (new tools not yet documented)
|
||||
5. Verify parameter names and types match
|
||||
6. Run `uv run pytest` to confirm nothing is broken
|
||||
Reference in New Issue
Block a user