Compare two design inventories produced by inventory-design and emit a structured gap artifact whose prose paragraphs satisfy the extract-work-items cue-phrase contract. Use after running inventory-design for both a current and target design surface. The resulting gap artifact under meta/design-gaps/ feeds directly into /accelerator:extract-work-items to produce actionable work items.

Review as a systems architect evaluating whether the structure will sustain the system's evolution.

!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh attach-jira-issue`

Review as the next developer who will maintain this code in six months.

Review as a work item completeness specialist ensuring that every section contains the information a reader needs to understand and act on the work item without follow-up questions.

Review as a formal verifier checking whether the code's logic is sound under all valid inputs, state transitions, and concurrent execution scenarios.

Review as a database administrator bringing expert knowledge of the specific database technology in use to ensure changes are correct from the database's perspective. Infer the database engine from the codebase (migrations, ORM configuration, connection strings, SQL dialect) and apply engine-specifi

Review as a dependency-mapping specialist evaluating whether every coupling the work item implies is explicitly captured.

Review as a technical writer ensuring that documentation enables self-service understanding — but first, infer the project's documentation norms from existing code. A project that omits docstrings in application code is not under-documented; it has different standards than a public library. Assess

!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh extract-work-items` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-agents.sh`

Extract architecture decision records from existing meta documents (research, plans). Scans documents for implicit or explicit architectural decisions and converts selected ones into formal ADRs. Use when decisions are buried in research or planning documents and need to be captured formally.

Set up the Jira Cloud integration for this project. Verifies credentials against a real Jira Cloud tenant, discovers the tenant's custom-field catalogue and project list, and persists the results under `<paths.integrations>/jira/` (default `meta/integrations/jira/`) as team-shared, version-controlled JSON caches. Idempotent: safe to re-run after credential or project changes.

!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh inventory-design` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-agents.sh`

List and filter work items from the configured work directory. Use when discovering what work items exist, filtering by status/type/priority/parent/tag, or viewing the work item hierarchy.

Review as a capacity planner identifying where the system will bottleneck under load.

Output format specification for plan review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for plan reviews.

Review as a platform engineer ensuring the system can run in any target environment without modification. Always flag vendor coupling — even when the project currently targets a single provider — so that lock-in is a conscious decision rather than an accidental one.

Output format specification for PR review agents. Defines the JSON schema, field reference, severity emoji prefixes, and comment body format for PR reviews.

Respond to pull request review feedback interactively, working through each item with verification and code changes. Use when the user wants to address PR review comments.