expert-solution-workflow

Routes problems to reusable expert-team or solution assets for lookup and capture.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill expert-solution-workflow-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expert-solution-workflow
Source: https://github.com/HACK-WU/skills/tree/main/skills/expert-solution-workflow
Command: npx skills add https://github.com/HACK-WU/skills --skill expert-solution-workflow-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams repeatedly re-diagnose the same module issues and re-solve the same technical problems because knowledge is never captured or retrieved. This Skill routes every encountered or solved problem to the right reusable asset type so prior work is found and new knowledge is preserved. ## Core Features & Use Cases - Problem-type routing: Classifies issues as business-module problems (routed to expert-lookup) or concrete technical problems (routed to solution-lookup) before investigation begins. - Capture routing after resolution: Directs reproducible fixes to solution-capture, reusable module knowledge to expert-team, and one-line facts to project memory. - Distinction between asset types: Treats expert teams as domain maps (contract layers C0-C4 plus implementation navigation) and solutions as step-by-step recipes for specific errors or configurations. - Use Case: After fixing a recurring deployment error, the Skill evaluates whether the fix is non-trivial and reproducible, then triggers solution-capture to store the steps and indexes them for future retrieval. ## Quick Start Ask the agent to check whether an existing expert team or solution covers the current problem before investigating, and to capture the fix afterward if it is reusable.

Frequently Asked Questions about expert-solution-workflow

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

FAQPage Schema
How do I reuse prior solutions when debugging a recurring error?

Classify the issue as a concrete technical problem, then invoke solution-lookup to search stored solution recipes. If a matching solution exists, follow its documented steps and cautions directly instead of re-diagnosing from scratch.

What is the difference between an expert team and a solution asset?

An expert team is a domain map covering a business module's contracts and implementation, used for navigation while you still read code. A solution is a step-by-step recipe for one specific reproducible problem, executed directly without re-reasoning.

When should I capture a fix as a reusable solution?

Capture it when the resolution was non-trivial: three or more steps, required documentation lookup or trial and error, is reproducible, or involves non-obvious tooling pitfalls. Trivial one-line fixes and one-off issues are skipped.

When should I skip looking up experts or solutions?

Skip expert-lookup when the problem is unrelated to any specific module or the user asks to read code directly. Skip solution-lookup for trivially solvable problems, and skip capture when an identical solution already exists.

Can this workflow handle cross-domain tasks spanning multiple modules?

Yes, cross-domain tasks load up to three expert teams collaboratively, combining their contract-layer knowledge to navigate across module boundaries before reading source code.