dt:study

Capture one verified lesson as user-level memory or a personal rule.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/adzcsx2/dev-tools-skills --skill dt-study
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt:study
Source: https://github.com/adzcsx2/dev-tools-skills/tree/main/skills/study
Command: npx skills add https://github.com/adzcsx2/dev-tools-skills --skill dt-study

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of capturing and documenting lessons learned from resolved issues, promoting knowledge retention and avoiding future mistakes.

Core Features & Use Cases

  • Issue Resolution Capture: Quickly document the resolution of technical issues for future reference.
  • User-Level Rule Creation: Generate rules for personal use without affecting project codebases.
  • Use Case: When encountering a bug that has been resolved, use the dt:study skill to create a personal rule that helps you remember the solution.

Quick Start

Run /dt:study followed by a summary of the issue to capture the resolution in your personal memory or rules.

Frequently Asked Questions about dt:study

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

FAQPage Schema
How do I document issue resolution for future knowledge retention?

To document issue resolution for knowledge retention, you capture verified lessons as user-level memory or personal rules without modifying project files. This process requires user confirmation before any external writes are executed.

Can I create personal rules from resolved bugs without modifying project codebases?

Yes, you can create personal rules from resolved bugs without modifying project codebases. The rule capture mechanism generates user-level memory entirely separate from your active project files.

What is the best way to automate user experience learning during project maintenance?

Automating user experience learning during project maintenance involves capturing verified lessons as personal rules. This prevents future mistakes by retaining knowledge of resolved issues without altering existing code.

Does rule capture require manual confirmation before writing to user-level memory?

Yes, rule capture requires manual user confirmation before writing to user-level memory. This ensures you maintain control over any external writes during the issue resolution documentation process.

How do I start issue resolution documentation for a resolved bug?

To start issue resolution documentation, provide a summary of the resolved bug. The system will then capture the verified lesson as a personal rule for future reference and mistake avoidance.