---
name: Feature-Session Workflow
description: Trigger and action rules for loading feature docs at session start
type: feedback
---

## Feature-Session Workflow

**TRIGGER** (any phrasing at session start that references a feature/topic):
- `Feature [topic]`
- `zum Feature [topic]`
- `wir arbeiten an [topic]`
- any similar phrasing indicating a feature or topic context

**ACTION — always execute immediately on trigger:**
1. Look for `docs/feature-[topic].md` in project root (case-insensitive match)
2. If found: read it, confirm context loaded, summarize key points briefly
3. If not found: inform user that no feature doc exists yet, suggest creating one

**CRITICAL: Do NOT wait to be explicitly asked. Load the feature doc proactively.**

When user says `aktualisiere deine Feature-Beschreibung` at session end:
1. Locate the relevant `docs/feature-[topic].md`
2. Update it with key insights, decisions, and findings from the current session
3. Keep it structured: Goal, Context, Key Decisions, Open Questions, Progress

File naming: `docs/feature-[featureName].md` (camelCase featureName, e.g. `feature-jobSystem.md`)

**CRITICAL**: When creating a new feature doc, the filename MUST start with `feature-`.
Never create docs like `jobSystem.md` or `job-system.md` — always `feature-jobSystem.md`.