hdb:design

Generate PRDs and staged task lists for software feature designs.

1|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/hughdbrown/claude-skills --skill hdb-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hdb:design
Source: https://github.com/hughdbrown/claude-skills/tree/main/hdb-design
Command: npx skills add https://github.com/hughdbrown/claude-skills --skill hdb-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative feature design often stalls as teams struggle to align on requirements and implementation steps. This skill provides a structured approach that yields a PRD and a detailed, staged task list grounded in the project's architecture and conventions.

Core Features & Use Cases

  • Produces a Product Requirements Document (PRD) that captures scope, decisions, and implementation stages.
  • Generates a Detailed Task List with test-first scope across each stage, covering tests, code, config, environment, dependencies, and docs.
  • Use Case: When starting a new feature, run this design to produce a unified plan that guides developers and validates feasibility against existing code patterns.

Quick Start

Describe the feature to generate a PRD and a task list.

Frequently Asked Questions about hdb:design

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

FAQPage Schema
How do I generate a PRD and task list for a new software feature?

Generating a PRD requires describing your feature scope to produce a structured requirements document. The design process creates a unified plan capturing technical decisions, test-first acceptance criteria, and staged implementation tasks validated against existing codebase conventions.

What is included in a product requirements document for feature planning?

A PRD for feature planning includes an overview, goals, acceptance criteria written as test descriptions, technical decisions, design and operation notes, test strategy, rollback considerations, and staged implementation plans to form a complete design contract.

How do I create a staged task list with test-first acceptance criteria?

Creating a staged task list with test-first acceptance criteria involves running the feature design process to generate sequential implementation stages. Each stage outputs detailed tasks covering tests, code, config, environment, dependencies, and docs to validate scope.

Can I plan feature development for an existing codebase using automated design?

Planning feature development for an existing codebase is supported by generating architecture-grounded decisions. The design process aligns the PRD, acceptance criteria, and staged implementation tasks with your project's established patterns and conventions.

What is the best way to document software architecture decisions and rollback plans?

Documenting architecture decisions and rollback plans is handled within the PRD's enforced design contract. This captures technical decisions, design and operation notes, and rollback considerations alongside acceptance criteria and staged implementation plans for comprehensive alignment.

When do I need a structured PRD versus a simple task list for feature planning?

A structured PRD is needed for complex software feature designs requiring alignment on scope, technical decisions, and feasibility. A simple task list works for minor changes, but staged implementation with test-first acceptance criteria requires the enforced design contract of a full PRD.