Three membership lists
New targets, complete historical membership and followed groups. Lists hold identities only; groups may overlap, and scans deduplicate their union.
Portable repository stewardship
Finish the work.
Keep it maintained.
A portable Skill for multi-agent harnesses: assemble Workers within scope and authority for discovery, investigation, delivery and ongoing follow-up. Keep state in Markdown.
Lists select scope.
Records preserve facts.
Minimal records
state.md holds current facts and actions; work.md holds actual outcomes. Read details at native sources. Scoped rules load as needed; unfinished.md is navigation only.
Portable workspace
Keep RepoStew_skills/, state/ and work/owner/repo/ in the selected workspace. Source lives in checkout/; releasing source preserves records.
Independent, private sources
Public source positions live in read-positions.md; mail positions stay private. Preserve native boundaries and read source bodies live, without copying an interaction database.
Complete scope.
Concise assignments.
Establish outcome, scope, authority and resources. The Coordinator uses assembly rules and templates to assign Workers. Dispatch, wait, integrate, continue, hand off or recover through native harness capabilities; continue by delta.
Five forms: discovery/admission, new audits, contribution reassessment, incremental feedback, recurring patrols. Capture and deduplicate followed issues, notifications/selected mail and open/unfinished objects under separate source positions.
Trace actual use and documents; establish contribution evidence. Discuss ordinary unsettled contracts. Every new security finding uses private reporting only, never public issues; retain protected evidence and blockers without an authorized private channel. Complete assigned audit coverage before grouped repair, validation and publication under target and safety gates; handle feedback, consolidate roots or withdraw within authority.
Maintainers perform authorized maintenance: triage issues, review/amend/merge PRs under current rights/settings, audit actual use/documents and revise code. Keep actual-use coverage and essential CI/tests. Assigned PR review adds no universal pre-publication gate.
Write minimal records; migrate only when authorized; reconcile, recover or reclassify history; publish reviewed backups when requested. Check resource disposition every pass. Separate coverage, delivery, resolution and release.
Keep authority explicit, execution serial by default and one writer per resource. Apply user-selected exclusions before selecting or continuing GitHub work; preserve existing objects/history. Prohibit defensive programming, trust internal contracts and retain necessary boundary checks. Trust usable finals, preserve private/unknown work and report incomplete outcomes accurately.
Harnesses supply execution; forge rules map native access. Roles own responsibilities, prompts own wording, and workspace Markdown owns state. Files grant no implicit authority, tasks or schedules.
Bounded patrols.
Reliable continuation.
Configurable baseline: hourly notifications/selected mail, followed issues every 6 hours, open/unfinished-object fallback every 24 hours. Continue unfinished batches before new ones; reuse unchanged evidence.
Advance positions only after complete capture and handling or reliable retention. Never send mail, change read/subscription state or expand mailbox scope. Cadence does not prove coverage. Paused jobs remain paused; private material, backups and resource disposition retain their authority boundaries.