sharpening-the-knife

Capture valuable techniques and insights discovered during work immediately.

1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/zgagnon/skills --skill sharpening-the-knife
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharpening-the-knife
Source: https://github.com/zgagnon/skills/tree/main/sharpening-the-knife
Command: npx skills add https://github.com/zgagnon/skills --skill sharpening-the-knife

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the loss of valuable techniques, patterns, and insights discovered during work by providing a clear process to capture them immediately, avoiding the "I'll remember this later" trap.

Core Features & Use Cases

  • Immediate Capture: Provides a structured workflow to pause and document useful discoveries as soon as they are recognized.
  • Rationalization Countermeasures: Explicitly addresses common excuses for not documenting (e.g., "too simple," "almost done," "too urgent").
  • Handling Edge Cases: Offers guidance for multiple discoveries, fatigue, and urgent situations.
  • Use Case: While coding, you discover a particularly elegant way to handle error retries. Instead of continuing, you use this skill to pause, document the pattern, and then resume your work with a new, reusable tool.

Quick Start

Pause your current work and use the sharpening-the-knife skill to document a useful pattern you just discovered.

Frequently Asked Questions about sharpening-the-knife

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture development insights and patterns before forgetting them?

To capture development insights before forgetting, you pause your current coding workflow to immediately document the discovered technique, counter rationalizations for deferring, and resume work with a reusable knowledge reference.

What is the best way to document code patterns while working under time pressure?

Documenting code patterns under time pressure requires clear decision rules to pause work, handle urgent constraints, and record the insight using a structured capture mechanism rather than relying on memory.

How does pattern recognition knowledge retention work in fast-paced development environments?

Knowledge retention in fast-paced development works by systematically pausing to document discovered techniques on the spot, preventing knowledge loss when moving rapidly between complex coding tasks.

Why do developers lose valuable techniques and insights during work?

Developers lose valuable techniques because they defer documentation with rationalizations like being too busy or too tired, causing discovered patterns to vanish before they are ever recorded.

Can I use a structured workflow to document multiple discoveries when fatigued?

You can use a structured workflow to document multiple discoveries when fatigued, as it provides specific guidance and countermeasures to handle edge cases like exhaustion and urgency for knowledge capture.

What are the limitations of relying on memory for developer productivity knowledge capture?

Relying on memory for knowledge capture fails because rationalizations for deferring documentation lead to permanent knowledge loss, bypassing the systematic approach required to retain patterns in fast-paced environments.