dotfile-brainstorm

Convert vague project ideas into structured design documents with pipeline configuration.

330|47|Updated Aug 30, 2020

Search Tags:#design #specification #testing strategy #autonomous coding #llm pipelines #dot generation

Ready to run

npx skills add https://github.com/harperreed/dotfiles --skill dotfile-brainstorm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotfile-brainstorm
Source: https://github.com/harperreed/dotfiles/tree/main/.claude/skills-archive/dot-file-brainstorm
Command: npx skills add https://github.com/harperreed/dotfiles --skill dotfile-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you go from an unclear project idea to a complete, pipeline-ready design doc that can directly drive autonomous DOT-based build execution.

Core Features & Use Cases

Pipeline-ready project design: Produces a structured design document with a dedicated Pipeline Configuration section required for downstream DOT generation.
Build-pipeline thinking (not CI/CD): Guides you to describe an LLM coding build pipeline (plan → implement → verify → ship) rather than a deployment workflow or static architecture diagram.
Approval-first workflow: Enforces a hard gate so no DOT output or implementation happens until the full design is presented and approved.

Quick Start

Use the dotfile-brainstorm skill to brainstorm your feature request into a pipeline DOT-ready design doc, then approve the design to proceed to dotfile-from-spec.

Frequently Asked Questions about dotfile-brainstorm

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

FAQPage Schema

How do I turn a vague feature request into a build-ready design document?▼

To turn a vague feature request into a build-ready design document, you need to define the architecture, testing strategy, and pipeline routing. A structured brainstorming process transforms unspecific concepts into an execution-ready plan for autonomous LLM build pipelines.

What is a pipeline configuration for autonomous LLM coding?▼

A pipeline configuration for autonomous LLM coding defines the build phases, testing strategy, human gate decisions, retry plans, and parallelism. It structures the flow from planning to implementation, verification, and shipping rather than acting as a traditional CI/CD deployment workflow.

How do I generate a DOT file from a project specification?▼

To generate a DOT file from a project specification, you must first complete a structured design document that includes a full pipeline configuration. An approval gate ensures no DOT output or implementation begins until the execution-ready plan is reviewed and accepted.

Does autonomous coding require a human approval gate before generating execution plans?▼

Yes, autonomous coding requires a hard human approval gate before generating execution plans. This ensures no DOT output or implementation occurs until the complete design document, including pipeline routing and testing strategy, is explicitly reviewed and approved.

Can I use a design specification for static architecture diagrams instead of build pipelines?▼

No, this design specification process targets LLM build pipelines rather than static architecture diagrams. It guides you to describe a dynamic coding workflow of planning, implementation, verification, and shipping needed to drive autonomous DOT-based execution.

What do I need to define before creating an autonomous LLM build pipeline?▼

Before creating an autonomous LLM build pipeline, you need to define required build phases, a testing and quality strategy, human gate decisions, retry plans, and parallelism plans. Presenting this complete pipeline configuration is required to generate DOT output.