integration-analysis
Integration Analysis
Discover everything. Analyze how it all fits together. Plan what to build and in what order.
Give it a few starting points — repos, config dirs, system names. It discovers the full ecosystem by tracing integration surfaces in code and docs, clones repos it doesn't have locally, then thoroughly analyzes how every system works and connects. The output: a phased implementation plan where each layer builds on the last — MVP first, then progressively more capability.
Estimated Time: 30-90 minutes (depending on system count, mode, and available inputs)
Prerequisites: At least one starting-point repo or config directory
Output: Analysis artifacts + dependency-ordered epics in _integration-analysis/
When to Use This Skill
Use this skill when:
- You're integrating multiple legacy or new systems into a unified platform
- You need to understand the integration surface between systems (not just individual codebases)
- You want a layered implementation plan instead of a big-bang rewrite
- You need to identify shared data models, API contracts, and dependency chains across systems
More from jschulte/stackshift
analyze
Perform initial analysis of a codebase - detect tech stack, directory structure, and completeness. This is Step 1 of the 6-step reverse engineering process that transforms incomplete applications into spec-driven codebases. Automatically detects programming languages, frameworks, architecture patterns, and generates comprehensive analysis-report.md. Use when starting reverse engineering on any codebase.
7cruise-control
Automatic mode - shift through all 6 gears sequentially without stopping. Like cruise control or automatic transmission, this runs the entire StackShift workflow from analysis to implementation in one go. Perfect for unattended execution or when you want to let StackShift handle everything automatically.
6spec-coverage-map
Generate a visual spec-to-code coverage map showing which code files are covered by which specifications. Creates ASCII diagrams, reverse indexes, and coverage statistics. Use after implementation or during cleanup to validate spec coverage.
6discover
Ecosystem discovery from a single starting repo. Scans for integration signals (npm packages, docker compose, env vars, API calls, CI/CD triggers, workspace configs, message queues, infrastructure refs), searches GitHub for related repos, scans the local filesystem, then presents an ecosystem map with confidence scoring and a Mermaid dependency graph. Hands off confirmed repos to /stackshift.batch or /stackshift.reimagine.
5complete-spec
Interactive conversation to resolve [NEEDS CLARIFICATION] markers using /speckit.clarify command. Claude asks questions about missing features, UX/UI details, behavior, and priorities. Updates specs in .specify/memory/ with answers to create complete, unambiguous documentation. This is Step 5 of 6 in the reverse engineering process.
5modernize
Brownfield Upgrade - Upgrade all dependencies and modernize the application while maintaining spec-driven control. Runs after Gear 6 for brownfield projects with modernize flag enabled. Updates deps, fixes breaking changes, improves test coverage, updates specs to match changes.
5