From 3552cdd269c194e337993fe3ef9f4f1eb71f8880 Mon Sep 17 00:00:00 2001 From: moilanik Date: Sat, 18 Apr 2026 07:06:38 +0300 Subject: [PATCH] =?UTF-8?q?keskityt=C3=A4=C3=A4n=20yhteen=20teht=C3=A4v?= =?UTF-8?q?=C3=A4=C3=A4n=20s=C3=A4=C3=A4nt=C3=B6?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .ai/skills/root-skill/SKILL.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.ai/skills/root-skill/SKILL.md b/.ai/skills/root-skill/SKILL.md index b652c3c..bfe9150 100644 --- a/.ai/skills/root-skill/SKILL.md +++ b/.ai/skills/root-skill/SKILL.md @@ -26,8 +26,16 @@ To prevent premature execution, you operate as a State Machine. You must explici - **CRITICAL PRE-EXECUTION:** Before any file edits, mechanically `read_file` the relevant skill files (e.g., `clean-code`, `helm`). - **ACTIVE SKILL ECHO:** Immediately after reading skills, output a section `### Active Skills:` summarizing the 2-3 most critical rules. - **ALLOWED:** You may use file modification tools and generate concrete code. + - **RETURN TO PLAN:** Once execution is finished, your VERY NEXT response MUST transition back to `STATE: PLAN`. +## 🔒 TASK LOCK & CONTEXT MANAGEMENT +1. **Strict Monotasking:** Focus only on the current task. Do not plan the next step until the current one is confirmed. +2. **The "Parking Lot":** If new ideas emerge mid-flow, list them under a `💡 IDEAS / BACKLOG` section at the end of the response. Do not act on them yet. +3. **Mandatory Confirmation:** After every implementation, you MUST stop and ask: + > "Is this task completed to your satisfaction?" + Do not start new work until the user confirms. + ## 🚫 GIT HARD RULES (Reference) See complete Git rules: `.ai/skills/git/SKILL.md`