source-command-sparc-integration

Merges outputs from multiple development modes into a tested, cohesive system.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/derbalimajd04-dot/al-wasat --skill source-command-sparc-integration-derbalimajd04-dot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-sparc-integration
Source: https://github.com/derbalimajd04-dot/al-wasat/tree/main/.agents/skills/source-command-sparc-integration
Command: npx skills add https://github.com/derbalimajd04-dot/al-wasat --skill source-command-sparc-integration-derbalimajd04-dot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Combining code and artifacts produced by different development modes often leads to interface mismatches, duplicated modules, and inconsistent environment configuration. This Skill acts as a system integrator that merges those outputs into one working, tested system. ## Core Features & Use Cases - Interface Verification: Checks compatibility of interfaces, shared modules, and environment configuration standards across components. - Integration Orchestration: Splits integration logic across domains and can spawn subtasks for preflight testing or conflict resolution. - Memory Persistence: Stores and queries integration context in a namespaced memory store via MCP tools or the NPX CLI. - Use Case: After separate modes generate a payment service and an API gateway, run the integration mode to connect them, verify shared modules, and produce a completion summary of what was connected. ## Quick Start Ask the assistant to run the sparc integration mode to connect the payment service with the rest of the system and verify interface compatibility.

Frequently Asked Questions about source-command-sparc-integration

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

FAQPage Schema
How do I run the sparc integration mode?▼

Run the integration mode through MCP tools by calling sparc_mode with mode set to integration and a task description, or use the NPX CLI fallback with npx Codex-flow sparc run integration followed by your task in quotes.

What does the system integrator mode actually check?▼

It verifies interface compatibility, shared modules, and environment configuration standards across components. It can split integration logic across domains and end tasks with a completion summary of what was connected.

Can I use the integration mode without MCP tools?▼

Yes, use the NPX CLI fallback with npx Codex-flow sparc run integration followed by your task description. You can also add flags like --namespace integration or --non-interactive for scripted runs.

How do I store integration context between runs?▼

Use the memory_usage MCP tool with action store, a key, and the integration namespace, or run npx Codex-flow memory store from the CLI. Query previous work later with memory_search or memory query using the same namespace.

When should I not use the integration mode?▼

Avoid it when components have not yet been produced by their respective modes, since there is nothing to merge. It is designed for combining finished outputs, not for generating new features or writing initial implementations.