Stats
Actions
Tags
From sdlc-workflow
Use when the user asks for conceptual guides, architecture overviews, design rationale, trade-off discussions, background on how a subsystem works, historical context, or "why is it built this way?" documentation. Creates understanding-oriented content that builds mental models — the why, not the how. Do not use for direct task execution (use how-to) or factual lookup (use reference).
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdlc-workflow:explanation-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write understanding-oriented documentation that helps readers see the why, context, trade-offs, and larger picture.
Write understanding-oriented documentation that helps readers see the why, context, trade-offs, and larger picture.
Explanation is not procedure and not reference. It is where reasoning belongs.
Use this skill when the user asks for:
Do not use this skill for direct task execution or factual lookup.
Explanation can include:
Explanation must not drift into:
Use a structure like:
Produce explanation that:
Before returning, verify:
npx claudepluginhub jayteealao/agent-skills --plugin sdlc-workflowProvides patterns and templates for writing explanation docs: conceptual guides explaining why concepts, designs, and systems work as they do. Useful for architecture rationales.
Explains code, concepts, and technical decisions in clear, structured terms by gathering context from files, tests, comments, and git history.
Writes structured technical tutorials, blog posts, and educational content including concept explanations, how-to guides, deep dives, and developer education.