ship-init

Automate Shipyard project setup, configuration, scaffolding, and codebase analysis.

2|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Acendas/shipyard --skill ship-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-init
Source: https://github.com/Acendas/shipyard/tree/main/plugins/shipyard/skills/ship-init
Command: npx skills add https://github.com/Acendas/shipyard --skill ship-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Initialize or update a Shipyard project by configuring settings, creating a robust directory structure, and performing codebase analysis to establish a reliable working context.

Core Features & Use Cases

  • Bootstrap a new Shipyard project with a complete config, scaffolding, and initial analysis.
  • Reconfigure existing projects, re-analyze after changes, or migrate tool files to the latest schema.
  • Generate stable, shareable memory and context artifacts for teams to align on project state.

Quick Start

Run ship-init to set up Shipyard in your project, generating config, scaffolding, and initial codebase analysis.

Frequently Asked Questions about ship-init

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

FAQPage Schema
How do I initialize project configuration and codebase analysis for a new setup?

To initialize project configuration, run ship-init to automatically generate config files, scaffold the directory structure, and perform initial codebase analysis to establish a reliable working context.

What is the best way to migrate legacy project configuration files to a new schema?

Migrating legacy project configuration files is handled automatically by ship-init, which updates existing tool files to the latest schema while preserving your current project state during reconfiguration.

Can I re-analyze my codebase after making changes to update the project context?

Yes, you can re-analyze your codebase by running ship-init again, which updates the project context, refreshes memory artifacts, and ensures your environment is prepared for feature planning.

Does ship-init work with existing repositories or only fresh installs?

Ship-init works with both fresh installs and existing repositories, supporting quick checks, legacy migrations, and memory initialization across various repo contexts to maintain deterministic project state.

Why does project initialization require deterministic steps and shared memory artifacts?

Project initialization requires deterministic steps enforced via SHIPYARD_DATA to generate stable, shareable memory and context artifacts, ensuring teams align reliably on the exact project state.

What should I do if my project scaffolding or context initialization is not working correctly?

If project scaffolding or context initialization is not working, ensure SHIPYARD_DATA is properly configured, then re-run ship-init to enforce deterministic steps and overwrite any inconsistent config templates.