write-engineering-lessons-article
Write Engineering Lessons Article
What this skill is for
Turn a real engineering incident into a publishable article that a skeptical engineer would find credible reading it cold. The output is an executive summary, a main body of 900–1500 words, and an appendix of verbatim code excerpts with file-path and revision attribution.
This skill does not run on a generic topic. It runs on a specific past incident the user can point at.
Minimum viable evidence
Before drafting anything, confirm you have all three of:
- A concrete failing input, trace, metric, or reproduction
- The commit, PR, or diff that changed behavior to fix it
- Evidence the fix held — a test, an eval run, a log, a dashboard, or explicit user confirmation
If any is missing, stop and ask the user for it. Do not infer stages from vibes. Do not reconstruct a failure that is not evidenced.
Deliverables
More from wiseiodev/skills
code-principles
Software engineering principles for code review, planning validation, and learning. Covers SOLID, DRY, YAGNI, design heuristics, testing, API design, architecture patterns, and React best practices. Use when reviewing code, validating plans/specs, injecting review criteria into council sessions, or when user asks about a specific principle. Triggers on "principles", "code review checklist", "SOLID", "DRY", "design heuristics", "review criteria", "best practices", or any named principle like "Law of Demeter", "Liskov", "YAGNI", etc.
11gt
Create Graphite stacked PRs from staged git changes. Use when user says "/gt", "create a PR", "submit PR", or wants to commit and create a pull request using Graphite. Optionally accepts a Linear issue ID (e.g., "/gt A-35") to auto-close issues on merge.
4graphite
Comprehensive Graphite CLI for stacked PRs. Triggers on stack management, gt commands, rebasing/syncing, branch navigation (up/down/top/bottom), merge conflicts, reorganizing branches, recovery (undo/abort), teammate stacks. For simple PR creation, use gt skill instead.
3review-council
Send a document (plan, spec, PRD, ADR, code) to a review council of 2+ AI agents (Claude Code + Codex CLI by default, optionally Gemini CLI and Copilot CLI) for independent parallel review. Synthesizes feedback, auto-revises the document, and re-reviews if council members had high variance. Use when wanting multi-agent review, "review council", peer review from multiple AIs, or validating plans/specs/code before finalizing.
3dispatch-cli-agent
Dispatch work to an external CLI agent (Claude Code, Codex CLI, Gemini CLI, or GitHub Copilot CLI) by writing a prompt and launching the agent via background Bash tasks. Use when orchestrating multi-agent workflows, sending work for external review, parallel task fan-out, or the "review council" pattern where multiple agents review a plan in parallel. Triggers on words like "dispatch", "fan-out", "review council", "send to agent", "launch agent", or when orchestrating parallel CLI agent work.
2work-log
Log accomplishments, solved problems, learnings, and milestones to Obsidian daily notes via the Obsidian CLI. Also answers questions about the Obsidian CLI. Triggers on "/log", "log accomplishment", "log what I did", "work log", "obsidian cli", "daily note", or when user wants to record something noteworthy they did.
1