[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CT42THPYNA2EXX0YC4V0ES":3,"skill-same:01M7CT42THPYNA2EXX0YC4V0ES":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7CT42THPYNA2EXX0YC4V0ES","sdd-architect",null,"Author comprehensive Software Design Description (SDD) specifications compliant with IEEE 1016-2009 standard, translating SRS requirements into layered clean architectures, explicit Business Service method signatures, domain exceptions, ERDs, REST APIs, and ADRs.","roychshao\u002Fhermes-multi-agent-sdlc","roychshao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80042326?v=4","01M7CT40S8BYSC0MNGP7XBSHZV","邵靖翔","01M7CT40SVAZD0C7JVDFSDGWJ8",0,"MIT","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-architech\u002Fskills\u002Fsdd-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdd-architect\ndescription: \"Author comprehensive Software Design Description (SDD) specifications compliant with IEEE 1016-2009 standard, translating SRS requirements into layered clean architectures, explicit Business Service method signatures, domain exceptions, ERDs, REST APIs, and ADRs.\"\nversion: 2.0.0\nauthor: Hermes Agent Team\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [architecture, sdd, ieee-1016, system-design, database, erd, openapi, adr]\n    related_skills: [srs-specifier, test-planner, delegate-software-engineering-team]\n---\n\n# Software Design Description (SDD) Skill (IEEE 1016)\n\n## Overview\nProduce a comprehensive **Software Design Description (SDD)** document that translates requirements from `docs\u002Fsrs.md` into concrete, implementable software blueprints.\n\n## Standards Compliance\n- **IEEE 1016-2009**: IEEE Standard for Information Technology — Systems Design — Software Design Descriptions.\n\n## When to Use\n- Phase 1 Architecture Design (dispatched by `dev-pm` to `dev-architech`).\n- Mid-development Tier 2 architectural revisions when database schema or cross-module boundaries change.\n- Replaces legacy lightweight `system_design.md` with an IEEE 1016 compliant specification.\n\n## Target Output Path\n`\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fsdd.md`  \n`\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fadr\u002FADR-XXX-{title}.md` (for major architectural decisions)\n\n---\n\n## 🔒 Ironclad Tech Stack Adherence Rule\n> [!CAUTION]\n> **Strict Compliance with `docs\u002Fsrs.md` Section 3**:\n> `dev-architech` MUST read `docs\u002Fsrs.md` first. The architectural design MUST 100% follow the exact language, framework, database engine, and ORM specified in `docs\u002Fsrs.md` Section 3.\n> **DO NOT switch tech stacks (e.g. never substitute TypeScript\u002FExpress for Python\u002FFastAPI or vice-versa)** unless explicitly authorized by the user via an approved ADR.\n\n---\n\n\n## 🌐 System Boundary, Network Topology & Infrastructure Architecture Law\n> [!IMPORTANT]\n> **Mandatory Network Topology, CORS & DevOps Containerization Specifications**:\n> In addition to Domain Models and Business Services, `dev-architech` **MUST explicitly author a dedicated Network Topology & Infrastructure Blueprint section in `docs\u002Fsdd.md`**:\n> 1. **System Boundary & Network Topology**: Mermaid diagram depicting Client Browser, Reverse Proxy \u002F Ingress (Nginx), Application Server (FastAPI \u002F Uvicorn), Database (PostgreSQL 16), and Background Schedulers.\n> 2. **Cross-Origin Resource Sharing (CORS) Specification**: Explicit specification of CORS policy, configurable via `CORS_ORIGINS` environment variable, including `allow_origins`, `allow_credentials`, `allow_methods`, and `allow_headers`.\n> 3. **Gateway & Routing Contracts**: Standard path prefix (`\u002Fapi\u002Fv1`), trailing slash rules, and reverse proxy forwarding headers (`X-Forwarded-For`, `X-Forwarded-Proto`, `Host`).\n> 4. **DevOps Multi-Container Topology**: Complete blueprint for `dev-ops` containerization in Phase 5, defining container service names, internal network bridges, exposed host ports, volume persistence mounts, Required Environment Variables Specification (categorized by Backend, Frontend, and Database container), and container healthchecks.\n\n## ⚖️ SDD Service Contract Law\n> [!IMPORTANT]\n> **Explicit Business Service Layer & Domain Exception Contracts**:\n> In Phase 1 SDD authoring, `dev-architech` **MUST explicitly specify**:\n> 1. **Domain Business Service Layer**: Full class definitions, method signatures (`async def method_name(...) -> ReturnType`), exact parameter types, and return models.\n> 2. **Domain Exception Hierarchy**: Explicit domain Exception classes (e.g. `MeetingNotFoundError`, `DuplicateTranscriptError`, `InvalidMeetingStateError`) with their HTTP status mappings and error codes.\n> 3. **Repository Interfaces**: Data access contracts and async session boundaries.\n> This provides an unambiguous blueprint so that `dev-backend` and `dev-tester` never guess or diverge on method contracts.\n\n---\n\n## 🛠️ Step-by-Step Procedure\n\n### Step 1: Ingest SRS Specification\n1. Read `\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fsrs.md`.\n2. Extract all Use Cases (`UC-001` ~ `UC-NNN`), Technical Constraints (`TC`), and Non-Functional Requirements (`NFR`).\n\n### Step 2: Design Layered Software Architecture & Domain Services\nEstablish a clean separation of concerns:\n- **Presentation Layer (Frontend)**: React Components, Custom Hooks, Zustand\u002FContext Stores, Axios\u002FFetch API Clients.\n- **Interface Layer (Routers \u002F Controllers)**: FastAPI APIRouter, request validation via Pydantic schemas, HTTP status mapping, dependency injection (DB sessions, current user).\n- **Domain & Service Layer**: Explicit Business Service classes, typed method signatures, domain exception raises, business logic workflows.\n- **Data Access Layer (Persistence & Repositories)**: SQLAlchemy 2.0 Async declarative models, async queries, transaction boundaries.\n\n### Step 3: Complete Data Architecture & ERD \u002F DDL\n1. Provide a Mermaid ERD diagram showing all entities, cardinality (1:1, 1:N, N:M), foreign keys, and cascading rules.\n2. Provide **complete, copy-paste ready SQL DDL statements** for all tables with exact data types, constraints, default values, and indexes.\n\n### Step 4: Interface & API Specification (OpenAPI 3.0 Standard)\nFor every API endpoint:\n1. HTTP Method and Route Path (e.g. `POST \u002Fapi\u002Fv1\u002Fmeetings`).\n2. Authentication & Authorization requirements (e.g. Bearer JWT, required role).\n3. Request Headers, Query Parameters, Path Parameters.\n4. Request Body JSON schema with data types and validation rules.\n5. Response Body JSON schemas for HTTP 200\u002F201 (Success) and HTTP 400\u002F401\u002F403\u002F404\u002F422\u002F500 (Error).\n\n### Step 5: Requirement Traceability Matrix (RTM)\nConstruct an exhaustive bidirectional Traceability Matrix mapping:\n`SRS Use Case ID` -> `API Endpoints` -> `Database Models` -> `Service Functions` -> `Frontend Views` -> `Test Cases`.\n\n### Step 6: Security & Cross-Cutting Architecture\n1. JWT lifecycle (Issuance, Expiration, Claims: `sub`, `email`, `role`, `exp`).\n2. Password hashing configuration (bcrypt with work factor 12).\n3. Global Exception Handler & Standard Error Response Envelope.\n4. CORS middleware configuration and allowed origins\u002Fmethods.\n\n### Step 7: Output SDD & Report\n1. Write `\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fsdd.md`.\n2. If major architectural trade-offs occurred, write `\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fadr\u002FADR-001-{title}.md`.\n3. Commit and push to git: `git add docs\u002F && git commit -m \"docs(architecture): IEEE 1016 SDD specification\" && git push origin main`.\n4. Call `kanban_complete()` to notify PM.\n","# Software Design Description (SDD) Skill (IEEE 1016)\n\n## Overview\nProduce a comprehensive **Software Design Description (SDD)** document that translates requirements from `docs\u002Fsrs.md` into concrete, implementable software blueprints.\n\n## Standards Compliance\n- **IEEE 1016-2009**: IEEE Standard for Information Technology — Systems Design — Software Design Descriptions.\n\n## When to Use\n- Phase 1 Architecture Design (dispatched by `dev-pm` to `dev-architech`).\n- Mid-development Tier 2 architectural revisions when database schema or cross-module boundaries change.\n- Replaces legacy lightweight `system_design.md` with an IEEE 1016 compliant specification.\n\n## Target Output Path\n`\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fsdd.md`  \n`\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fadr\u002FADR-XXX-{title}.md` (for major architectural decisions)\n\n---\n\n## 🔒 Ironclad Tech Stack Adherence Rule\n> [!CAUTION]\n> **Strict Compliance with `docs\u002Fsrs.md` Section 3**:\n> `dev-architech` MUST read `docs\u002Fsrs.md` first. The architectural design MUST 100% follow the exact language, framework, database engine, and ORM specified in `docs\u002Fsrs.md` Section 3.\n> **DO NOT switch tech stacks (e.g. never substitute TypeScript\u002FExpress for Python\u002FFastAPI or vice-versa)** unless explicitly authorized by the user via an approved ADR.\n\n---\n\n\n## 🌐 System Boundary, Network Topology & Infrastructure Architecture Law\n> [!IMPORTANT]\n> **Mandatory Network Topology, CORS & DevOps Containerization Specifications**:\n> In addition to Domain Models and Business Services, `dev-architech` **MUST explicitly author a dedicated Network Topology & Infrastructure Blueprint section in `docs\u002Fsdd.md`**:\n> 1. **System Boundary & Network Topology**: Mermaid diagram depicting Client Browser, Reverse Proxy \u002F Ingress (Nginx), Application Server (FastAPI \u002F Uvicorn), Database (PostgreSQL 16), and Background Schedulers.\n> 2. **Cross-Origin Resource Sharing (CORS) Specification**: Explicit specification of CORS policy, configurable via `CORS_ORIGINS` environment variable, including `allow_origins`, `allow_credentials`, `allow_methods`, and `allow_headers`.\n> 3. **Gateway & Routing Contracts**: Standard path prefix (`\u002Fapi\u002Fv1`), trailing slash rules, and reverse proxy forwarding headers (`X-Forwarded-For`, `X-Forwarded-Proto`, `Host`).\n> 4. **DevOps Multi-Container Topology**: Complete blueprint for `dev-ops` containerization in Phase 5, defining container service names, internal network bridges, exposed host ports, volume persistence mounts, Required Environment Variables Specification (categorized by Backend, Frontend, and Database container), and container healthchecks.\n\n## ⚖️ SDD Service Contract Law\n> [!IMPORTANT]\n> **Explicit Business Service Layer & Domain Exception Contracts**:\n> In Phase 1 SDD authoring, `dev-architech` **MUST explicitly specify**:\n> 1. **Domain Business Service Layer**: Full class definitions, method signatures (`async def method_name(...) -> ReturnType`), exact parameter types, and return models.\n> 2. **Domain Exception Hierarchy**: Explicit domain Exception classes (e.g. `MeetingNotFoundError`, `DuplicateTranscriptError`, `InvalidMeetingStateError`) with their HTTP status mappings and error codes.\n> 3. **Repository Interfaces**: Data access contracts and async session boundaries.\n> This provides an unambiguous blueprint so that `dev-backend` and `dev-tester` never guess or diverge on method contracts.\n\n---\n\n## 🛠️ Step-by-Step Procedure\n\n### Step 1: Ingest SRS Specification\n1. Read `\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fsrs.md`.\n2. Extract all Use Cases (`UC-001` ~ `UC-NNN`), Technical Constraints (`TC`), and Non-Functional Requirements (`NFR`).\n\n### Step 2: Design Layered Software Architecture & Domain Services\nEstablish a clean separation of concerns:\n- **Presentation Layer (Frontend)**: React Components, Custom Hooks, Zustand\u002FContext Stores, Axios\u002FFetch API Clients.\n- **Interface Layer (Routers \u002F Controllers)**: FastAPI APIRouter, request validation via Pydantic schemas, HTTP status mapping, dependency injection (DB sessions, current user).\n- **Domain & Service Layer**: Explicit Business Service classes, typed method signatures, domain exception raises, business logic workflows.\n- **Data Access Layer (Persistence & Repositories)**: SQLAlchemy 2.0 Async declarative models, async queries, transaction boundaries.\n\n### Step 3: Complete Data Architecture & ERD \u002F DDL\n1. Provide a Mermaid ERD diagram showing all entities, cardinality (1:1, 1:N, N:M), foreign keys, and cascading rules.\n2. Provide **complete, copy-paste ready SQL DDL statements** for all tables with exact data types, constraints, default values, and indexes.\n\n### Step 4: Interface & API Specification (OpenAPI 3.0 Standard)\nFor every API endpoint:\n1. HTTP Method and Route Path (e.g. `POST \u002Fapi\u002Fv1\u002Fmeetings`).\n2. Authentication & Authorization requirements (e.g. Bearer JWT, required role).\n3. Request Headers, Query Parameters, Path Parameters.\n4. Request Body JSON schema with data types and validation rules.\n5. Response Body JSON schemas for HTTP 200\u002F201 (Success) and HTTP 400\u002F401\u002F403\u002F404\u002F422\u002F500 (Error).\n\n### Step 5: Requirement Traceability Matrix (RTM)\nConstruct an exhaustive bidirectional Traceability Matrix mapping:\n`SRS Use Case ID` -> `API Endpoints` -> `Database Models` -> `Service Functions` -> `Frontend Views` -> `Test Cases`.\n\n### Step 6: Security & Cross-Cutting Architecture\n1. JWT lifecycle (Issuance, Expiration, Claims: `sub`, `email`, `role`, `exp`).\n2. Password hashing configuration (bcrypt with work factor 12).\n3. Global Exception Handler & Standard Error Response Envelope.\n4. CORS middleware configuration and allowed origins\u002Fmethods.\n\n### Step 7: Output SDD & Report\n1. Write `\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fsdd.md`.\n2. If major architectural trade-offs occurred, write `\u002Fopt\u002Fdata\u002Fworkspace\u002F{project_name}\u002Fdocs\u002Fadr\u002FADR-001-{title}.md`.\n3. Commit and push to git: `git add docs\u002F && git commit -m \"docs(architecture): IEEE 1016 SDD specification\" && git push origin main`.\n4. Call `kanban_complete()` to notify PM.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":41,"description":7},"Hermes Agent Team","2.0.0",{"hermes":27},{"tags":28,"related_skills":37},[29,30,31,32,33,34,35,36],"architecture","sdd","ieee-1016","system-design","database","erd","openapi","adr",[38,39,40],"srs-specifier","test-planner","delegate-software-engineering-team",[42,43,44],"linux","macos","windows","master","89e68a8718471ab849f0bdbce4a3b9c482268777","dev-architech\u002Fskills\u002Fsdd-architect","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc","https:\u002F\u002Fgithub.com\u002Froychshao","National Taiwan University CSIE Master\r\nNational Chengchi University CS Bachelor","2026-09-15 03:35:21",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add roychshao\u002Fhermes-multi-agent-sdlc --skill sdd-architect",{"tool":58,"command":59},"bunx","bunx skills add roychshao\u002Fhermes-multi-agent-sdlc --skill sdd-architect",{"tool":61,"command":62},"pnpm","pnpm dlx skills add roychshao\u002Fhermes-multi-agent-sdlc --skill sdd-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-architech\u002Fskills\u002Fsdd-architect\u002FSKILL.md",true,[],[67,73,79,86,92,97],{"skillNo":68,"name":38,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CT8XM3T4AHBARB8ZVVZCH7","Generate professional Software Requirements Specification (SRS) compliant with ISO\u002FIEC\u002FIEEE 29148 and IEEE 830 standards, focusing purely on requirements (WHAT the system does) with granular use-case decomposition, high-level technology constraints, non-functional requirements, and strict exclusion of design details (no API routes, no ERD\u002FDDL, no response envelopes).","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fmain\u002Fskills\u002Fsrs-specifier\u002FSKILL.md",[],[],{"skillNo":74,"name":39,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CT84MWYRZ9FFFS4FTMVMNH","Author comprehensive Test Plan specifications compliant with ISO\u002FIEC\u002FIEEE 29119-3 standard (superseding IEEE 829) and E2E Testing Patterns, establishing testing pyramid ratios, fixture strategies, boundary edge cases, headless containerized E2E acceptance suites, and triple-gate quality metrics.","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-tester\u002Fskills\u002Ftest-planner\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CT6WM0NNVJ9ZW4MSS4YYDK","writing-plans","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-pm\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":87,"name":32,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CT6H6BEPFJW4QKH0CXY14F","Produce a comprehensive system design document for a software project.","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-pm\u002Fskills\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":93,"name":38,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CT6B27YCX5QVZXE4H9ZZR2","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-pm\u002Fskills\u002Fsrs-specifier\u002FSKILL.md",[],[],{"skillNo":98,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CT65P7PTV5YNVTT3BDZKFR","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-pm\u002Fskills\u002Fsdd-architect\u002FSKILL.md",[],[]]