[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C7RTECP7GHP9N70QJWSSN5":3,"skill-same:01M7C7RTECP7GHP9N70QJWSSN5":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7C7RTECP7GHP9N70QJWSSN5","highway-onboarding",null,"Manages one decision, one reference architecture, and one reference implementation. Use when the person wants to onboard one capability in a single pass, grounded in accepted setup or architecture records.","jacob623\u002Fhighway-skills","jacob623","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9532643?v=4","01M7C7HA4F52SFFC164SQ76BC6","01M7C7HA57FCG77W7TGPX5R706",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhighway-onboarding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: highway-onboarding\ndescription: \"Manages one decision, one reference architecture, and one reference implementation. Use when the person wants to onboard one capability in a single pass, grounded in accepted setup or architecture records.\"\nlicense: Apache-2.0\nmetadata:\n  version: 10.13.0\n  usage: \"Run highway-onboarding.\"\n---\n\n# highway-onboarding\n\n## Purpose\n\nBrings existing platforms into Highway by validating capabilities, mapping them to providers, and orchestrating one decision, architecture, and implementation for each provider group.\n\n## When to use\n\n- The person invokes `highway-onboarding`.\n- Accepted Profile, Objectives, Controls, NFRs, or existing architecture records can ground a capability.\n\n## When not to use\n\nDo not create a technology, platform, provider, or application inventory. `library\u002Fcoding-standards\u002Fcodify-platforms.md` lists only platforms that can start automation and is not that inventory.\nDo not create a Request, Discovery, or synthetic `DISC` record.\nDo not change Profile, Objectives, Controls, or NFRs.\nDo not authorize deployment.\nDo not authorize the agent platform to act on its own.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\n\n## Inputs\n\n- Accepted Profile, Objectives, Controls, NFRs, ADRs, architectures, and implementations when present.\n- Material the person supplies, including a website when retrieval is available.\n- `adrs\u002Fadrs.md`.\n- `highway-adr`.\n- `highway-architecture`.\n- `highway-implementation`.\n- `library\u002Fcoding-standards\u002Fcodify-platforms.md`.\n- The highway-experience skill, activated first.\n\n## Outputs\n\n- One accepted ADR, Reference Architecture, and Reference Implementation per provider group, written by `highway-adr`, `highway-architecture`, and `highway-implementation`.\n- One lineage that lists every completed provider, then one summary.\n- One row in `library\u002Fcoding-standards\u002Fcodify-platforms.md`, with blank When to use and When not to use, written by `highway-implementation` for each implementation that can start automation.\n- No inventory file. The capability queue and the provider queue are not written.\n\n## Procedure\n\nActivate the highway-experience skill before any output the person sees, and follow it for Highway's identity, the Experience Standard, and the storage contract.\n\nBefore the first question, confirm these seeded files exist: `adrs\u002Fadrs.md`, `architectures\u002Farchitectures.md`, `implementations\u002Fimplementations.md`, `implementations\u002Fcapabilities.md`, `library\u002Fcoding-standards\u002Fcodify-platforms.md`.\nWhen any is absent, emit the message below exactly, stop, and write nothing.\n\n**Oops... we need to setup your repository.**\n\nHighway needs to gather your organizational preferences and set up your repository. Run highway-setup to get started.\n\nEmit only the active template. Follow the steps in this order: `overview`, `capabilities`, `map`, `mapping`, `orchestrate`, `lineage`, `configure`, then `summary`. Review happens only when the person asks for it from the summary.\n\nOnboarding keeps two queues. The capability queue holds accepted capabilities that still need a platform. The provider queue holds accepted providers that still need a decision. Neither queue is written. Queue membership is not an ADR, an architecture, or an implementation.\n\nA capability may map to more than one provider. A provider may serve more than one capability. One mapping may be primary. A capability the person says does not exist is removed. A provider the person says does not exist is marked `Does not exist` and does not enter the provider queue.\n\nBefore a step in this table, read its file and follow it to the end.\n\n| File | Steps |\n| --- | --- |\n| `references\u002Fproposal.md` | `overview`, `capabilities`, `map`, `mapping` |\n| `references\u002Forchestrate.md` | `orchestrate`, `lineage`, `configure` |\n\n### Classify\n\nClassify the latest reply before any other action.\n\n- `edit`: adds, removes, corrects, splits, combines, or replaces substance.\n- `accept`: affirms the current block and adds no fact.\n- `unknown`: the person says they do not know.\n- `question`: asks for an explanation.\n- `decline`: the person stops or cancels.\n\nOn a starting point, \"looks good\" is `accept`.\n\n### summary\n\nList every completed provider group.\n\n**Onboarding is now complete for [Name]**\n\n1. **[Provider]:** [ADR id] → [RA id] → [RI id] ([capabilities])\n\nIf you'd like to review your Decision, Reference Architecture or Reference Implementation records, just say so.\n\n**Where would you like to go next?**\n\n`highway-assessment` is a good choice. Highway can perform an assessment of your current business context and provide recommendations you can act on today.\n\nRun highway-help to explore what Highway can help you do.\n\n[When `highway-codify-config` handed off this onboarding for a platform: Run `highway-codify-config [Platform]` to finish adding [Platform].]\n\nWhen the person asks to review a record, go to `review`. When they choose a next step, follow that step. Do not start another record.\n\n### review\n\nWhen the person names a record, show that record.\n\nWhen the person asks to review and names nothing, list every completed provider in the order they were created.\n\n**[Provider]**\n- Decision: [ADR id]\n- Reference Architecture: [RA id]\n- Reference Implementation: [RI id]\n\n**Which would you like to review, or would you like to review all?**\n\n- They name a record: show that record.\n- They name a provider: show that provider's Decision, then its Reference Architecture, then its Reference Implementation.\n- They ask to review all: for each provider, in creation order, show the Decision, then the Reference Architecture, then the Reference Implementation.\n- `question`: answer, then re-emit the list and this question. Stay on `review`.\n- `unknown`: re-emit the list and this question. Stay on `review`.\n- `decline`: return to the summary question.\n\nShow one record at a time. When the next record belongs to a different provider than the record just shown, emit this before that provider's first record:\n\nReview the [provider] records Highway has prepared for you.\n\nBefore every record, including the first record and the next record for the same provider, emit this level of bold:\n\n**Review the [record] Highway has prepared:**\n\n[record] is Decision, Reference Architecture, or Reference Implementation. Then show that record. After the record, ask:\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so.\n\n- `edit`: emit one consequence sentence. Update that record in its existing structure. Re-emit the record hand-off, that record, and this question. Stay on `review`.\n- `accept`: when another record remains in this review, show the next record. When the next record belongs to a different provider, emit the provider hand-off first. When none remain, return to the summary question.\n- `question`: answer, then re-emit the record hand-off, that record, and this question. Stay on `review`.\n- `unknown`: re-emit the record hand-off, that record, and this question. Stay on `review`.\n- `decline`: return to the summary question.\n\n## Verification\n\n- The provider queue starts only after the mapping is accepted.\n- The summary tells the person they can review a Decision, Reference Architecture, or Reference Implementation.\n- A review that names nothing lists each provider's Decision, Reference Architecture, and Reference Implementation, and asks which to review or whether to review all.\n- Review all shows one record at a time: for each provider, the Decision, then the Reference Architecture, then the Reference Implementation.\n- Each record is introduced with **Review the [record] Highway has prepared:**\n- A later provider is introduced with \"Review the [provider] records Highway has prepared for you.\"\n- A shown record asks **What would you add, correct, or remove?**\n- No Request or Discovery record is created.\n- A failed architecture or implementation does not claim onboarding is complete.\n- No inventory file is written.\n- After lineage, each yes, in the order asked, emits \"Let's configure how highway-codify uses [Platform].\" and follows `highway-codify-config` for that platform with the return step `configure`. The summary follows the last return and has no `highway-codify-config [Platform]` configure pointer.\n- An onboarding handed off by `highway-codify-config` does not ask to configure that platform, and its summary ends with the line to finish adding that platform.\n- The summary recommends `highway-assessment`, then `highway-help`.\n\n## Error Handling\n\n- An unreadable website continues from accepted repository evidence and says the site could not be read.\n- A failed ADR write leaves existing ADR bytes unchanged and does not create an architecture.\n- A failed architecture or implementation write keeps earlier records and names the record that could not be written.\n- A capability the person says does not exist is removed and is not mapped.\n- A provider the person says does not exist is marked `Does not exist` and does not create a provider decision.\n\n## Example\n\n`\u002Fhighway-onboarding`","# highway-onboarding\n\n## Purpose\n\nBrings existing platforms into Highway by validating capabilities, mapping them to providers, and orchestrating one decision, architecture, and implementation for each provider group.\n\n## When to use\n\n- The person invokes `highway-onboarding`.\n- Accepted Profile, Objectives, Controls, NFRs, or existing architecture records can ground a capability.\n\n## When not to use\n\nDo not create a technology, platform, provider, or application inventory. `library\u002Fcoding-standards\u002Fcodify-platforms.md` lists only platforms that can start automation and is not that inventory.\nDo not create a Request, Discovery, or synthetic `DISC` record.\nDo not change Profile, Objectives, Controls, or NFRs.\nDo not authorize deployment.\nDo not authorize the agent platform to act on its own.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\n\n## Inputs\n\n- Accepted Profile, Objectives, Controls, NFRs, ADRs, architectures, and implementations when present.\n- Material the person supplies, including a website when retrieval is available.\n- `adrs\u002Fadrs.md`.\n- `highway-adr`.\n- `highway-architecture`.\n- `highway-implementation`.\n- `library\u002Fcoding-standards\u002Fcodify-platforms.md`.\n- The highway-experience skill, activated first.\n\n## Outputs\n\n- One accepted ADR, Reference Architecture, and Reference Implementation per provider group, written by `highway-adr`, `highway-architecture`, and `highway-implementation`.\n- One lineage that lists every completed provider, then one summary.\n- One row in `library\u002Fcoding-standards\u002Fcodify-platforms.md`, with blank When to use and When not to use, written by `highway-implementation` for each implementation that can start automation.\n- No inventory file. The capability queue and the provider queue are not written.\n\n## Procedure\n\nActivate the highway-experience skill before any output the person sees, and follow it for Highway's identity, the Experience Standard, and the storage contract.\n\nBefore the first question, confirm these seeded files exist: `adrs\u002Fadrs.md`, `architectures\u002Farchitectures.md`, `implementations\u002Fimplementations.md`, `implementations\u002Fcapabilities.md`, `library\u002Fcoding-standards\u002Fcodify-platforms.md`.\nWhen any is absent, emit the message below exactly, stop, and write nothing.\n\n**Oops... we need to setup your repository.**\n\nHighway needs to gather your organizational preferences and set up your repository. Run highway-setup to get started.\n\nEmit only the active template. Follow the steps in this order: `overview`, `capabilities`, `map`, `mapping`, `orchestrate`, `lineage`, `configure`, then `summary`. Review happens only when the person asks for it from the summary.\n\nOnboarding keeps two queues. The capability queue holds accepted capabilities that still need a platform. The provider queue holds accepted providers that still need a decision. Neither queue is written. Queue membership is not an ADR, an architecture, or an implementation.\n\nA capability may map to more than one provider. A provider may serve more than one capability. One mapping may be primary. A capability the person says does not exist is removed. A provider the person says does not exist is marked `Does not exist` and does not enter the provider queue.\n\nBefore a step in this table, read its file and follow it to the end.\n\n| File | Steps |\n| --- | --- |\n| `references\u002Fproposal.md` | `overview`, `capabilities`, `map`, `mapping` |\n| `references\u002Forchestrate.md` | `orchestrate`, `lineage`, `configure` |\n\n### Classify\n\nClassify the latest reply before any other action.\n\n- `edit`: adds, removes, corrects, splits, combines, or replaces substance.\n- `accept`: affirms the current block and adds no fact.\n- `unknown`: the person says they do not know.\n- `question`: asks for an explanation.\n- `decline`: the person stops or cancels.\n\nOn a starting point, \"looks good\" is `accept`.\n\n### summary\n\nList every completed provider group.\n\n**Onboarding is now complete for [Name]**\n\n1. **[Provider]:** [ADR id] → [RA id] → [RI id] ([capabilities])\n\nIf you'd like to review your Decision, Reference Architecture or Reference Implementation records, just say so.\n\n**Where would you like to go next?**\n\n`highway-assessment` is a good choice. Highway can perform an assessment of your current business context and provide recommendations you can act on today.\n\nRun highway-help to explore what Highway can help you do.\n\n[When `highway-codify-config` handed off this onboarding for a platform: Run `highway-codify-config [Platform]` to finish adding [Platform].]\n\nWhen the person asks to review a record, go to `review`. When they choose a next step, follow that step. Do not start another record.\n\n### review\n\nWhen the person names a record, show that record.\n\nWhen the person asks to review and names nothing, list every completed provider in the order they were created.\n\n**[Provider]**\n- Decision: [ADR id]\n- Reference Architecture: [RA id]\n- Reference Implementation: [RI id]\n\n**Which would you like to review, or would you like to review all?**\n\n- They name a record: show that record.\n- They name a provider: show that provider's Decision, then its Reference Architecture, then its Reference Implementation.\n- They ask to review all: for each provider, in creation order, show the Decision, then the Reference Architecture, then the Reference Implementation.\n- `question`: answer, then re-emit the list and this question. Stay on `review`.\n- `unknown`: re-emit the list and this question. Stay on `review`.\n- `decline`: return to the summary question.\n\nShow one record at a time. When the next record belongs to a different provider than the record just shown, emit this before that provider's first record:\n\nReview the [provider] records Highway has prepared for you.\n\nBefore every record, including the first record and the next record for the same provider, emit this level of bold:\n\n**Review the [record] Highway has prepared:**\n\n[record] is Decision, Reference Architecture, or Reference Implementation. Then show that record. After the record, ask:\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so.\n\n- `edit`: emit one consequence sentence. Update that record in its existing structure. Re-emit the record hand-off, that record, and this question. Stay on `review`.\n- `accept`: when another record remains in this review, show the next record. When the next record belongs to a different provider, emit the provider hand-off first. When none remain, return to the summary question.\n- `question`: answer, then re-emit the record hand-off, that record, and this question. Stay on `review`.\n- `unknown`: re-emit the record hand-off, that record, and this question. Stay on `review`.\n- `decline`: return to the summary question.\n\n## Verification\n\n- The provider queue starts only after the mapping is accepted.\n- The summary tells the person they can review a Decision, Reference Architecture, or Reference Implementation.\n- A review that names nothing lists each provider's Decision, Reference Architecture, and Reference Implementation, and asks which to review or whether to review all.\n- Review all shows one record at a time: for each provider, the Decision, then the Reference Architecture, then the Reference Implementation.\n- Each record is introduced with **Review the [record] Highway has prepared:**\n- A later provider is introduced with \"Review the [provider] records Highway has prepared for you.\"\n- A shown record asks **What would you add, correct, or remove?**\n- No Request or Discovery record is created.\n- A failed architecture or implementation does not claim onboarding is complete.\n- No inventory file is written.\n- After lineage, each yes, in the order asked, emits \"Let's configure how highway-codify uses [Platform].\" and follows `highway-codify-config` for that platform with the return step `configure`. The summary follows the last return and has no `highway-codify-config [Platform]` configure pointer.\n- An onboarding handed off by `highway-codify-config` does not ask to configure that platform, and its summary ends with the line to finish adding that platform.\n- The summary recommends `highway-assessment`, then `highway-help`.\n\n## Error Handling\n\n- An unreadable website continues from accepted repository evidence and says the site could not be read.\n- A failed ADR write leaves existing ADR bytes unchanged and does not create an architecture.\n- A failed architecture or implementation write keeps earlier records and names the record that could not be written.\n- A capability the person says does not exist is removed and is not mapped.\n- A provider the person says does not exist is marked `Does not exist` and does not create a provider decision.\n\n## Example\n\n`\u002Fhighway-onboarding`",{"name":5,"license":14,"metadata":23,"description":7},{"usage":24,"version":25},"Run highway-onboarding.","10.13.0","main","40844ce31770431531f69285c7c0b5372161e0f4",".github\u002Fskills\u002Fhighway-onboarding","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills","https:\u002F\u002Fgithub.com\u002Fjacob623","2026-11-15 03:33:56",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add jacob623\u002Fhighway-skills --skill highway-onboarding",{"tool":38,"command":39},"bunx","bunx skills add jacob623\u002Fhighway-skills --skill highway-onboarding",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jacob623\u002Fhighway-skills --skill highway-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhighway-onboarding\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Forchestrate.md","REFERENCE","参考文档",4281,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhighway-onboarding\u002Freferences\u002Forchestrate.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fproposal.md",8696,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhighway-onboarding\u002Freferences\u002Fproposal.md",[57,64,71,77,83,90],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7C7Z5YQ3BWYB6H1P0ZDY484","valid-skill","A fully conformant fixture skill used only by the tests to validate the authoring framework. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid-skill\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7C7YQQ3HSFB6DWS47BNYK95","invalid_skill_bad_id","Fixture whose directory name is not kebab-case, to test the id failure path. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid_skill_bad_id\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7C7YJWDD4GWB5VYBXWNBVK0","invalid-skill-undeclared-key","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-undeclared-key\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7C7YFDNBRCDRGSV496BHESC","invalid-skill-short-description","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-short-description\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7C7YB56VE90KD00WMYY84XF","invalid-skill-relative-link","Fixture whose body carries a relative Markdown link target, to test the P8.7 failure path. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-relative-link\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7C7Y6XJ9DXY6KVNYVB1VC7W","invalid-skill-nondeterministic-criterion","Fixture whose decision criteria depend on when they are read, to test the P6.4 failure path. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-nondeterministic-criterion\u002FSKILL.md",[],[]]