# Improve System

> Improve System

- Skill: `abed-zahed/improve-system` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add abed-zahed/improve-system`
- Raw SKILL.md: https://api.skillmd.com/api/skills/abed-zahed/improve-system/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Abed-Zahed (https://skillmd.com/u/abed-zahed)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/abed-zahed/improve-system

---


# /improve-system

## Auto-trigger rule
Run this skill automatically when the user says:
- "review your work" / "double check" / "improve the process" → **skill-review**
- "I just learned" / "we should remember" / "that worked well" → **experience**
- "what did we miss" / "review our sessions" / "mine past sessions" → **historical-review**
- "find duplicates" / "clean up notes" / "audit memory" → **audit**
- "what are we missing" / "fill in the gaps" / "foundational" → **foundation**

If mode is unclear from context, ask: *"Which mode? audit / skill-review / experience / historical-review / foundation"*

---

## Mode: audit
Find stale, conflicting, or duplicate notes.

1. Scan `C:\Users\Administrator\.claude\projects\d--Job-hunter\memory\` for:
   - Duplicate topics across files
   - Contradictions between files
   - Notes older than 30 days with time-sensitive claims (dates, job statuses)
   - Memory entries that reference code/files that no longer exist
2. Report findings as a list: **keep / merge / delete / update**
3. Apply changes with confirmation

---

## Mode: skill-review
Improve a specific skill based on recent back-and-forth.

1. Identify which skill underperformed or succeeded in the recent conversation
2. Read the skill's `SKILL.md`
3. Review conversation for: gaps, repeated corrections, what worked
4. Propose specific edits (show before/after)
5. Apply with confirmation

---

## Mode: experience
Capture a story, win, or lesson just shared.

1. Extract from what was shared:
   - What happened (situation)
   - What worked / what failed
   - The lesson or principle
   - Who was involved
2. Format as a memory entry with the standard frontmatter
3. Route to `knowledge/experiences/` or relevant project memory
4. Add [[wikilinks]] to related concepts

---

## Mode: historical-review
Mine recent Claude Code sessions for missed learnings.

1. Review recent git commits, conversation patterns, and corrections in this session
2. Identify:
   - Repeated mistakes that should be in memory
   - Approaches that worked well but weren't saved
   - Decisions made that future sessions would benefit from knowing
3. Propose new memory entries or skill updates for each finding
4. Apply confirmed items

---

## Mode: foundation
Fill in missing foundational content for a project or identity.

Check for and fill in missing entries across these pillars:
- **Brand voice** — how the user writes and speaks
- **Target audience** — who they're talking to
- **Offers/products** — what they're selling or building
- **Core processes** — how they do their key workflows
- **Key people** — team, advisors, frequent collaborators

For each missing item: ask 3-5 targeted questions, save answers to `knowledge/foundation/`.
This content feeds `/ask-the-board` and `/internal-focus-group`.