shipyard-brainstorming

Translate user ideas into structured design requirements for Shipyard projects.

66|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/lgbarn/shipyard --skill shipyard-brainstorming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipyard-brainstorming
Source: https://github.com/lgbarn/shipyard/tree/main/skills/shipyard-brainstorming
Command: npx skills add https://github.com/lgbarn/shipyard --skill shipyard-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming translates scattered ideas into structured design requirements for Shipyard projects, enabling a focused, requirement-driven development process.

Core Features & Use Cases

  • One-question-at-a-time brainstorming to refine ideas before any implementation.
  • Guided requirements gathering during /shipyard:init to capture scope, constraints, and success criteria.
  • Iterative design segmentation presenting design sections in small, reviewable chunks.

Quick Start

Use the shipyard-brainstorming skill to start requirements gathering for a new feature. The agent will read the project context, ask one focused question at a time, and produce a design brief in sections for review.

Frequently Asked Questions about shipyard-brainstorming

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

FAQPage Schema
How do I translate scattered ideas into structured design requirements?

Structured design requirements are produced by translating scattered ideas through one-question-at-a-time conversations that prompt for context and enforce validation steps.

What is the best way to gather requirements before starting a design?

Requirements gathering is best handled by breaking ideas into manageable design sections, presenting them in small reviewable chunks during initial exploration.

How does guided brainstorming work for project initialization?

Guided brainstorming works by reading project context, asking focused questions sequentially, and producing a design brief in sections for review.

Can I validate project scope and constraints iteratively during design exploration?

Yes, you can validate project scope iteratively because the process enforces explicit validation steps and prompts for context to capture constraints and success criteria.

Does this brainstorming process output commit-ready design documents?

Yes, the brainstorming process outputs documented designs suitable for commit-ready formats by enforcing a rule-driven process with structured sections.

When should I use one-question-at-a-time brainstorming for my project?

One-question-at-a-time brainstorming should be used during initial requirements gathering to refine ideas and define scope before any implementation begins.