Lars
87f258be38
All checks were successful
Deploy Development / deploy (push) Successful in 42s
Test Suite / pytest-backend (push) Successful in 43s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 14s
Test Suite / k6 /health Baseline (push) Successful in 34s
Test Suite / playwright-tests (push) Successful in 1m15s
- Introduced `roadmap_qa_mode` to manage QA behavior based on roadmap-first logic, improving gap detection between major steps. - Updated `detect_path_gaps` to skip gaps for roadmap-planned neighbor pairs, enhancing the accuracy of path assessments. - Added new helper function `is_roadmap_planned_neighbor_pair` to facilitate roadmap neighbor checks. - Updated relevant tests to validate new functionality and ensure robustness. - Incremented application version to 0.8.209 to reflect these changes.
89 lines
3.6 KiB
Markdown
89 lines
3.6 KiB
Markdown
# Planungs-KI — Produkt-Roadmap
|
||
|
||
**Stand:** 2026-06-07
|
||
**App-Version:** ab **0.8.204** — maßgeblich `backend/version.py`
|
||
|
||
Diese Roadmap ergänzt die **Architektur-Refaktor-Roadmap** (`UMSETZUNGSPLAN_ROADMAP.md`) und gilt **nur für KI-gestützte Trainingsplanungsunterstützung**.
|
||
|
||
**Leit-Spec:** `.claude/docs/working/PLANNING_PROGRESSION_ROADMAP_SPEC.md`
|
||
|
||
---
|
||
|
||
## Strategische Entscheidung (verbindlich)
|
||
|
||
1. **Progressionsgraph:** Planung **vom Ziel rückwärts** (Roadmap-first), nicht Bibliothek-first.
|
||
2. **Keine Gruppenanalyse** im Graphen — Kontext = Zieltext, Thema, Schrittanzahl, optional Graph-Kanten.
|
||
3. **Trainingsplanung** (Einheit, Rahmen, Abschnitt): eigene Pipeline später, **mit** Gruppenkontext — siehe `AI_PLANNING_KI_MULTISTAGE_FORECAST.md` S0–S4.
|
||
4. **Orchestrierung:** Workflow-**lite** jetzt (`planning_progression_roadmap.py`); Mitai Workflow-Engine **später**, wenn 2–3 Pipelines stabil sind.
|
||
|
||
---
|
||
|
||
## Phasen-Übersicht
|
||
|
||
| Phase | Domäne | Kurzbeschreibung | Status |
|
||
|-------|--------|------------------|--------|
|
||
| P0–P2 | Übungssuche | Kontext-Pack, Hybrid-Score, LLM-Rerank | ✅ |
|
||
| A–C2 | Übungssuche | Voll-Library, Graph, Varianten | ✅ |
|
||
| C3 | Progressionsgraph | Pfad-Builder (retrieval-first) | ✅ |
|
||
| E–E3 | Progressionsgraph | Semantik, QA, Lücken-Angebote | ✅ |
|
||
| **F0–F1** | Progressionsgraph | Roadmap-Pipeline Scaffold + API-Preview | 🔄 **0.8.204** |
|
||
| **F2–F4** | Progressionsgraph | LLM Roadmap, roadmap-first Retrieval, UI Review | 🔲 |
|
||
| D | Übungs-Neuanlage | `planning_context` an `suggestExerciseAi` | ✅ **0.8.208** |
|
||
| G | Trainingsplanung | Kontext-Pack Gruppe/Historie, S0–S4 | 🔲 |
|
||
| H | Plattform | Mitai-Workflow-Engine (optional) | 🔲 Backlog |
|
||
|
||
---
|
||
|
||
## Phase F — Progressions-Roadmap (aktiver Fokus)
|
||
|
||
### F0 — Foundation (0.8.204)
|
||
|
||
- [x] Spec `PLANNING_PROGRESSION_ROADMAP_SPEC.md`
|
||
- [x] Modul `planning_progression_roadmap.py` (Pydantic, Pipeline-Skeleton)
|
||
- [x] Migration **078** Prompt-Slugs (Zielanalyse, Roadmap)
|
||
- [x] API: `include_roadmap_preview` auf `progression-path-suggest`
|
||
- [x] Doku: HANDOVER, PLANNING_EXERCISE_SUGGEST_CONTEXT, MULTISTAGE_FORECAST
|
||
|
||
### F1 — Deterministische Roadmap
|
||
|
||
- [x] Phase A aus Semantic Brief
|
||
- [x] Phase B: `micro_objectives` aus `development_arc` + Konsolidierung auf N
|
||
- [x] Phase C: heuristische `stage_specs`
|
||
- [ ] pytest für Konsolidierung
|
||
|
||
### F2 — LLM Roadmap (0.8.205)
|
||
|
||
- [x] Prompts **078/079** in `ai_prompts` — Code nur Slugs (`PROMPT_SLUG_*`)
|
||
- [x] `include_llm_roadmap` + `load_and_render_ai_prompt` + JSON-Validierung
|
||
- [x] Deterministischer Fallback wenn Prompt/OpenRouter fehlt
|
||
- [ ] Response/UI: genutzte `prompt_slugs` sichtbar machen (Admin-Hinweis)
|
||
|
||
### F3 — roadmap-first (0.8.206)
|
||
|
||
- [x] Retrieval pro `major_step` + `stage_spec` statt iterativem Pfad-Bau
|
||
- [x] Gap-Angebote für unbesetzte Roadmap-Stufen (`roadmap_unfilled`)
|
||
- [x] QA/Lücken an Roadmap gekoppelt (`roadmap_first_lite`: keine Brücken/Reorder zwischen Major Steps)
|
||
|
||
### F4 — UI (0.8.207)
|
||
|
||
- [x] Roadmap-Review im `ExerciseProgressionPathBuilder`
|
||
- [x] Major Steps editierbar (Phase, Lernziel, Reihenfolge) vor Übungs-Match
|
||
- [x] API `roadmap_only` + `roadmap_override`
|
||
|
||
---
|
||
|
||
## Abhängigkeiten
|
||
|
||
| Von | Nach | Hinweis |
|
||
|-----|------|---------|
|
||
| F2 | Enrichment / Skills | Bessere Roadmap bei technikspezifischen Skills |
|
||
| F3 | F2 | LLM-Roadmap oder stabile heuristische B |
|
||
| G | F4 | Trainingsplanung kann Roadmap aus Graph referenzieren |
|
||
| H | G + F4 | Workflow-Engine lohnt bei verzweigten Planungsflows |
|
||
|
||
---
|
||
|
||
## Pflege
|
||
|
||
Bei Abschluss einer Teilphase: diese Datei, `HANDOVER.md` §2.8, `PLANNING_EXERCISE_SUGGEST_CONTEXT.md` §24, Changelog in `version.py`.
|