highway-controls
Manages the repository-wide control baseline. Use when highway-setup delegates the control baseline, after Objectives finish or when setup runs again.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- highway-controls
- license
- Apache-2.0
- metadata
- { "usage": "Run highway-controls.", "version": "8.8.0" }
- description
- Manages the repository-wide control baseline. Use when highway-setup delegates the control baseline, after Objectives finish or when setup runs again.
02 资源文件 4
- 资产文件assets/control-catalog.md913 B
- 资产文件assets/control-record.md1.7 KB
- 参考文档references/proposal.md7.6 KB
- 参考文档references/record.md3.8 KB
03 SKILL.md 正文
highway-controls
Purpose
Collects controls when setup delegates this skill.
When to use
highway-setupdelegates this skill after Objectives returnsFinished.highway-setupdelegates this skill when setup runs again.
When not to use
Do not create Objectives, NFRs, Capabilities, or governance rules. Do not treat a recommendation or a queued title as a captured Control. Do not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked. Do not emit Setup's safeguard transition. Setup already emitted it.
Inputs
library/knowledge/profile.mdwhen present.library/governance/objectives.mdandlibrary/objectives/when present.library/governance/controls.mdwhen present.library/governance/controls/CTL*.mdwhen present.assets/control-record.md.assets/control-catalog.md.- The highway-experience skill, activated first.
- Delegation from
highway-setup.
Outputs
The complete structure is assets/control-record.md and assets/control-catalog.md.
- Updated Control records and catalog after a review edit.
- New Control records and catalog after the guided flow writes them.
Finishedreturned tohighway-setupafter review acceptance or a successful guided write.Finishedis not shown to the person.- One closing line after review acceptance or a successful guided write, when the person ran this skill directly.
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.
Emit only the active template. Follow this order: review when the catalog exists; otherwise recommend, then queue or ask, then capture, then identifier, title when needed, and write. Both paths end at close. Follow the Highway Experience Standard for attribution and acceptance wording. Use the accepted Organization Name from the Profile. Use Repository Name when no Organization Name is accepted. Do not ask for Profile or Objective facts already accepted.
A Control is an enforceable safeguard: what must remain true. Do not write an Objective, a metric, or an implementation plan.
Before a step in this table, read its file and follow it to the end.
| File | Steps |
|---|---|
references/proposal.md |
recommend, more, queue, ask, capture |
references/record.md |
identifier, title, write |
Entry
- Read
library/governance/controls.md. Then read each active record it indexes atlibrary/governance/controls/[ID].md, with "Read a file". - If the catalog is present and readable, and every active row has a readable record, go to
review. - If the catalog is absent, go to
recommendwhenprofile.mdandlibrary/governance/objectives.mdare readable. Otherwise go toask. - If the catalog is unreadable, or an active row has no readable record, stop. Say the Controls could not be read. Leave every file unchanged. Do not return
Finished.
A removed row has no record file. Do not treat that as unreadable.
Classify
Classify the latest reply before any other action.
select-all: affirms every recommendation in the current set and adds no separate safeguard.select: names one or more recommendations in the current set, by title or by number.own: supplies a safeguard that is not a displayed title.more: asks for more suggestions.review-now: asks to review the queue, or affirms a queue prompt that asks whether to review.edit: adds, removes, corrects, splits, combines, or replaces substance.accept: affirms the current capture or review body and adds no fact.unknown: the person says they do not know.question: the person asks for an explanation.decline: the person explicitly drops the active set.
On a recommendation set, "looks good" is select-all. On a queue prompt that asks whether to review, "looks good" and "let's review" are review-now. On a capture or on review, "looks good" is accept.
review
Show every active Control in catalog order. Omit frontmatter, omit the catalog, and omit removed rows. For each Control emit:
[Title]: [Statement]
Why it matters: [Rationale]
Put --- between Controls. Do not put --- after the last Control.
When no active Control is recorded, emit: No controls are recorded yet.
Then emit the validation block.
edit: emit one consequence sentence. Apply the edit to the named Control. Preserve every Control the person left unchanged. An added safeguard becomes a new record. A removed Control deletes that record file and keeps its catalog row with statusremoved, so the id stays taken. Derive the id before writing. When the id is taken for a different title, go totitleand do not write yet. Otherwise rewrite the affected records and the catalog. Show the updated Controls and emit the validation block. Stay onreview.accept: go toclose.unknown: show the Controls and emit the validation block. Stay onreview.question: answer in one sentence. Show the Controls and emit the validation block. Stay onreview.
Validation block:
What would you add, correct, or remove?
If this is accurate, just say so.
close
When highway-setup delegated this skill, return Finished. Emit nothing else.
Otherwise emit one line and stop. When at least one Control is active, emit:
Your Controls are recorded.
When no Control is active, emit:
No Controls are recorded yet. Run highway-controls when you have one to add.
Verification
- An existing readable catalog is shown with What would you add, correct, or remove?
- Acceptance of that review goes to
close. - Run by
highway-setup,closereturnsFinishedand emits nothing else. Run directly, it emits one closing line and no question. - A review edit rewrites the affected record and catalog, then shows the updated Controls with the same question.
- An absent catalog and readable Profile and Objectives begin with a recommendation set.
- Records and the catalog are written once, after the set is accepted or declined.
- Written records match
assets/control-record.md. - The written catalog matches
assets/control-catalog.md. - Setup receives
Finishedand the person does not see that word.
Error Handling
- An unreadable catalog or active record stops the skill, leaves every file unchanged, and does not return
Finished. - A failed review rewrite leaves every file unchanged, says what failed in terms the person can act on, and stays on
review. - A failed guided write leaves the baseline unchanged, says what failed in terms the person can act on, and stays on
write. - An absent or unreadable Profile or Objectives catalog uses
askand does not invent organizational facts.
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.