integrate

Verifies, merges, and reconciles factory worker pull requests against spec acceptance criteria.

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/myspecs/claude-plugins --skill integrate-myspecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integrate
Source: https://github.com/myspecs/claude-plugins/tree/main/plugins/myspec-factory/skills/integrate
Command: npx skills add https://github.com/myspecs/claude-plugins --skill integrate-myspecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When parallel Claude Code worker sessions deliver pull requests for spec-driven tasks, someone must verify each PR against acceptance criteria and the constitution, merge them safely under an agreed policy, and write progress back to MySpec. This Skill automates that integration-manager role so no unverified or out-of-scope code reaches the default branch. ## Core Features & Use Cases - Pull request collection and verification: Matches open PRs to tasks by branch or title, checks CI status, review approvals, acceptance-criteria test coverage, constitution compliance, and scope using read-only verification subagents guided by a test-integrity checklist. - Policy-driven merging: Applies a seven-point ready-to-merge gate (current-head approval, green checks, resolved threads, verified sha), merges one PR at a time in dependency order with --match-head-commit, and watches post-merge CI before continuing. - Spec write-back and milestone gate: Marks merged tasks done in tasks.md on MySpec with optimistic versioning, reconciles spec documents with shipped behavior, and runs a milestone gate with full test suite, convergence analysis, and an uploaded summary. - Use Case: After dispatching a wave of worker sessions for a spec bundle, say "integrate the wave" to have each resulting PR verified, merged per your autonomy policy, tasks marked done on MySpec, and the milestone gate executed. ## Quick Start Ask the assistant to integrate the wave by verifying and merging the factory pull requests for your bundle and marking the tasks done on MySpec.

Frequently Asked Questions about integrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge pull requests from parallel AI coding sessions?▼

Collect open PRs with the GitHub CLI, match each to its tasks by branch name or title, verify checks, reviews, and acceptance criteria, then merge one at a time in dependency order. This Skill automates that flow with a seven-point ready-to-merge gate before each merge.

How to verify AI-generated code against acceptance criteria?▼

Delegate a read-only subagent to map each acceptance criterion to a test in the diff, checking whether the test would actually fail if the implementation were reverted. High-risk criteria require reading the implementation code directly, not just confirming a test exists.

Does this work with GitHub branch protection and required reviews?▼

Yes. The merge gate requires the gating reviewer's approval on the current head commit, all required checks green, no unresolved review threads, and a CLEAN merge state. It never uses --admin, --auto, or force pushes, and disables auto-merge if a PR arrives with it enabled.

Why should pull requests not be merged back to back?▼

Push workflows on the default branch build and deploy per merge commit, and runs started seconds apart can race, letting an older commit's run finish last and overwrite a mutable image tag. The Skill waits for post-merge CI to finish before merging the next PR.

What happens when a worker reports a spec conflict or deviation?▼

The lane stops and the question goes to the user; the answer is recorded as a Clarification in tasks.md or requirements.md before redispatching. Unflagged deviations found in the diff are also surfaced with trade-offs rather than silently kept or reverted.

Can the manager fix failing code itself during integration?▼

No. The manager never rewrites code; red checks or requested changes are sent back to the worker via redispatch with the failing output or review comments in the brief. It only resolves trivial lockfile or changelog conflicts, and says when it did.