القائمة
Post-session retrospective — append tagged learnings (with severity) to configured learnings file (default: `learnings.md`)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | lesson |
| description | Post-session retrospective — append tagged learnings (with severity) to configured learnings file (default: `learnings.md`) |
Extract actionable, project-specific learnings from friction encountered in the current session and append them to the configured learnings file (default: learnings.md, reads lessonFilePath from project config when set) with domain and severity tags.
Review the current conversation for these pattern types, ordered by priority:
| Pattern | Signal | Example |
|---|---|---|
| Repeated failure | Same error/approach tried 2+ times | Forgot WITH(NOLOCK) again, same enum serialization bug |
| Troubleshooting spiral | 3+ back-and-forth attempts to fix one issue | 4 tries to fix login fixture timing before finding networkidle |
| Wrong assumption | Approach based on incorrect mental model | Assumed MustAsync runs in same pipeline as sync validators |
| User correction | User had to redirect or correct the agent | "No, use Dapper not EF" or "That's the wrong table" |
| Convention violation | Broke a project convention, had to redo | Missing audit columns, wrong SP naming, hardcoded hex colors |
| Tool/API surprise | Tool or API behaved unexpectedly | git add silently fails with bracket paths in zsh |
| Failed tool use | Tool invoked incorrectly, skipped, or retried unnecessarily | Used Edit before Read, used Bash grep instead of Grep tool, wrong sqlcmd flag syntax |
| Process shortcut | Skipped a required workflow step | Claimed completion without running tests, made design decision without AskUserQuestion, skipped EnterPlanMode for 3+ file change |
Each learning gets:
YYYY-MM-DD[backend], [frontend], [db], [e2e], [workflow], [tooling], [shell], [process]
[process] — tool discipline violations, skipped workflow steps, wrong-sequence tool use[one-off], [recurring], [spiral]
[one-off] — happened once, but non-obvious enough to record[recurring] — same mistake or pattern seen before (check existing entries in the configured learnings file)[spiral] — required 3+ attempts or a long back-and-forth to resolveQuality bar: project-specific, actionable, non-obvious, 1-2 sentences max.
For [recurring] entries: read the configured learnings file to check if a similar entry already exists. If so, append a count bump like (x3) to the new entry to track frequency.
learnings.md)Silently append — no AskUserQuestion, no multi-file routing. Just append.
Entry format:
- **2026-02-23** [backend] [spiral] Login fixture timing — 4 attempts before finding networkidle fix
- **2026-02-23** [db] [recurring] (x3) Forgot WITH(NOLOCK) on SELECT query
- **2026-02-23** [tooling] [one-off] SP parameter order mismatch caused silent null
- **2026-02-23** [process] [recurring] (x2) Used Edit before Read — always Read the file first, even for "obvious" edits
- **2026-02-23** [process] [one-off] Skipped EnterPlanMode for 4-file change — caused rework; use plan mode for 3+ files
Mistake entries must include the correction — record not just what failed, but what to do instead next time.
[recurring] tagging — quickly scan existing entries in the configured learnings file (the only file read)[process] entries must include the correction — "Used Edit before Read" is incomplete; "Used Edit before Read — always Read first to confirm line content" is validAutomates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Save current session state to a handover document for seamless continuation in a new session. Invoke manually or triggered automatically when context window reaches 85%.
Use when the user wants to delegate a task to OpenAI Codex CLI, get a second opinion, or run codex review on changes
Configurable 9-phase feature development workflow enforcer (Phase 0 Context Setup → Phase 8 Approval & Commit). Delegates planning to OpenSpec (proposal→specs→design→tasks) and enhances execution with superpowers skills (TDD, subagent-driven-development, worktrees, verification). Auto-validates phase transitions, manages state via context.md, and orchestrates specialized agents. Use when user says "start feature" or "resume feature", mentions implementing/building/creating a feature, needs structured development process, references TDD or test-driven development, asks about feature planning or implementation phases, references 9-phase workflow or mentions "Phase 1" or "Planning phase", needs approval gates or phase validation, or asks "how do I start a feature" or "what's the development workflow".
Structured E2E test troubleshooting using the 6-layer diagnostic ladder (Frontend → API → SP/Schema → Infra → CI/CD). Use when any E2E test fails, UI doesn't render, auth drops, unexpected status codes, CI passes locally but fails in pipeline, or any test failure where the root cause is unclear. Routes to the correct read-only diagnostic agent based on the symptom, walks the sequential ladder with [EVIDENCE]/[HANDOFF]/[ROOT-CAUSE] taxonomy, and enforces the Fix Gate (no action before root cause confirmed).
SQL Server database development specialist. Use when creating tables, stored procedures, migrations, or troubleshooting SQL Server/Docker issues. Reads project tech-stack directory conventions if present; falls back to generic SQL Server patterns (UNIQUEIDENTIFIER PKs, CreatedOn/ModifiedOn with GETUTCDATE(), no FK constraints, WITH(NOLOCK), SARG optimization, stored proc naming {Product}_{Module}_{Function}_{Date}).