ship-architect

Translates feature briefs into technical implementation specifications with data models and API surfaces.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/dain-agency/mood-tracker --skill ship-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-architect
Source: https://github.com/dain-agency/mood-tracker/tree/main/.claude/skills/ship-architect
Command: npx skills add https://github.com/dain-agency/mood-tracker --skill ship-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the gap between high-level feature briefs and build-ready technical plans, removing the need for manual deep codebase exploration and reducing costly rework from misaligned specifications.

Core Features & Use Cases

  • Convention-Aligned Design: Reads project config and domain INDEX.md files to ensure all technical decisions match existing tech stacks, design systems, database conventions, and component catalogues.
  • End-to-End Spec Generation: Produces complete technical strategies including data models, API surfaces, component trees, dependency maps, and impact assessments.
  • Validated Wireframes: Generates interactive, design-system-compliant wireframes for UI features with built-in self-audits to catch layout issues before user review.
  • Use Case: A product manager submits a feature brief for a new user notification centre. Use this Skill to output a full technical spec with Prisma schema changes, API endpoints, React component designs, and approved wireframes ready for the engineering team to build.

Quick Start

Use the ship-architect skill to produce a complete technical implementation spec for the feature brief located at [path/to/your/feature-brief.md].

Frequently Asked Questions about ship-architect

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

FAQPage Schema
How do I generate technical implementation specifications from a feature brief?

To generate technical implementation specifications from a feature brief, you translate human-readable user journeys and requirements into detailed data models, API surfaces, and component designs aligned with existing project conventions.

How do I create build-ready specs that match my existing tech stack and codebase architecture?

Build-ready specs matching your tech stack are created by reading project config and domain INDEX.md files, ensuring all technical decisions align with existing database conventions, design systems, and component catalogues.

Can I generate design-system-compliant wireframes for full-stack software projects?

Yes, you can generate interactive, design-system-compliant wireframes for UI features. These wireframes include built-in self-audits to catch layout issues and validate component designs before user review.

What is the best way to automate API design and schema design from product requirements?

Automating API design and schema design from product requirements involves processing feature briefs to output complete technical strategies, including Prisma schema changes, API endpoints, and dependency maps for the engineering team.

Does generating technical specifications require manual codebase exploration?

No, generating technical specifications does not require manual deep codebase exploration. The process automatically applies project conventions to eliminate build errors and reduce costly rework from misaligned specifications.

What should a feature brief include for accurate implementation planning?

For accurate implementation planning, a feature brief should include user context, journeys, and requirements. This input is translated into validated wireframes, data models, and component trees ready for development.