# Grind Design Discussion

Autonomous review pass on design discussion document.

- Repository: https://github.com/humanlayer/humanlayer (12740 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add humanlayer/humanlayer --skill grind-design-discussion -g -a claude-code -y`
Codex: `npx skills add humanlayer/humanlayer --skill grind-design-discussion -g -a codex -y`
Cursor: `npx skills add humanlayer/humanlayer --skill grind-design-discussion -g -a cursor -y`
Gemini CLI: `npx skills add humanlayer/humanlayer --skill grind-design-discussion -g -a gemini-cli -y`

## Description

autonomous review pass on design discussion document. Use when you want to grind on a design doc without user feedback - surfaces questions, vets assumptions, verifies patterns.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Grind Design Discussion

You are performing an autonomous review pass on an existing design discussion document. Self-direct the review by mining assumptions, verifying patterns, and surfacing new design questions.

## Steps

1. **Find and read the task directory**:
   - You should know the task directory, if not ask the user
   - Read ALL files in the task directory (design discussion, ticket, research, etc.)
   - **IMPORTANT**: Use the Read tool WITHOUT limit/offset to read entire files
   - **IMPORTANT**: DO NOT use Glob or Grep or Search tools on .humanlayer/tasks, it may be a symlink

2. **Assumption mining, surface implicit assumptions**:
   - Re-read the design discussion carefully
   - For each design decision and recommendation, identify implicit assumptions:
     - What codebase behavior is assumed but not verified by the research?
     - What edge cases or failure modes are not discussed?
     - What interactions between components are assumed but not explored?
     
   - Build a list of assumptions to investigate

3. **Pattern verification, verify patterns to follow**:

   - Note any patterns that are outdated, incomplete, or have edge cases not mentioned in the design doc
   - If you find multiple patterns to accomplish a task, remove it from "patterns to follow" and add a design question about which one to follow
   - If you find important information in the codebase, add it to the research document as well. Remember the research doc must only contain information about the current state.

4. **Question completeness review**:
   - Review existing design questions
   - For each question, check if the listed options are comprehensive, are there other viable approaches not considered?
   - Check if recommendations are well-supported by patterns found
   - Identify any new design questions that emerge from the assumption mining and pattern verification

The rest: https://github.com/humanlayer/humanlayer/blob/HEAD/.claude/skills/grind-design-discussion/SKILL.md