vloop-architect
The design act for this repo — the /vloop:create-brief skill, plus what this repository adds to it (the roadmap row, the domain's invariants cited by ID, the constraints every brief here carries). Use in an interactive session when the operator asks to write, draft, revise or scope the next brief. Running, verifying and closing briefs belong to the vloop-operator skill.
- License 许可
- MIT
- 所属仓库
- mvelosop/vloop
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- vloop-architect
- description
- The design act for this repo — the /vloop:create-brief skill, plus what this repository adds to it (the roadmap row, the domain's invariants cited by ID, the constraints every brief here carries). Use in an interactive session when the operator asks to write, draft, revise or scope the next brief. Running, verifying and closing briefs belong to the vloop-operator skill.
03 SKILL.md 正文
The design act here
Follow /vloop:create-brief for the whole act: find the
documentation, survey, settle forks with the operator, write from the template,
check it, have it reviewed with /vloop:review-brief, hand over at draft.
Until a release ships them, read them from plugin/skills/create-brief/ and
plugin/skills/review-brief/. This skill only adds what is particular to this
repository.
Scope comes from the roadmap
The brief's row in docs/design-notes/vloop-roadmap.md says what it owns; the
rows after it are its out-of-scope list. At hand-over, point the row at the
brief.
Bind by invariant
Walk the domain (docs/domain/README-domain.md → domain-model.md → the
context and entity pages each part of the brief touches) and cite the
invariants that apply by ID, one path per entry:
- `docs/domain/domain-model.md` — B-4 and M-2: where the estimate is read; what counts as a line
- `docs/domain/execution/task.md` — the gate and gate history, for the task verify changes
What every brief here carries
- Real numbers from the telemetry (
.vloop/state/runs/,vloop metrics), never from hand-rounded run records. B1–B7's history is the shell loop's, under.loop/state/runs/. - A real-data check where the slice can read this repository's own history.
- These lessons as constraints, verbatim where they apply: gates run on macOS's
BSD tools; sessions never move refs; tests build their fixtures in temporary
directories and address them with
git -C. - In
vloop brief check, un-backtick paths that exist only after the run.
04 同仓库更多 Skills
work
Do exactly one task of the autonomous loop's plan and report on it. Invoked once per iteration by the driver as /vloop:work <task id>.
verify
Verify the built result of a whole run against its brief, in three passes, and report findings as verify/v2. Invoked once per complete run by the driver as /vloop:verify, in a session separate from the work and the reviews.
review
Independently verify one completed task of the autonomous loop and return a verdict. Invoked once per iteration by the driver as /vloop:review <task id>, in a session separate from the work.
review-brief
Independently review a vloop brief before it is marked ready — facts against the code, internal consistency, conflicts with the repository's own rules, decisions the author took that the operator has not approved, and whether the loop can actually run it — and return a verdict with findings. Use in a session separate from the one that wrote the brief, when asked to review a brief, or before running a brief that the same operator session wrote.
plan
Decompose a brief into .vloop/state/state.json — the task list the autonomous loop executes. Invoked once per run by the driver as /vloop:plan <brief path>.
operate
The operator's playbook — from a ready brief, check the repository, run it with vloop on a work branch, handle halts, verify the result independently, record defects and interventions, close the brief and merge. Use in an interactive session when asked to run, resume, verify, close or merge a brief, or what to do about a halt or a finding. Writing briefs is /vloop:create-brief's.