[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CT48N0ES26RYPCW4CS1GVN":3,"skill-same:01M7CT48N0ES26RYPCW4CS1GVN":65},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7CT48N0ES26RYPCW4CS1GVN","system-design",null,"Produce a professional Software Design Description (SDD) compliant with IEEE 1016 standard, with strict requirement traceability, locked tech stack adherence, database ERD\u002FDDL, OpenAPI specifications, and layered architecture design.","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\u002Fsystem-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: system-design\ndescription: \"Produce a professional Software Design Description (SDD) compliant with IEEE 1016 standard, with strict requirement traceability, locked tech stack adherence, database ERD\u002FDDL, OpenAPI specifications, and layered architecture design.\"\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 3 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## 🛠️ 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\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**: Business logic, workflow validation, domain events, transaction orchestration.\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` $\\rightarrow$ `API Endpoints` $\\rightarrow$ `Database Models` $\\rightarrow$ `Service Functions` $\\rightarrow$ `Frontend Views` $\\rightarrow$ `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 (refs #{issue})\" && git push origin main`.\n4. Call `kanban_complete()` to notify PM.\n\n---\n\n## 📄 SDD Document Template Structure\n\n```markdown\n# Software Design Description (SDD)\n## Project: {Project Name}\n**Standard**: IEEE 1016-2009  \n**Version**: 1.0.0  \n**Status**: Baseline  \n**SRS Reference**: `docs\u002Fsrs.md` (v1.0.0)  \n\n---\n\n## 1. System Overview & Architectural Style\n### 1.1 Architectural Pattern\n- **Style**: Layered Clean Architecture (Client-Server over REST API)\n- **Frontend Architecture**: SPA with React, TypeScript, Component-Driven Design.\n- **Backend Architecture**: Layered Modular Architecture (Routers -> Services -> Repositories\u002FModels).\n\n### 1.2 System Topology Diagram\n```mermaid\ngraph TD\n    Client[React Frontend \u002F Browser] -->|HTTP REST \u002F JSON| Gateway[FastAPI Backend Application]\n    Gateway --> Router[API Routers \u002F Controllers]\n    Router --> Service[Domain Business Services]\n    Service --> Repo[Data Access \u002F Repositories]\n    Repo --> DB[(PostgreSQL 16 Database)]\n```\n\n---\n\n## 2. Requirement Traceability Matrix (RTM)\n| SRS UC ID | Description | API Endpoint(s) | Database Tables | Backend Service \u002F Model | Frontend Component | Test Suite Ref |\n| :--- | :--- | :--- | :--- | :--- | :--- | :--- |\n| `UC-001` | User Registration | `POST \u002Fapi\u002Fv1\u002Fauth\u002Fregister` | `users` | `AuthService.register` \u002F `User` | `RegisterPage`, `AuthForm` | `tests\u002Funit\u002Ftest_auth.py` |\n| `UC-002` | User Login | `POST \u002Fapi\u002Fv1\u002Fauth\u002Flogin` | `users` | `AuthService.login` \u002F `User` | `LoginPage` | `tests\u002Funit\u002Ftest_auth.py` |\n\n---\n\n## 3. Data Architecture & Database Design\n### 3.1 Entity Relationship Diagram (ERD)\n```mermaid\nerDiagram\n    USERS ||--o{ MEETINGS : creates\n    MEETINGS ||--o{ MINUTES : contains\n    MEETINGS ||--o{ ACTION_ITEMS : assigns\n    \n    USERS {\n        uuid id PK\n        string email UK\n        string hashed_password\n        string full_name\n        string role\n        timestamp created_at\n    }\n```\n\n### 3.2 SQL DDL Schema\n```sql\nCREATE EXTENSION IF NOT EXISTS \"uuid-ossp\";\n\nCREATE TABLE users (\n    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),\n    email VARCHAR(255) UNIQUE NOT NULL,\n    hashed_password VARCHAR(255) NOT NULL,\n    full_name VARCHAR(100) NOT NULL,\n    role VARCHAR(50) NOT NULL DEFAULT 'member',\n    is_active BOOLEAN NOT NULL DEFAULT TRUE,\n    created_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP,\n    updated_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP\n);\n\nCREATE INDEX idx_users_email ON users(email);\n```\n\n---\n\n## 4. API & Interface Specifications\n### 4.1 Authentication & Base URL\n- **Base URL**: `\u002Fapi\u002Fv1`\n- **Security Scheme**: `Authorization: Bearer \u003CJWT_TOKEN>`\n\n### 4.2 Endpoint Specifications\n#### `POST \u002Fapi\u002Fv1\u002Fauth\u002Fregister`\n- **Description**: Registers a new user account.\n- **Request Body**:\n  ```json\n  {\n    \"email\": \"user@example.com\",\n    \"password\": \"SecurePassword123!\",\n    \"full_name\": \"Roy Shao\"\n  }\n  ```\n- **Responses**:\n  - `201 Created`: `{\"id\": \"uuid\", \"email\": \"user@example.com\", \"full_name\": \"Roy Shao\"}`\n  - `400 Bad Request`: `{\"detail\": \"Email already registered\", \"code\": \"EMAIL_EXISTS\"}`\n  - `422 Unprocessable Entity`: Field validation error.\n\n---\n\n## 5. Security & Session Architecture\n1. **Password Hashing**: Passlib bcrypt context with `rounds=12`.\n2. **JWT Issuance**: `jwt.encode({\"sub\": str(user.id), \"email\": user.email, \"role\": user.role, \"exp\": ...}, SECRET_KEY, algorithm=\"HS256\")`.\n3. **CORS Configuration**: Allowed origins configured via `CORS_ORIGINS` environment variable.\n\n---\n\n## 6. Architecture Decision Records (ADRs)\n- `docs\u002Fadr\u002FADR-001-postgresql-async-orm.md`\n- `docs\u002Fadr\u002FADR-002-jwt-stateless-authentication.md`\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 3 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## 🛠️ 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\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**: Business logic, workflow validation, domain events, transaction orchestration.\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` $\\rightarrow$ `API Endpoints` $\\rightarrow$ `Database Models` $\\rightarrow$ `Service Functions` $\\rightarrow$ `Frontend Views` $\\rightarrow$ `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 (refs #{issue})\" && git push origin main`.\n4. Call `kanban_complete()` to notify PM.\n\n---\n\n## 📄 SDD Document Template Structure\n\n```markdown\n# Software Design Description (SDD)\n## Project: {Project Name}\n**Standard**: IEEE 1016-2009  \n**Version**: 1.0.0  \n**Status**: Baseline  \n**SRS Reference**: `docs\u002Fsrs.md` (v1.0.0)  \n\n---\n\n## 1. System Overview & Architectural Style\n### 1.1 Architectural Pattern\n- **Style**: Layered Clean Architecture (Client-Server over REST API)\n- **Frontend Architecture**: SPA with React, TypeScript, Component-Driven Design.\n- **Backend Architecture**: Layered Modular Architecture (Routers -> Services -> Repositories\u002FModels).\n\n### 1.2 System Topology Diagram\n```mermaid\ngraph TD\n    Client[React Frontend \u002F Browser] -->|HTTP REST \u002F JSON| Gateway[FastAPI Backend Application]\n    Gateway --> Router[API Routers \u002F Controllers]\n    Router --> Service[Domain Business Services]\n    Service --> Repo[Data Access \u002F Repositories]\n    Repo --> DB[(PostgreSQL 16 Database)]\n```\n\n---\n\n## 2. Requirement Traceability Matrix (RTM)\n| SRS UC ID | Description | API Endpoint(s) | Database Tables | Backend Service \u002F Model | Frontend Component | Test Suite Ref |\n| :--- | :--- | :--- | :--- | :--- | :--- | :--- |\n| `UC-001` | User Registration | `POST \u002Fapi\u002Fv1\u002Fauth\u002Fregister` | `users` | `AuthService.register` \u002F `User` | `RegisterPage`, `AuthForm` | `tests\u002Funit\u002Ftest_auth.py` |\n| `UC-002` | User Login | `POST \u002Fapi\u002Fv1\u002Fauth\u002Flogin` | `users` | `AuthService.login` \u002F `User` | `LoginPage` | `tests\u002Funit\u002Ftest_auth.py` |\n\n---\n\n## 3. Data Architecture & Database Design\n### 3.1 Entity Relationship Diagram (ERD)\n```mermaid\nerDiagram\n    USERS ||--o{ MEETINGS : creates\n    MEETINGS ||--o{ MINUTES : contains\n    MEETINGS ||--o{ ACTION_ITEMS : assigns\n    \n    USERS {\n        uuid id PK\n        string email UK\n        string hashed_password\n        string full_name\n        string role\n        timestamp created_at\n    }\n```\n\n### 3.2 SQL DDL Schema\n```sql\nCREATE EXTENSION IF NOT EXISTS \"uuid-ossp\";\n\nCREATE TABLE users (\n    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),\n    email VARCHAR(255) UNIQUE NOT NULL,\n    hashed_password VARCHAR(255) NOT NULL,\n    full_name VARCHAR(100) NOT NULL,\n    role VARCHAR(50) NOT NULL DEFAULT 'member',\n    is_active BOOLEAN NOT NULL DEFAULT TRUE,\n    created_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP,\n    updated_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP\n);\n\nCREATE INDEX idx_users_email ON users(email);\n```\n\n---\n\n## 4. API & Interface Specifications\n### 4.1 Authentication & Base URL\n- **Base URL**: `\u002Fapi\u002Fv1`\n- **Security Scheme**: `Authorization: Bearer \u003CJWT_TOKEN>`\n\n### 4.2 Endpoint Specifications\n#### `POST \u002Fapi\u002Fv1\u002Fauth\u002Fregister`\n- **Description**: Registers a new user account.\n- **Request Body**:\n  ```json\n  {\n    \"email\": \"user@example.com\",\n    \"password\": \"SecurePassword123!\",\n    \"full_name\": \"Roy Shao\"\n  }\n  ```\n- **Responses**:\n  - `201 Created`: `{\"id\": \"uuid\", \"email\": \"user@example.com\", \"full_name\": \"Roy Shao\"}`\n  - `400 Bad Request`: `{\"detail\": \"Email already registered\", \"code\": \"EMAIL_EXISTS\"}`\n  - `422 Unprocessable Entity`: Field validation error.\n\n---\n\n## 5. Security & Session Architecture\n1. **Password Hashing**: Passlib bcrypt context with `rounds=12`.\n2. **JWT Issuance**: `jwt.encode({\"sub\": str(user.id), \"email\": user.email, \"role\": user.role, \"exp\": ...}, SECRET_KEY, algorithm=\"HS256\")`.\n3. **CORS Configuration**: Allowed origins configured via `CORS_ORIGINS` environment variable.\n\n---\n\n## 6. Architecture Decision Records (ADRs)\n- `docs\u002Fadr\u002FADR-001-postgresql-async-orm.md`\n- `docs\u002Fadr\u002FADR-002-jwt-stateless-authentication.md`\n```\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":40,"description":7},"Hermes Agent Team","2.0.0",{"hermes":27},{"tags":28,"related_skills":36},[29,30,31,5,32,33,34,35],"architecture","sdd","ieee-1016","database","erd","openapi","adr",[37,38,39],"srs-specifier","test-planner","delegate-software-engineering-team",[41,42,43],"linux","macos","windows","master","89e68a8718471ab849f0bdbce4a3b9c482268777","dev-architech\u002Fskills\u002Fsystem-design","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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add roychshao\u002Fhermes-multi-agent-sdlc --skill system-design",{"tool":57,"command":58},"bunx","bunx skills add roychshao\u002Fhermes-multi-agent-sdlc --skill system-design",{"tool":60,"command":61},"pnpm","pnpm dlx skills add roychshao\u002Fhermes-multi-agent-sdlc --skill system-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-architech\u002Fskills\u002Fsystem-design\u002FSKILL.md",true,[],[66,72,78,85,91,96],{"skillNo":67,"name":37,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":38,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":5,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":37,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CT6B27YCX5QVZXE4H9ZZR2","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-pm\u002Fskills\u002Fsrs-specifier\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CT65P7PTV5YNVTT3BDZKFR","sdd-architect","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.","https:\u002F\u002Fgithub.com\u002Froychshao\u002Fhermes-multi-agent-sdlc\u002Fblob\u002Fmaster\u002Fdev-pm\u002Fskills\u002Fsdd-architect\u002FSKILL.md",[],[]]