weihung-user-claude

Use when starting project code-improvement work — refactoring, architecture improvement, cleanup of an existing codebase — or when a grilling session should leave docs behind. Runs the interview and records decisions as ADRs and domain terms in CONTEXT.md as they crystallise.

Use when the user requests development work — implementing a feature, debugging an error, designing an approach, or deploying a release. MUST be invoked as the entry point before any implementation, debugging, or design sub-skill.

Use when the user names final QA as the goal — pre-release verification, "上線前驗證 / 最終品質保證".

A relentless interview to sharpen a plan or design.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Use when the user asks to check, audit, or review something thoroughly. Builds a check plan, then verifies each item with the investigating skill.

Use when the user asks to research or investigate a question, claim, or topic in depth. Comprehensive investigation with current information, every claim traceable to a source.

Use when the user asks an explanatory question — what is, how does, why, compare. Builds the user's mental model rather than dumping facts.

Use when completing significant work, resolving a difficult bug, or ending a session. Routes session learnings to user-root (~/.claude/) or project-level components.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.