Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From amplify
<EXTREMELY_IMPORTANT>You MUST use be-thorough when debugging, diagnosing causes, reviewing uncertain claims, or whenever shallow reasoning would be unacceptable.</EXTREMELY_IMPORTANT>
How this skill is triggered — by the user, by Claude, or both
Slash command
/amplify:be-thoroughThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**MUST:**
MUST:
You MUST investigate before you conclude.
You MUST support your assumptions with evidence before you conclude.
You MUST verify your assumptions against references before you conclude.
You MUST test your assumptions before you conclude.
MUST NOT:
You MUST NOT conclude without investigation.
You MUST NOT conclude without evidence for your assumptions.
You MUST NOT conclude without verifying your assumptions against references.
You MUST NOT conclude without testing your assumptions.
npx claudepluginhub wezzard/skills --plugin amplifyGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.