skill-forge-planlisted

# Skill Architecture & Design Planning ## Process ### Step 1: Domain Discovery Ask the user these questions (adapt based on context): 1. **What domain is this skill for?** (e.g., SEO, advertising, DevOps, data analysis) 2. **What are the top 2-3 use cases?** What should users be able to accomplish? 3. **What trigger phrases would users say?** List 5-10 natural language triggers. 4. **Does it need external tools?** MCP servers, APIs, CLI tools? 5. **Who is the target user?** Developer, marketer, analyst, general user? ### Step 2: Use Case Decomposition For each use case, define: ``` Use Case: [Name] Trigger: User says "[phrases]" Steps: 1. [First action] 2. [Decision point or validation] 3. [Next action] Result: [What success looks like] Tools Needed: [built-in, MCP, scripts] ``` ### Step 3: Complexity Tier Assessment Evaluate based on answers: | Signal | Tier 1 | Tier 2 | Tier 3 | Tier 4 | |--------|--------|--------|--------|--------| | Use cases | 1-2 | 2-3 | 4-8 | 8+ | | Needs scripts? | No | Yes | Maybe | Yes | | Sub-skills needed? | No | No | Yes | Yes | | Parallel execution? | No | No | No | Yes | | Reference docs? | No | Maybe | Yes | Yes | | Industry templates? | No | No | Maybe | Yes | **Decision matrix:** - Single workflow, no scripts -> **Tier 1** (minimal) - Needs deterministic validation -> **Tier 2** (workflow) - Multiple distinct workflows -> **Tier 3** (multi-skill) - Complex domain with parallel delegation -> **Tier 4** (ecosystem) ### Step 4: Arc