2.0 KiB
Pipelines maintenance
Consent (hard rule)
The operator owns this system. No change to it happens without their explicit consent in the current conversation: new pipelines or versions, definition and stage-prompt edits, orchestration scripts, briefs and the conventions they carry, the packaged skill and templates, deploys, installs and deletions. Read-only investigation and reporting need no consent. Ask first and name exactly what would change; a request for a fix is not consent for a particular mechanism.
When changing user-facing behavior or learning a confirmed runtime limitation,
update the relevant packaged OpenCode skill reference in
internal/author/skill/references/ in the same change. Keep SKILL.md a concise,
task-directed index: preserve ask-first authoring and never preload every reference.
Separate current capabilities, dated verification evidence, deployment state and
unimplemented ideas. Do not turn mocked or structural checks into live claims.
For new references, update internal/author/install.go's managed file inventory.
Run the author package tests: they check embedding, reference links, installation,
upgrades and protection of user modifications. Never hand-edit an installed copy
as the source of truth; refresh it with the current-source pipelines skill install
only when installation is requested. Do not deploy runtime changes merely because
the skill is updated. Keep README/topic docs and the packaged reference consistent.
Maintenance workflow
Top-level agents use the configured Pipelines maintenance - plan implement review
maintenance workflow for code changes. Inspect the retained plan/implement/review
outputs and diffs, execute the checks independently, and iterate on concrete
failures rather than trusting stage summaries. An executing stage performs its own
role directly and never recursively launches a workflow. If the workflow is
unavailable, ask instead of silently bypassing it. Never hardcode a disposable
server URL as a project default; the configured endpoint is authoritative.