refactor: decouple delivery agents to prepare-delivery plugin + repo-intel rename

[avifenesh]

Summary

• Rename git-map/repo-map plugin references to repo-intel across agent docs and adapter transforms
• Decouple delivery-specific agents and skills to the new prepare-delivery plugin:
  • Moved: delivery-validator, test-coverage-checker (agents), orchestrate-review, validate-delivery (skills)
  • All references updated from next-task:* to prepare-delivery:* in commands, hooks, CLAUDE.md, AGENTS.md, README.md, adapter-transforms
  • Deleted orphaned files after copy to prevent shadowing
• Added Cross-Plugin Dependencies table to README.md
• Updated CHANGELOG.md with unreleased entries

Motivation

Part of the composable delivery pipeline work. The new plugin architecture:

• /prepare-delivery - quality gates (deslop, review, validation, docs sync)
• /gate-and-ship - chains /prepare-delivery then /ship
• /next-task - full orchestrator, now references prepare-delivery for phases 8-11

Test plan

• Verify npm test passes
• Verify all prepare-delivery:* cross-plugin references resolve correctly
• Verify hooks.json decision tree uses correct agent prefixes
• Verify no bare delivery-validator or test-coverage-checker references remain

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the agent architecture by extracting delivery-related agents and skills into a dedicated prepare-delivery plugin. This change is a foundational step towards a more composable delivery pipeline, enhancing modularity and clarity within the system. It also standardizes the naming convention for repository intelligence components, improving consistency across the codebase.

Highlights

• Plugin Decoupling: Decoupled delivery-specific agents (delivery-validator, test-coverage-checker) and skills (orchestrate-review, validate-delivery) to a new prepare-delivery plugin.
• Reference Updates: Updated all internal cross-plugin references from next-task:* to prepare-delivery:* in commands, hooks, and documentation.
• Repository Intelligence Rename: Renamed git-map/repo-map plugin references to repo-intel across agent documentation and adapter transforms.
• Documentation Enhancements: Added a 'Cross-Plugin Dependencies' table to README.md and updated CHANGELOG.md with unreleased entries reflecting these changes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the project by moving delivery validation and test coverage agents and skills (e.g., delivery-validator, test-coverage-checker, orchestrate-review, validate-delivery) into a new prepare-delivery plugin. This change involves updating all internal references to these components with the prepare-delivery: prefix and consistently renaming git-map/repo-map references to repo-intel throughout the codebase and documentation. The documentation files AGENTS.md, CHANGELOG.md, CLAUDE.md, and README.md have been updated accordingly, and the original agent/skill definitions have been removed. Feedback suggests improving error handling in agents/planning-agent.md by logging the error object in catch blocks for better debugging.

[gemini-code-assist]

The catch block currently swallows the actual error, which can make debugging difficult. It's a good practice to log the error object for better diagnostics, as per our general rules.

Consider capturing and logging the error, like this:

  } catch (e) {
    console.log('[WARN] repo-intel plugin found but queries failed to load', e);
  }

Suggested change

	} catch {
	console.log('[WARN] git-map plugin found but queries failed to load');
	console.log('[WARN] repo-intel plugin found but queries failed to load');
	}
	} catch (e) {
	console.log('[WARN] repo-intel plugin found but queries failed to load', e);
	}

References

1. In helper functions that catch and handle errors, log the error along with relevant context, such as input arguments, to ensure failures are visible and debuggable.