AGENT SKILL

highway-setup

Orchestrates initial highway setup through the owning governance skills. Use when the person sets up highway in a repository for the first time, or runs setup again to revise it.

License 许可
Apache-2.0
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
highway-setup
license
Apache-2.0
metadata
{ "usage": "Run highway-setup.", "version": "10.4.0" }
description
Orchestrates initial highway setup through the owning governance skills. Use when the person sets up highway in a repository for the first time, or runs setup again to revise it.

02 资源文件 12

03 SKILL.md 正文

highway-setup

Purpose

Seeds the project's catalogs, then orchestrates Profile, Objectives, Controls, and NFRs in order when the person runs setup.

When to use

  • The person invokes highway-setup and library/knowledge/profile.md is absent.
  • The person invokes highway-setup again after a prior setup run.

When not to use

Do not collect Profile, Objective, Control, or NFR evidence. Do not write Profile, Objective, Control, or NFR records or catalogs. Do not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked. Do not show Finished to the person.

Inputs

  • highway-profile.
  • highway-objectives.
  • highway-controls.
  • highway-nfrs.
  • library/knowledge/profile.md when present.
  • The seeded files' skeletons in assets/, one per row of the Seed table.
  • The highway-experience skill, activated first.
  • The person's request to run setup.

Outputs

  • The welcome, once, when Profile has not been written.
  • One domain transition before Objectives, Controls, and NFRs.
  • The closing conclusion, once, after NFRs returns Finished.
  • Each seeded file that was absent, written from its asset, such as requests/requests.md from assets/request-catalog.md.

Procedure

Activate the highway-experience skill before any output the person sees, and follow it for Highway's identity, the Experience Standard, and the storage contract.

User-visible interaction follows the Highway Experience Standard.

Seed first. Then delegate each owner in this order: Profile, Objectives, Controls, NFRs. Stay with the current owner until it returns Finished. Render that owner's messages as written. Do not answer its question, restate its recommendations, or add a second question.

Finished is the only result that advances. Do not show that word. An owner that stops without Finished ends Setup. Do not delegate a later owner, and do not emit the conclusion.

Seed

Seed in every setup run, after the storage contract's mode check and before the welcome.

For each row below, when the project file is absent, write it from the asset unchanged. Write every absent file as one group. Do not change a file that exists. Emit nothing for this step.

Asset Project file
assets/request-catalog.md requests/requests.md
assets/discovery-catalog.md discoveries/discoveries.md
assets/adr-catalog.md adrs/adrs.md
assets/architecture-catalog.md architectures/architectures.md
assets/implementation-catalog.md implementations/implementations.md
assets/capability-catalog.md implementations/capabilities.md
assets/codify-catalog.md code/code.md
assets/codify-integrations.md code/integrations.md
assets/codify-platforms.md library/coding-standards/codify-platforms.md
assets/coding-standards-catalog.md library/coding-standards/coding-standards.md
assets/assessment-findings.md library/knowledge/assessment-findings.md
assets/storage.md library/knowledge/storage.md

Welcome

When library/knowledge/profile.md is absent, emit the lines below before Profile. Emit "Welcome to Highway" as a level-2 heading and "During setup we'll:" as a level-3 heading. Emit every other line as written. Do not emit the welcome when that file exists.

Welcome to Highway Turn organizational knowledge into connected decisions. Your context stays yours.

Highway builds on information you choose to accept into your repository. Your repository remains the authoritative source of truth, and you retain ownership of the context and artifacts created through Highway.


During setup we'll:

  • Learn about your organization, where you'd like to go, how you plan to get there, and what principles guide decisions.
  • Identify important business outcomes worth pursuing.
  • Establish safeguards that future technology decisions should respect.
  • Define operational expectations for how future solutions should behave.

You don't need to have everything figured out in advance. We'll build this foundation together, and you can refine it over time as your organization evolves.

Now, let's get started.


Then delegate highway-profile.

Profile

Delegate highway-profile. Profile opens the organization conversation. Do not add a transition before it.

When Profile returns Finished, emit the Objectives transition and delegate highway-objectives in that same moment.

Objectives


Let's identify some outcomes worth pursuing.

These give Highway something concrete to connect future decisions back to.

When Objectives returns Finished, emit the Controls transition and delegate highway-controls.

Controls


Now let's establish the safeguards that should guide future technology decisions.

These help Highway keep future recommendations aligned with what needs to remain true.

When Controls returns Finished, emit the NFR transition and delegate highway-nfrs.

NFRs


Now let's consider the operational expectations future solutions should meet.

These help connect your safeguards to how solutions need to behave in practice.

When NFRs returns Finished, emit the conclusion.

Conclusion

Emit this once.

Your foundational Highway context is now in place.

Highway now has organizational context, business objectives, safeguards, and operational expectations it can build on in future work.

Where would you like to go next?

Run highway-onboarding to inform Highway of your current technology landscape. This aids Highway in providing cohesive recommendations.

Run highway-help to explore what Highway can help you do.

Resume

Every highway-setup run starts at Seed, then Profile. Setup stores no checkpoint. Seeding writes only absent files, so a later run keeps every catalog as it is. When profile.md already exists, skip the welcome and still delegate Profile, then Objectives, Controls, and NFRs. Each owner reviews what it already holds before returning Finished.

Verification

  • Seeding runs before the welcome in every run.
  • Seeding writes only absent seeded files, each from its asset.
  • Seeding changes no existing file.
  • Seeding emits nothing.
  • Owner order is Profile, Objectives, Controls, NFRs.
  • The welcome is emitted once, and only when profile.md is absent.
  • Profile is always delegated.
  • Each later owner is delegated only after the previous owner returns Finished.
  • The Objectives, Controls, and NFR transitions are each emitted once, directly before that owner's first message.
  • Setup does not add a question to an owner's message.
  • Setup does not add a synthesis between owners.
  • Finished is not shown.
  • An owner that stops without Finished ends Setup before the next owner.
  • The conclusion is emitted once, after NFRs returns Finished.
  • The conclusion directs the person to highway-onboarding before highway-help.
  • Setup writes no file other than the seeded files.

Error Handling

  • A seeded file that cannot be written stops Setup before the welcome. Say which file could not be written and what the person can do next.
  • An owner that stops without Finished ends Setup. The owner's message is the person's explanation. Do not delegate a later owner and do not emit the conclusion.
  • An unexpected orchestration failure stops Setup without claiming completion and says what the person can do next.

Example

/highway-setup

04 同仓库更多 Skills