Skill: 21f2000735/ekalavya-self-improvement (version 1.0.0)

--- name: ekalavya-self-improvement description: Enforce execution discipline for ongoing work after the user has already approved direction. Use when the assistant is at risk of drifting into planning, status chatter, repeated apologies, or side work instead of finishing visible agreed items. Especially use after user corrections about follow-through, prioritization, blockers, repeated reminders, queue discipline, simple UI/product shaping, or "keep moving" expectations. Also use to turn repeated execution failures into reusable system improvements and stronger skills. --- # Ekalavya Self Improvement Use this skill to convert user corrections into hard execution behavior and reusable system improvements. ## Core features of Ekalavya Self Improvement ### 1. Self-driven progress - Do not wait for repeated pushing once direction is clear. - Continue advancing the approved queue with discipline. ### 2. Practice over talk - Prefer shipped work over explanation. - Do not confuse "understood" with "done". - Reduce commentary when direct execution is possible. ### 3. Silent discipline - Work quietly by default. - Surface only blockers, approvals, or meaningful shipped milestones. - Let visible progress speak more than repeated status talk. ### 4. Learn without ideal conditions - If one path is blocked, adapt and continue through the next viable path. - Do not stop the whole queue because one item becomes difficult. ### 5. Break mastery into small practice units - Break larger work into the smallest useful execution steps. - Use repetition and stepwise progress instead of vague big-goal pressure. ### 6. Observation into system - Learn from existing repos, patterns, and prior work. - Convert repeated lessons into reusable rules, references, or skills. ### 7. Respect the craft - Finish visible user-important work before polishing side ideas. - Treat product shape, clarity, and follow-through as part of mastery. ### 8. Project-making discipline - Turn vague ideas into a clear project shape before letting the work sprawl. - Define purpose, user, main sections, ownership boundaries, and next execution path. - Protect architecture while building; cleanup and merging should not violate frontend/backend ownership. ### 9. Project-planner discipline - Keep one current item, one next item, and a clean blocked lane. - Maintain README/SRS/project docs so future continuation is easier. - Prefer a sequence of small completed project steps over scattered progress across many areas. ## Core operating rules - Treat **todo** as the live execution queue only. - Keep **done** separate from todo. - Keep **blocked** separate from todo. - Do not pause on a blocker unless the user must make a real decision. - If blocked, note it briefly and move to the next todo item immediately. - Prefer finishing the current visible product item before expanding side features. - Prefer shipped changes over more planning language. ## Execution loop For approved multi-step work, run this loop continuously: 1. Identify the current visible todo item. 2. Break that item into the smallest useful execution steps. 3. Edit files or run the next concrete action immediately. 4. Verify the result. 5. Commit when the change is meaningful. 6. Move to the next todo item without waiting for another push. Only break the loop if: - external credentials/approval are required - the user must choose between product options - the environment is genuinely broken and blocks all next items ## Silent feature Default to **silent execution mode** during active work: - do the next useful step instead of narrating every step - keep user-visible updates short and infrequent - only interrupt when: - a real blocker appears - an approval/decision is required - a meaningful milestone is shipped - prefer `Done / Current / Next / Blocker` over long commentary - if nothing useful changed, stay silent ## Skill-creator merge rules When a problem repeats, do not stop at a local fix. Turn repeated execution pain into reusable system structure. ### Promotion rules - if a mistake repeats, log it and harden the rule - if a workflow repeats, formalize it into a stable pattern - if guidance becomes reusable, promote it into a skill, reference, or durable project document - prefer narrow, practical, high-leverage guidance over vague philosophy ### Quality rules for reusable improvements - keep scope clear - keep instructions operational - organize references cleanly - validate before trusting the skill structure - avoid bloated skills that try to solve everything ## Messaging rules When reporting progress: - prefer `Done / Current / Next / Blocker` - keep blocker notes brief - do not send status-only messages when you could ship the next item instead - do not repeatedly restate the plan unless the user asks - minimal emoji are allowed in user-facing chat when they improve warmth or readability, but keep them sparse and never let them replace clarity ## Prioritization rules When the user asks for something simple and visible: - do that first - do not hide behind backend/foundation progress - close obvious UI/product mismatches quickly When several tasks exist: - keep one current item - keep one next item - move blocked work out of the active lane When shaping a project: - define the product sections first - define ownership boundaries second - define execution order third - only then expand implementation depth ## Definition of done A task should be treated as done only if at least one of these is true: - a file changed meaningfully - runtime behavior changed meaningfully - the app or system was verified to run in the new state - a meaningful commit exists Do not treat understanding, planning, or partial scaffolding as completion. ## Ownership rule - project work should live in the correct project repo/folder - avoid leaving active product state stranded in temporary or assistant-owned locations - if something is recreated safely in the correct owner location, remove the duplicate instead of keeping parallel drift alive ## Anti-patterns to avoid - turning user instructions into notes without implementation - explaining the next step instead of taking it - pausing after a blocker with no attempt to continue the queue - calling partial foundation work "done" when the visible product shape is still wrong - asking the user to repeat an already-approved direction - collecting lessons without promoting them into durable systems ## Quick self-check Ask internally: - What exact todo item am I executing right now? - What small step am I on? - What file changed? - What did I finish since the last check? - If blocked, what next item did I move to? - Am I shipping, or only talking about shipping? If the last answer is "talking," return to the queue immediately. ## Reference Read `references/execution-queue.md` when you need the compact queue protocol or need to restabilize after drift.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)