AI Agent Workflow Collection

Create or revise repository AGENTS.md files using a progressive-disclosure, dispatcher-style structure. Use when an agent needs to author or edit a top-level or directory-local AGENTS.md, convert a long instruction file into task-oriented "Start Here for ..." sections, add a concise "Must Follow" section with Always/Never rules, improve skill-discovery cues, or decide whether guidance belongs in root AGENTS.md, deeper docs, local AGENTS.md, or a repository-local skill.

Create or revise repository ARCHITECTURE.md files as short, stable architecture codemaps. Use when an agent needs to author or edit ARCHITECTURE.md, restructure an architecture document around a bird's-eye view and code map, clarify system boundaries, add architectural invariants or cross-cutting concerns, or decide which implementation detail should stay out of ARCHITECTURE.md and live in deeper design documents instead.

Handle Dependabot dependency update work, especially grouped updates, peer-dependency conflicts, lockfile refreshes, and validation for npm or other package-manager changes. Use when an agent needs to review, implement, test, or explain a dependency bump PR; decide whether related packages should be grouped; verify whether plugins, adapters, or companion packages can unblock a failed upgrade; or summarize why an attempted bump could not be made safely.

Create or revise Markdown description frontmatter so docgarden match routes agents to the right repository documents. Use when adding a new routed Markdown document, updating existing frontmatter, fixing noisy or missing match results, tuning skills or docs discovery, or making descriptions more query-aligned without loading document bodies.

Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan.

Implement from an active plan or ExecPlan while keeping it up to date. Use when an agent needs to implement the active plan, continue plan-driven work, resume the current plan, or carry out an existing ExecPlan.

Create, update, revise, reopen, or rescope a plan or ExecPlan using docs/PLANS.md. Use when an agent needs to create a plan, plan a change, update the plan with new requirements, or rewrite an active ExecPlan.