steamship-integrations

Verifies features and decisions align with project constitution. Use when evaluating new features, resolving design conflicts, or ensuring constitutional compliance.

For use when a new issue/task has been identified and needs to be formally captured using the Wingman MCP issue management system. Use this skill to create new issues via the issues_create MCP tool with appropriate metadata and structured content.

Develops project constitutional principles through Socratic questioning. Use when establishing design values, creating project governance, or resolving ambiguous design decisions.

Fixes documentation issues on isolated worktrees with PRs. Processes issues from docs-audit-scan in parallel where possible.

Reviews documentation fix PRs for completeness and accuracy against their source issues. Acts as a quality gate before merge.

Parallelized documentation audit that scans for completeness, accuracy, consistency, and staleness, then creates implementation-ready fix issues.

Perform comprehensive project housekeeping - update roadmap, reconcile issues with implementation reality, organize completed work, and identify drift. This is a workflow skill that coordinates multiple parallel subagents for efficiency. Use when user says something like "run housekeeping", "do your housekeeping" or "clean up project state".

Implements an existing plan by executing MCP issues in a worktree with TDD and PR publication. Use when a plan with subtask issues already exists and you need to execute it. Does NOT create plans -- use writing-plans for that.

Implements a single issue with TDD, code review, and fix loop. Use when a specific issue needs implementation -- either standalone or as part of orchestrated spec execution.

Orchestrates specification implementation through planning, execution, verification, and PR publication phases with session recovery. Use when implementing specifications requiring phased workflow and resumable progress tracking.

Initializes complete governance framework including constitution, roadmap, and templates. Use when setting up new projects or establishing governance in existing projects lacking systematic documentation.

Launches workflow engine runs in the background, monitors progress via session files, and reports status. Use when running construyelo workflows or any workflow engine invocation.

Traces every spec sub-requirement through to integrated implementation, fixes integration gaps, and gates on compliance. Use between implement and review-pr phases.

Validates governance file completeness, format compliance, and metric accuracy. Use when auditing governance health, after bulk changes, or ensuring documentation integrity.

Use when design is complete and you need detailed implementation tasks - creates tracked MCP issues with exact file paths, complete code examples, and verification steps. Optional architecture plan published as a section on the spec issue.

Use when creating technical specifications for features, systems, or architectural designs. Creates comprehensive specification documents using the Wingman MCP issue management system with proper structure and completeness checks.

Generates a visual architecture overview of a codebase using Mermaid diagrams, producing ARCHITECTURE.md at the repo root. Use when onboarding to a new project, documenting system structure, or creating a high-level map of modules, dependencies, and key flows.

Auto-updates status metrics across governance documents from MCP issue counts. Use when governance metrics are stale or after significant issue status changes requiring documentation refresh.

Generate situational awareness report showing new memos, recent commits, decisions, questions, and roadmap work since user's last reporting-status. Use when user asks "what's new", "catch me up", "status update", "what did I miss", or "recent activity". ONLY invoke via /wingman:reporting-status command.

Validates roadmap completeness, phase coherence, and alignment with constitution. Use when creating roadmaps, reviewing planning documents, or ensuring strategic consistency.

Generates user-facing documentation from specifications with auto-detection of pre-implementation vs post-implementation context. Use when writing docs for a feature (conceptual overviews, READMEs, API reference, tutorials, how-to guides) either before or after code exists.

Creates structured notes from user intent. Replaces ad-hoc memo writing and the former capturing-ideas skill. Auto-selects a typed template based on context.

Workflow-orchestrated research and documentation of ocean carrier API capabilities. Produces a verified inventory, updates cross-carrier reference docs, and provides SDK adapter recommendations.