ros2_agent_workspace

Host orchestrator that drives an issue through the full per-issue lifecycle — dispatches each phase (review-issue → plan-task → review-plan → implement → review-code → triage-reviews → address-findings) as a fresh-context sub-agent, reads each phase's progress.md entry to choose the next action, and pauses at user checkpoints. Local-first: the PR is created at the end, never auto-pushes or auto-merges without confirmation.

Evaluate a GitHub issue against workspace principles and ADRs before work begins. Records findings in progress.md and best-effort posts them as a comment on the issue.

Independent evaluation of a committed work plan before implementation begins. Checks scope, approach, principle alignment, consequences, and ROS conventions.

Activate deployment mode for a live field deployment. Discovers the project's deployment config, detects dev/field side via field_mode.sh, and either creates a new deployment, first-activates an existing one (worktree/main-tree + per-host log + issue-sync push), or resumes an ongoing one. Loads the urgency contract (sterile-cockpit / mitigate-before-diagnose / time-box) into the current agent session.

Close out a field deployment. Verifies dev-side access, finds the open deployment issue, collects field logs, interviews the operator for corrections, consolidates the dev log, reconciles field code via SHA-preserving merge and /import-field-changes, opens the wrap-up PR (Closes

Lead reviewer that orchestrates specialist sub-reviews (static analysis, governance, plan drift, adversarial) to evaluate a PR or pre-push diff. Scales review depth to change risk. Produces a unified structured report and persists findings to progress.md.

Work through the open action items from the latest review entry in progress.md — a

Generate a principles-aware work plan for an issue. Saves to `.agent/work-plans/` in the repo that owns the issue and commits as the first step on the feature branch.

Integrator — evaluate PR review comments (human and bot) together with the prior progress.md review timeline, against local code, principles, and ADRs. Includes CI check status. Classifies each finding as valid or false positive, flags cross-source confirmations, presents a fix plan, and persists a unified Integrated Review entry to progress.md.

Batch-import field changes from a secondary remote (e.g., gitcloud) back to GitHub for review. For each repo with remote-ahead commits, creates an issue, opens a draft PR, and pre-reviews the diff against the Quality Standard.

Track external projects for portable enhancements and interesting patterns. Supports fork-style file diffs and inspiration-style surveys with per-project digests.

Interactive audit and onboarding for project repos. Checks for CI, pre-commit, agent guide, GitHub settings, and labels. Offers to fix gaps or open issues.

Scan overlay repositories for GitHub issues, categorize them, flag stale items, and cross-reference with workspace tracking.

Scaffold, debug, and analyze test coverage for ROS 2 packages. Supports GTest, PyTest, and launch_testing.

Generate or update ROS 2 package documentation (README and API docs) by reading source code. Enforces the documentation verification workflow.

Evaluate and import external skills into the workspace. Checks for redundancy, format, safety, and source attribution before importing.

Scan workspace repos and generate project knowledge summaries for `.agents/workspace-context/`. Requires a GitHub issue and layer worktree on the target repo.

Check a project repo against workspace and project-level conventions. Reports governance coverage, documentation gaps, and test status.

Survey external sources on a topic and maintain living research digests. Workspace digest is tracked; project digest lives in the manifest repo.

Explore possibilities for a topic by combining research digests with project knowledge and governance context.

Check the workspace against its own standards. Find rules without enforcement, drifted ADRs, stale docs, and missing consequences. Run periodically.

Applies UNH CCOM/JHC official brand colors, typography, naming conventions, and editorial style to documentation and artifacts. Use when writing or updating project documentation, README files, web content, presentations, or any material that should reflect the Center's institutional identity.