sp-integrate

Runs integration prechecks and closeout for completed feature lanes before mainline merge.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-integrate-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-integrate
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-integrate
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-integrate-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple isolated feature lanes finish implementation, teams lack a structured way to verify readiness, detect merge conflicts or shared-surface overlap, and close lanes cleanly before merging to mainline. ## Core Features & Use Cases - Lane Discovery and Prechecks: Discovers completed feature lanes and runs integration readiness checks against verification evidence. - Drift and Overlap Detection: Surfaces shared-surface overlap, merge sequencing risk, and unresolved blockers instead of hiding them behind a generic done status. - Integrated UI Evidence: For UI-bearing lanes, recaptures viewport and state evidence against the integrated tree before allowing closeout. - Use Case: After three parallel feature branches complete implementation, run this workflow to confirm each lane's readiness, get explicit closeout guidance, and sequence the merges safely. ## Quick Start Ask the agent to run sp-integrate to check integration readiness and close out the completed feature lanes before merging to mainline.

Frequently Asked Questions about sp-integrate

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

FAQPage Schema
How do I check if feature branches are ready to merge?▼

Run the sp-integrate workflow after implementation completes. It discovers candidate completed lanes, checks verification evidence and shared-surface overlap, and returns an integration readiness result for each lane with explicit closeout guidance.

What is the difference between sp-integrate and sp-implement?▼

sp-implement handles feature implementation inside a lane, while sp-integrate is a dedicated closeout workflow that runs after implementation completes. The skill explicitly forbids folding integration closeout back into sp-implement.

Does sp-integrate require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory, including templates like .specify/templates/workflow-blocker-template.md and memory files such as .specify/memory/constitution.md.

What happens when integration closeout is blocked?▼

The workflow follows a blocked exit contract that preserves state and produces structured blocker output per the workflow-blocker-template JSON schema. It never claims completion and only sets human_action_required for authority, credentials, or human decisions.

How does sp-integrate handle UI changes across lanes?▼

For UI-bearing lanes, isolated screenshots are treated as input only. After the integrated tree exists, the workflow reruns real entry points, recaptures the viewport and state matrix, and keeps closeout blocked until integrated evidence exists.