highway-profile
Manages the repository-wide organizational Profile and its contextual guidance. Use when highway-setup delegates the Profile, at the start of setup or when setup runs again.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- highway-profile
- license
- Apache-2.0
- metadata
- { "usage": "Run highway-profile.", "version": "14.5.0" }
- description
- Manages the repository-wide organizational Profile and its contextual guidance. Use when highway-setup delegates the Profile, at the start of setup or when setup runs again.
02 资源文件 1
- 资产文件assets/profile-record.md2.9 KB
03 SKILL.md 正文
highway-profile
Purpose
Collects the organizational Profile when setup delegates this skill.
When to use
highway-setupdelegates this skill at the start of setup.highway-setupdelegates this skill when setup runs again.
When not to use
Do not create Controls, NFRs, Objectives, governance rules, or Highway identity. Do not treat proposed evidence as organizational fact. Do not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.
Inputs
library/knowledge/profile.mdwhen present.assets/profile-record.md.- The highway-experience skill, activated first.
- Delegation from
highway-setup. - Material the person supplies, including a public website when retrieval is available.
Outputs
The complete structure is assets/profile-record.md.
- An updated
library/knowledge/profile.mdafter a review edit. - A new
library/knowledge/profile.mdafter the guided flow writes it. Finishedreturned tohighway-setupafter review acceptance or a successful guided write.Finishedis not shown to the person.
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. Repository ownership stays with the person.
X2.21 does not apply. The accepted proposal bullets are the retained domain, so Profile does not show a second capture heading.
Emit only the active template. Follow this order: review when profile.md exists; otherwise name, offer, Identity, Vision, Competitive Path, Guiding Principles, then write. Follow the Highway Experience Standard for attribution and acceptance wording. Use accepted Organization Name in templates. Use Repository Name until an Organization Name is accepted. Repository Name does not become Organization Name.
Entry
- Read
library/knowledge/profile.mdfrom the repository root. - If
library/knowledge/profile.mdis present and readable, go toreview. - If that file is absent, go to
name. - If that file is present and unreadable, stop. Say the Profile could not be read. Leave the file unchanged. Do not return
Finished.
Classify
Classify the latest reply before any other action.
edit: adds, removes, corrects, splits, combines, or replaces substance.accept: affirms the current block and adds no fact.unknown: the person says they do not know.question: the person asks for an explanation.decline: the person explicitly leaves the active domain unresolved.
unknown is not decline.
review
Show the file body. Omit frontmatter. Then emit the validation block.
edit: emit one consequence sentence. Rewrite the file with that edit. Preserve every section the person left unchanged. Show the updated body and emit the validation block. Stay onreview.accept: returnFinished. Emit nothing else.unknown: show the body and emit the validation block. Stay onreview.question: answer in one sentence. Show the body and emit the validation block. Stay onreview.
Validation block:
What would you add, correct, or remove?
If this is accurate, just say so.
name
Emit:
Let's get to know your organization
What would you like to call your Highway repository?
Using your organization's name is often a good choice.
Store the reply as Repository Name. Go to offer.
offer
Emit:
Do you already have something I can use to start understanding [Repository Name]?
You can share a website link, an overview or description, a strategy document, or an assistant export. If you don't have anything handy, say so and we can work through it together.
- The person has nothing: go to
identity.ask. - Text, with or without a link: the text is supplied material for every domain. Store a link in it as Organization URL and retrieve it. When the link cannot be read, say so once and continue with the text. Go to
identity.reviewwhen the material supports at least one Identity finding. Otherwise go toidentity.ask. - A link or document with no other text: retrieve it. Store a supplied link as Organization URL. Go to
identity.reviewwhen it supports at least one Identity finding. Otherwise go toidentity.ask. - A link with no other text, when retrieval is unavailable: go to
identity.ask. Do not mention the missing retrieval.
Facts from supplied material stay proposed until accepted in that domain's proposal.
Use supplied material across every later domain. Do not ask the person to repeat it. Do not use model memory or prior-agent memory as organizational evidence.
Domain order
Run Identity, Vision, Competitive Path, then Guiding Principles.
Each domain uses start when a proposal can be shown. Identity uses ask only when no supported starting point exists. Vision, Competitive Path, and Guiding Principles always use start. Do not put a question template in the same message as a starting point.
identity.revieworidentity.askvision.startpath.startprinciples.startwrite
Hold each accepted bullet list until write. Do not write the file before write.
Shared replies
Apply these on every domain step.
edit: emit one sentence stating a consequence the person did not state. Re-emit the same template with the edit applied. Stay.acceptonrevieworstart: hold the current bullets. Advance.acceptonidentity.ask: hold the answer as the Identity bullets. Advance. Do not emit a capture paragraph.unknownonrevieworstart: re-emit that template. Stay.unknownonidentity.ask: re-emit the question template. Stay.question: answer in one sentence. Re-emit the same template. Stay.decline: store no narrative for this domain. Advance.
unknown does not finish a domain.
Domain rules
Identity states who the organization is and what it provides. Omit a technology inventory.
Vision states the future the organization is creating. Omit method, sequencing, and organizational approach. When the person supplies those, emit this sentence, hold that material for Competitive Path, and stay on Vision:
That is an important part of how you will get there. I will carry it forward when we reach Competitive Path, and return to Vision.
Competitive Path states the broad approach toward the accepted Vision. Omit Controls, NFRs, safeguards, architecture, implementation requirements, and plans. Keep only the broad strategic meaning of volunteered detail.
Guiding Principles state enduring decision-making values. Do not write an enforceable Control.
Open Vision, Competitive Path, and Guiding Principles by naming accepted substance from the previous captured domain. Always emit the proposal. Infer a slot, including the Competitive Path tradeoff, from accepted context when the person has not stated it. Do not replace the proposal with a question.
Templates
Identity review:
Here's what Highway believes [Name] does.
[Short activity name]: [One sentence: who receives it, and what they receive.]
Emit 3 to 6 findings. Omit a finding the source does not support.
Identity question:
What does [Name] do?
If you don't know, say "I don't know" and we'll work through it together.
Vision opening and starting point:
Emit this level-3 heading, then the sentence under it:
Where you're going
With [accepted Identity substance], let's explore the future you are working to create.
Here is a proposed starting point for your Vision:
-
Future Direction
[Inferred from accepted context.]
-
Desired Impact
[Inferred from accepted context.]
-
Future State
[Inferred from accepted context.]
What would you add, correct, or remove?
If this is accurate, just say so. If you don't know, say "I don't know" and we'll work through it together.
Competitive Path opening and starting point:
Emit this level-3 heading, then the sentence under it:
How you'll get there
To advance toward [accepted Vision substance], let's explore how [Name] plans to get there.
Here is a proposed starting point for your Competitive Path:
-
Primary Approach
[Inferred from accepted context.]
-
Strategic Advantage
[Inferred from accepted context.]
-
Important Tradeoff
[Inferred from accepted context.]
What would you add, correct, or remove?
If this is accurate, just say so. If you don't know, say "I don't know" and we'll work through it together.
Guiding Principles opening and starting point:
Emit this level-3 heading, then the sentence under it:
What will guide your decisions
With your competitive path grounded in [accepted Competitive Path substance], let's explore what principles guide [Name]'s decisions.
Here is a proposed starting point for your Guiding Principles:
-
[Short principle name]
[Accepted-evidence decision-making value.]
Emit 3 to 5 principles. Infer each principle from accepted context when the person has not stated it. The label is a short principle name.
What would you add, correct, or remove?
If this is accurate, just say so. If you don't know, say "I don't know" and we'll work through it together.
When the previous domain was declined, replace the bracketed accepted substance with: Nothing has been accepted for [previous domain] yet.
Bold only the question in each block.
write
Write library/knowledge/profile.md from the repository root once, in the shape required by assets/profile-record.md. Create library/knowledge/ when it is absent.
- A captured domain is
discussedand its narrative section contains the held bullets. Omit a term the person rejected. - A declined domain is
boundedand its narrative section is omitted. - Write
## Contextwith Repository Name. - Write Organization URL, Organization Name, and Organizational Context only when the person supplied or accepted that value.
- Emit nothing after a successful write.
- Return
Finished.
Verification
- An existing readable
profile.mdis shown with What would you add, correct, or remove? - Acceptance of that review returns
Finishedand emits nothing else. - A review edit rewrites the file and shows the updated body with the same question.
- An absent
profile.mdbegins at the repository-name template. - A starting-point message contains no canonical question.
- The file is written once, after Guiding Principles is captured or declined.
- A successful guided write returns
Finishedand emits nothing else. - The written file matches
assets/profile-record.md. - Setup receives
Finishedand the person does not see that word.
Error Handling
- An unreadable
profile.mdstops the skill, leaves the file unchanged, and does not returnFinished. - A failed review rewrite leaves the file unchanged, says what failed in terms the person can act on, and stays on
review. - A failed guided write leaves the file absent, says what failed in terms the person can act on, and stays on
write. - Pasted text is supplied material. A link in it that cannot be read is named once, and the skill continues with the text.
- A link with no other text and no retrieval continues at
identity.askwithout mentioning the missing capability.
Example
/highway-setup
04 同仓库更多 Skills
valid-skill
A fully conformant fixture skill used only by the tests to validate the authoring framework. Use when the tests exercise the validator.
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.
invalid-skill-undeclared-key
A fully conformant fixture skill used only by the tests to validate the authoring framework. Use when the tests exercise the validator.
invalid-skill-short-description
暂无简介
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.
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.