lgbarn

Import a spec-kit feature spec into Shipyard, replacing brainstorming. Use when a spec-kit feature directory exists with spec.md.

Use to inspect or manage Shipyard project state under Codex — show status, resume a previous session, cancel/pause in-progress work, or roll back to a checkpoint. Trigger when the user says "shipyard status", "what's the status", "resume", "continue where we left off", "cancel", "pause this", "roll back", or "restore the checkpoint". Codex has no SessionStart hook, so this skill loads state on demand.

Use when running any multi-step Shipyard workflow under Codex — build, audit, plan, ship, review, research, or map. Explains how Shipyard's parallel-agent workflows degrade to inline sequential execution in Codex, and routes intent to the right workflow skill. Trigger when the user says "build the plan", "audit this", "ship it", "review the code", "run the shipyard build", or asks how Shipyard works in Codex.

Use when performing brownfield analysis on an existing codebase under Codex — onboarding to a new project, generating codebase documentation, or understanding legacy code. Trigger when the user says "map this codebase", "help me understand this code", "document this project", "I just inherited this repo", or runs shipyard init on existing code. This is the Codex inline-sequential form of the mapper agent.

Use when conducting domain research, evaluating technology options, investigating ecosystem choices, or gathering knowledge for a development phase under Codex. Trigger when the user says "research X", "what are our options for", "evaluate these libraries", "what's the best approach to", or before planning a phase. This is the Codex inline-sequential form of the researcher agent.

Use when reviewing code under Codex — verifying spec compliance, conducting quality review after a build, or checking that an implementation matches its plan. Trigger when the user says "review this", "review the implementation", "does this match the plan", "check the code quality", or after a Shipyard build completes. This is the Codex inline-sequential form of the reviewer agent.

Use when delivering or releasing a completed Shipyard phase under Codex — final verification, pre-ship security audit, documentation, and release. Trigger when the user says "ship it", "ship this phase", "release this", "we're done — finalize", or "run the shipyard ship workflow". This is the Codex inline-sequential form of the /shipyard:ship orchestration.

Use after implementing features, before claiming a phase is complete, when reviewing AI-generated code, or when code feels overly complex. Also use when you notice repeated patterns across files, a function exceeds 40 lines, nesting exceeds 3 levels, or an abstraction has only one implementation. Covers duplication, dead code, over-engineering, and AI-specific bloat patterns like verbose error handling and redundant type checks.

Use when executing implementation plans with independent tasks in the current session

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when generating documentation for Terraform modules, infrastructure, or runbooks. Creates READMEs, operational guides, and architecture docs.

Use before any Terraform or AWS operation to verify correct credentials and profile are active. Prevents cross-environment accidents.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when analyzing git history and past changes to identify patterns, recurring issues, and lessons learned from infrastructure changes.

NinjaTrader 8 NinjaScript indicator scaffold and patterns. Provides C# structure guidance and triggers doc-researcher for API verification. Use when developing NinjaTrader indicators.

Pine Script v5/v6 indicator scaffold and patterns. Provides structure guidance and triggers doc-researcher for current syntax verification. Use when developing TradingView indicators.

Tradovate JavaScript indicator scaffold and patterns. Provides class structure and export guidance. Use when developing Tradovate indicators.

Team conventions, module layout, and AWS GovCloud gotchas for our Terraform codebase. Use whenever the user mentions Terraform, tf files, modules, state backend, tagging, provider versions, GovCloud, region endpoints, or general IaC questions — even if they don't explicitly ask for help. Also use when a `.tf` or `.tfvars` file is in the working directory and the user asks "what should I do next" or "is this right".

Diagnose and troubleshoot Kubernetes cluster problems using the kdiag CLI. This skill MUST be consulted for ANY Kubernetes operational issue: pods crashing or stuck Pending, deployments not rolling out, services unreachable, DNS failures, ingress not routing, node pressure or capacity problems, missing ConfigMaps/Secrets, network policy conflicts, and EKS-specific issues like VPC CNI errors, ENI/IP exhaustion, security groups, or VPC endpoint verification. Activate on ANY mention of debugging, diagnosing, or investigating problems in a Kubernetes cluster — even vague reports like "my app isn't working" or "something broke in prod" when Kubernetes is involved. Do NOT activate for writing new Kubernetes manifests/operators/Helm charts, setting up CI/CD, provisioning infrastructure with Terraform, or application code development.

Comprehensive Go development skill for writing idiomatic, well-tested Go code. Use when creating new Go projects, writing or refactoring Go code, implementing Go tests, or reviewing Go code for best practices. Enforces TDD workflow, table-driven tests, and idiomatic patterns including proper error handling, interface design, and package organization.