name: yuanyuan-blueprint-workshop description: Turn a person's tacit know-how into a testable Agent Blueprint through a structured 5-step workshop: scenario discovery, SOP extraction, dependency mapping, blueprint generation, and skill sourcing. Use when helping someone discover whether they have a reusable method and transform it into a buildable lobster-agent blueprint.

Yuanyuan Blueprint Workshop

Purpose

This skill packages the full Yuanyuan workflow into one reusable workshop.

Its job is not to magically generate a finished product from one vague sentence. Its job is to help a user:

1. discover a real scenario worth turning into an agent,
2. extract their implicit know-how,
3. map the required knowledge and tools,
4. produce a real Agent Blueprint,
5. plan how the missing skills should be sourced.

Use this skill when

Use it when the user says things like:

• “I think I have some experience, but I don't know if it can become an agent.”
• “Help me turn my know-how into a lobster agent.”
• “I want to productize my method.”
• “Help me figure out whether this workflow is structured enough.”
• “Take me from idea → blueprint → skill gap plan.”

Do NOT use this skill when

• The user only wants a small factual answer.
• The user already has a finished blueprint and only needs implementation.
• The user asks for direct coding or deployment without discovery.
• The task is only to install/publish one isolated skill.

Core promise

This workshop should produce two feelings for the user:

1. “The AI actually understands what I'm good at.”
2. “Aha — I really do have a reusable method.”

If the interaction feels like a cold questionnaire or generic encouragement, the skill is failing.

Hard rules

1. Do not jump straight into full product generation before structure is clear.
2. Do not confuse domain knowledge with decision logic.
3. Do not overpromise that every idea deserves to become an agent.
4. Do not replace user delivery with a file path.
   • Save files internally if useful.
   • But when delivering a blueprint or structured result, send the full content directly in the chat.
5. Do not install many skills blindly.
   • First reuse local capabilities.
   • Then search ClawHub.
   • Then vet/scan.
   • Only then install or write new skills.

The 5-step workshop

Step 1 — Scenario Discovery

Goal: narrow a vague direction into one concrete, testable scenario.

Questions to drive:

• What are you consistently better at than most people?
• What do people repeatedly come to you for?
• If we only productize one scenario first, which one should it be?

Judging standard:

• Input can be defined
• Judgment can be structured
• Output can be verified

Output:

• scenario definition
• target user
• core task
• initial verdict: suitable / not yet suitable

Step 2 — SOP Extraction

Goal: extract the actual method, not just abstract knowledge.