Adds reverse engineering docs and adds new aidlc feature for front-end development

2026-06-16 23:25:22 +02:00
parent 95d986790e
commit 73025c5a84
15 changed files with 994 additions and 0 deletions
@@ -0,0 +1,73 @@
+# Gap Report: Language Preference Not Asked Per Feature
+
+**Gap ID**: gap-001  
+**Reported**: 2026-06-16  
+**Reporter**: User (via cms-frontend workflow session)  
+**Skill affected**: `aidlc-workflow`  
+**Rule file affected**: `.aidlc-rule-details/inception/workspace-detection.md`
+
+---
+
+## Problem Description
+
+The `aidlc-workflow` skill currently asks for language preference **only once** at the start of a **brand new workspace** (when no `active-features.md` or legacy `aidlc-state.md` exists). This is defined in **Step 2.5** of `workspace-detection.md`:
+
+> **Step 2.5: Ask Language Preference (New Workspace Only)**
+> Ask this question **once**, at the start of a brand new workspace (no `active-features.md`, no legacy `aidlc-state.md`).
+
+### Observed Behavior
+When a user starts a **new feature** in an existing multi-feature workspace (where `active-features.md` already exists), the language preference question is **skipped** and the default (English documentation) is used without consulting the user.
+
+### Expected Behavior
+The language preference should be asked **for each new feature** being started, not only on workspace initialization. Each feature can independently have its own language configuration stored in its `aidlc-state.md`.
+
+---
+
+## Impact
+
+- Users are not given the opportunity to choose documentation language when adding features to an existing workspace
+- The default (English) is silently applied without user consent
+- The `Language Configuration` in `aidlc-state.md` is set without user input
+
+---
+
+## Suggested Fix
+
+Update `workspace-detection.md` **Step 2.5** to trigger on **new feature creation** rather than only on new workspace initialization:
+
+**Current behavior**:
+- Step 2.5 fires only when NO `active-features.md` exists (brand new workspace)
+
+**Desired behavior**:
+- Step 2.5 fires when creating **any new feature** (i.e., after Step 4b — Create Feature Directory Structure), regardless of whether the workspace is new or existing
+
+**Implementation hint**:
+- Move/expand the language preference question trigger from "new workspace only" to "new feature only"
+- The existing feature's language config (if resuming) should be read from `aidlc-state.md` without asking again
+- The question should be presented BEFORE creating the feature's `aidlc-state.md`, or immediately after the directory structure is created, so the answer can be stored correctly
+
+---
+
+## Related Files
+
+- Skill: `C:\Users\Bryan\.junie\skills\aidlc-workflow\`
+- Rule file: `.aidlc-rule-details/inception/workspace-detection.md` — Step 2.5
+- State file template: Step 4c in `workspace-detection.md` — `## Language Configuration` section
+
+---
+
+## Workaround (for current session)
+
+The cms-frontend feature in `K:\Development\Projects\SlpModularCms` was created with the default English documentation language. If the user wants a different language, manually update:
+
+`aidlc-docs/features/cms-frontend/aidlc-state.md` → `## Language Configuration`
+
+---
+
+## Acceptance Criteria for Fix
+
+- [ ] Starting a NEW feature in an existing workspace triggers the language preference question
+- [ ] Resuming an EXISTING feature does NOT ask the language question again (read from aidlc-state.md)
+- [ ] The language preference is stored in the feature's `aidlc-state.md` under `## Language Configuration`
+- [ ] Both the SKILL.md and `workspace-detection.md` rule file are updated consistently
+- [ ] The `common/session-continuity.md` On Resume instruction is verified to still correctly read from state (no change needed there)