design

Investigate repository code and produce a TDD-oriented implementation plan.

88|6|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/heliohq/ship --skill design-heliohq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/heliohq/ship/tree/main/skills/design
Command: npx skills add https://github.com/heliohq/ship --skill design-heliohq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you plan implementation before coding by investigating the repository, identifying dependencies, and turning an ambiguous task into a concrete spec and executable plan.

Core Features & Use Cases

  • Repository Investigation: Reads the codebase directly and traces the relevant files, callers, consumers, and tests before proposing changes.
  • Spec and Plan Writing: Produces a validated spec, compares it against a peer-produced spec, and converts the result into an actionable implementation plan.
  • Peer Validation Workflow: Uses independent review to catch gaps, contradictions, and ambiguous steps before development starts.
  • Use Case: A developer asks for a refactor, feature, or bug fix and needs a clear, testable path forward instead of jumping straight into code.

Quick Start

Use the design skill to investigate this repository, write the spec, compare it with a peer review, and produce an implementation plan for my task.

Frequently Asked Questions about design

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

FAQPage Schema
What is the best way to turn an ambiguous coding task into an executable plan?

The best way to turn an ambiguous coding task into an executable plan is to investigate the repository code, write a validated spec, compare it against a peer-produced spec, and generate a TDD-oriented plan with clear commands and artifacts.

How do I create an implementation plan before coding a new feature?

To create an implementation plan before coding, investigate the repository to trace relevant files and tests, write a spec, validate it through peer review, and convert the result into an executable TDD-oriented plan with clear commands and artifacts.

What is peer review in spec writing and why is it needed?

Peer review in spec writing is an independent validation workflow that compares a produced spec against an independent alternative to catch gaps, contradictions, and ambiguous steps before development starts, ensuring a solid implementation plan.

How do I plan a codebase refactor without missing dependencies?

To plan a codebase refactor without missing dependencies, investigate the repository directly to trace callers, consumers, and tests, then use file-level evidence to produce an executable implementation plan with execution drill checks.

Does test-driven development planning work for bug fixes and refactoring?

Test-driven development planning works for bug fixes and refactoring by requiring file-level evidence and execution drill checks, applying an independent peer comparison workflow to validate the spec before producing an executable plan.

What is the best way to turn an ambiguous coding task into an executable plan?

The best way to turn an ambiguous coding task into an executable plan is to investigate the repository code, write a validated spec, compare it against a peer-produced spec, and generate a TDD-oriented plan with clear commands and artifacts.