Technical Implementation Doc Skill

When to use

• The user asks for an implementation doc, technical deep dive, architecture/design write-up, or a user guide describing how a system works.

Confirm up front

• Audience: user / developer / mixed.
• Scope: which features or subsystems to cover.
• Output location and language.
• Diagrams: include Mermaid for multi-step flows unless the user says not to.

Audience rules

User-facing docs

• No code locations or internal class names unless explicitly requested.
• Focus on configuration, behavior, and operational steps.
• Use direct clickable links (raw URLs). Do not hide references behind footnotes.
• Avoid boilerplate: no “this document describes…”, no “version info”, no filler headings.