teamsdlisted

Drives pre-sale solution design using IBM's Team Solution Design (TeamSD) methodology — produces the standard TeamSD work products (Project Definition, System Context, Non-Functional Requirements, Use Case Model, Architectural Decisions, Architecture Overview, Component Model, Operational Model, Viability Assessment, etc.) and walks the user outside-in through Plan → Pre-Sale Solution Design (EXPLORE, DEVELOP) → Support Implementation & Confirm Value phases. Use when the user asks to design a solution using TeamSD, write a Solution Design doc, build TeamSD work products, walk a case study, apply Buying Behaviour/BTT to choose work products, fill in SystemContextTemplate/TeAM-Template/Architectural Decisions templates, or mentions terms like TeamSD, Team Solution Design, UMF, CVM, SA4TeamSD, TeAMethod, iRAM, Solution Design work product, Viability Assessment, or the MyBank case study.
deeparchi-ai/Deeparchi-SD · ★ 0 · Web & Frontend · score 70

Install: claude install-skill deeparchi-ai/Deeparchi-SD

# TeamSD — Team Solution Design Use this skill to drive an IBM Team Solution Design (TeamSD) engagement. TeamSD is a pre-sale methodology: the goal is to produce a coherent set of work products that describes the client's problem, the proposed solution, and the proof it is viable — *just enough detail to assure the client their requirements are understood and the solution will address them*. ## Core mental model Three phases aligned with CVM: ``` Plan ───► Pre-Sale Solution Design ───► Support Implementation & Confirm Value (VALIDATED) (QUALIFIED → WON) (COMPLETED → NEW OPPORTUNITIES) │ │ ├ EXPLORE Options & Approach ├ IMPLEMENT Client Solution └ DEVELOP and Agree Solution └ CONFIRM Client Value & Experience ``` Nine core work products (memorize these): 1. Project Definition (ENG 343) 2. System Context (APP 011) 3. Non-Functional Requirements (ART 0507) 4. Use Case Model (ART 0508) 5. Architectural Decisions (ART 0513) 6. Architecture Overview (ART 0512) 7. Component Model (ART 0515) 8. Operational Model (ART 0522) 9. Viability Assessment (ART 0530) Three design principles govern everything: - **Outside-in** — start at System Context, work inward to components and nodes. - **Iterative** — activities drive the process, not tasks/work products. Revisit as new info arrives. Every decision traces back to a requirement. - **Varied level of elaboration** — pre-sale depth is "Basic/Conceptual" or "Presc