[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYRNQ0FWSA6X95PDCBYQSY":3,"skill-same:01M7AYRNQ0FWSA6X95PDCBYQSY":60},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M7AYRNQ0FWSA6X95PDCBYQSY","software-specification",null,"Spec-driven development workflow — requirements elicitation, SWEBOK-structured specs, template migration, spec validation against codebase.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fsoftware-specification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: software-specification\ndescription: Spec-driven development workflow — requirements elicitation, SWEBOK-structured specs, template migration, spec validation against codebase.\ntags: [specification, requirements, swebok, ba, grilling, template-migration]\n---\n\n# Software Specification\n\nSpec-driven development: write requirements before code, validate specs against implementation.\n\n## When to Use\n\n- User wants to define requirements for a new project\n- User has old specs that need restructuring into a standard template\n- User wants to validate specs against actual codebase\n- User mentions \"spec-driven development\" or \"requirements first\"\n\n## Workflow\n\n### Phase 1: Requirements Elicitation (Grilling)\n\nRun structured interview rounds to extract requirements. Use `grill-me` skill methodology:\n\n**Round 1 — Core Problem:**\n- What does \"done\" look like? (3-5 core actions)\n- Who is the user\u002Fpersona?\n- Why not existing solutions?\n- What's the MVP line?\n\n**Round 2 — Stress-Test Design:**\n- Find contradictions in answers\n- Challenge naming\u002Fsemantics\n- Identify gaps between vision and MVP\n\n**Round 3 — Architecture:**\n- API contract \u002F interface design\n- Data ownership \u002F isolation\n- Where it fits in existing stack\n- Why this architecture vs alternatives\n\n**Round 4 — Data Model:**\n- Review for redundancy (can fields be derived\u002Fcomputed?)\n- Naming consistency\n- Enum vs string trade-offs\n\n**Round 5 — API Contract:**\n- Propose endpoints\n- Pagination \u002F filtering\n- Response format\n- Error handling\n\n**Round 6 — Decisions:**\n- Consolidate all decisions\n- Set development order: spec → test → code\n\n### Phase 2: Spec Document Creation\n\nCreate structured spec documents using SWEBOK template format:\n\n```\nproject-specs\u002F\n├── 01_requirement\u002F\n│   ├── 011_business_objective.md    — SMART objectives\n│   ├── 012_user_stories.md          — User stories with ACs\n│   ├── 013_acceptance_criteria.md   — Given\u002FWhen\u002FThen format\n│   └── 014_stakeholder_analysis.md  — Stakeholder matrix\n├── 02_design\u002F\n│   ├── 021_architecture_decision_records.md  — ADRs\n│   ├── 022_API_specification.md              — REST endpoints\n│   ├── 023_database_schema_DDL.md            — PostgreSQL DDL\n│   ├── 024_ERD.md                            — Mermaid ERD\n│   └── 025_software_architecture_document.md — Architecture\n├── 03_construction\u002F\n│   ├── 031_README_developer_guide.md    — Setup instructions\n│   ├── 033_dependency_manifest.md       — Package versions\n│   ├── 034_commit_messages_changelog.md — PR\u002Fcommit log\n│   └── 035_coding_standards_development.md — Code style\n├── 04_testing\u002F\n│   ├── 041_test_plan.md     — Strategy + scope\n│   └── 042_test_cases.md    — Test cases from ACs\n├── 05_devops\u002F\n│   └── 053_release_notes.md — Release notes\n└── 07_pm\u002F\n    ├── 071_risk_register.md      — Risk log\n    └── 072_meeting_minutes.md    — Daily logs\n```\n\n**Key format rules:**\n- YAML frontmatter with document_type, version, status, tags, standard_ref\n- Tables for structured data (not prose)\n- Wikilinks for cross-references\n- Mermaid for diagrams (ERD, architecture, flowcharts)\n\n### Phase 3: Template Migration\n\nWhen user has old specs in non-standard format:\n\n1. Read old specs to understand content\n2. Read new template to understand structure\n3. Map old content to new structure\n4. Transform with proper frontmatter and formatting\n5. Create placeholder sections for TODO items\n\n**Mapping strategy:**\n| Old Content | New Location |\n|-------------|--------------|\n| Project overview | 011_business_objective + 021_ADR |\n| Data model | 023_database_schema_DDL + 024_ERD |\n| API spec | 022_API_specification |\n| Business logic | 013_acceptance_criteria |\n| Daily logs | 072_meeting_minutes |\n\n### Phase 4: Spec Validation\n\nAfter implementation exists, validate specs against actual codebase:\n\n1. Read GitHub repo structure (mcp__github__get_file_contents)\n2. Check actual dependencies (go.mod, package.json)\n3. Verify data model matches code structs\n4. Confirm API endpoints match handler code\n5. Update specs with actual versions and findings\n\n**What to check:**\n- Dependency versions (go.mod, package.json)\n- Data model structs (model\u002F*.go, types\u002F*.ts)\n- Handler implementations (handler\u002F*.go, pages\u002F*.tsx)\n- Test coverage (test files)\n- Configuration (ports, env vars)\n\n## Pitfalls\n\n- **Don't over-spec for MVP** — placeholder files are fine for future work\n- **Don't assume tech stack** — read actual code before updating specs\n- **Don't skip validation** — specs that don't match code are worse than no specs\n- **Use tables, not prose** — structured data is easier to maintain and reference\n- **Frontmatter matters** — consistent YAML enables tooling and filtering\n\n## Related Skills\n\n- `grill-me` — Requirements elicitation methodology\n- `plan` — Planning mode for implementation\n- `test-driven-development` — Test-first development\n","# Software Specification\n\nSpec-driven development: write requirements before code, validate specs against implementation.\n\n## When to Use\n\n- User wants to define requirements for a new project\n- User has old specs that need restructuring into a standard template\n- User wants to validate specs against actual codebase\n- User mentions \"spec-driven development\" or \"requirements first\"\n\n## Workflow\n\n### Phase 1: Requirements Elicitation (Grilling)\n\nRun structured interview rounds to extract requirements. Use `grill-me` skill methodology:\n\n**Round 1 — Core Problem:**\n- What does \"done\" look like? (3-5 core actions)\n- Who is the user\u002Fpersona?\n- Why not existing solutions?\n- What's the MVP line?\n\n**Round 2 — Stress-Test Design:**\n- Find contradictions in answers\n- Challenge naming\u002Fsemantics\n- Identify gaps between vision and MVP\n\n**Round 3 — Architecture:**\n- API contract \u002F interface design\n- Data ownership \u002F isolation\n- Where it fits in existing stack\n- Why this architecture vs alternatives\n\n**Round 4 — Data Model:**\n- Review for redundancy (can fields be derived\u002Fcomputed?)\n- Naming consistency\n- Enum vs string trade-offs\n\n**Round 5 — API Contract:**\n- Propose endpoints\n- Pagination \u002F filtering\n- Response format\n- Error handling\n\n**Round 6 — Decisions:**\n- Consolidate all decisions\n- Set development order: spec → test → code\n\n### Phase 2: Spec Document Creation\n\nCreate structured spec documents using SWEBOK template format:\n\n```\nproject-specs\u002F\n├── 01_requirement\u002F\n│   ├── 011_business_objective.md    — SMART objectives\n│   ├── 012_user_stories.md          — User stories with ACs\n│   ├── 013_acceptance_criteria.md   — Given\u002FWhen\u002FThen format\n│   └── 014_stakeholder_analysis.md  — Stakeholder matrix\n├── 02_design\u002F\n│   ├── 021_architecture_decision_records.md  — ADRs\n│   ├── 022_API_specification.md              — REST endpoints\n│   ├── 023_database_schema_DDL.md            — PostgreSQL DDL\n│   ├── 024_ERD.md                            — Mermaid ERD\n│   └── 025_software_architecture_document.md — Architecture\n├── 03_construction\u002F\n│   ├── 031_README_developer_guide.md    — Setup instructions\n│   ├── 033_dependency_manifest.md       — Package versions\n│   ├── 034_commit_messages_changelog.md — PR\u002Fcommit log\n│   └── 035_coding_standards_development.md — Code style\n├── 04_testing\u002F\n│   ├── 041_test_plan.md     — Strategy + scope\n│   └── 042_test_cases.md    — Test cases from ACs\n├── 05_devops\u002F\n│   └── 053_release_notes.md — Release notes\n└── 07_pm\u002F\n    ├── 071_risk_register.md      — Risk log\n    └── 072_meeting_minutes.md    — Daily logs\n```\n\n**Key format rules:**\n- YAML frontmatter with document_type, version, status, tags, standard_ref\n- Tables for structured data (not prose)\n- Wikilinks for cross-references\n- Mermaid for diagrams (ERD, architecture, flowcharts)\n\n### Phase 3: Template Migration\n\nWhen user has old specs in non-standard format:\n\n1. Read old specs to understand content\n2. Read new template to understand structure\n3. Map old content to new structure\n4. Transform with proper frontmatter and formatting\n5. Create placeholder sections for TODO items\n\n**Mapping strategy:**\n| Old Content | New Location |\n|-------------|--------------|\n| Project overview | 011_business_objective + 021_ADR |\n| Data model | 023_database_schema_DDL + 024_ERD |\n| API spec | 022_API_specification |\n| Business logic | 013_acceptance_criteria |\n| Daily logs | 072_meeting_minutes |\n\n### Phase 4: Spec Validation\n\nAfter implementation exists, validate specs against actual codebase:\n\n1. Read GitHub repo structure (mcp__github__get_file_contents)\n2. Check actual dependencies (go.mod, package.json)\n3. Verify data model matches code structs\n4. Confirm API endpoints match handler code\n5. Update specs with actual versions and findings\n\n**What to check:**\n- Dependency versions (go.mod, package.json)\n- Data model structs (model\u002F*.go, types\u002F*.ts)\n- Handler implementations (handler\u002F*.go, pages\u002F*.tsx)\n- Test coverage (test files)\n- Configuration (ports, env vars)\n\n## Pitfalls\n\n- **Don't over-spec for MVP** — placeholder files are fine for future work\n- **Don't assume tech stack** — read actual code before updating specs\n- **Don't skip validation** — specs that don't match code are worse than no specs\n- **Use tables, not prose** — structured data is easier to maintain and reference\n- **Frontmatter matters** — consistent YAML enables tooling and filtering\n\n## Related Skills\n\n- `grill-me` — Requirements elicitation methodology\n- `plan` — Planning mode for implementation\n- `test-driven-development` — Test-first development\n",{"name":5,"tags":24,"description":7},[25,26,27,28,29,30],"specification","requirements","swebok","ba","grilling","template-migration","main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fhermes-main-profile\u002Fsoftware-specification",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add oat431\u002Fhermes_config_backup --skill software-specification",{"tool":46,"command":47},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill software-specification",{"tool":49,"command":50},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill software-specification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fsoftware-specification\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fswebok-template-structure.md","REFERENCE","参考文档",3532,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fsoftware-specification\u002Freferences\u002Fswebok-template-structure.md",[61,69,76,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"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},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]