Andrew Nutter-Upham andynu

Two-Context Execution Pattern with Beads

A workflow pattern for AI-assisted development that separates planning from execution, using context isolation to keep each layer focused.

The Problem

Large tasks overwhelm a single Claude session:

Context fills with implementation details
Hard to track overall progress
Easy to lose sight of the plan while deep in code

Multi-Agent Claude Code Workflow

A lightweight pattern for spawning secondary Claude Code sessions using tmux, enabling parallel work across projects without context collision.

Why Spawn Secondary Sessions?

When working from a "mission control" directory (like ~/work/src/ with 100+ projects), you often need to:

Dispatch deep work to a specific project while continuing meta-level coordination
Run parallel investigations that would pollute a single session's context

name	description
C4 Diagrams	Creating C4 architecture diagrams using D2 diagram language. Use when creating system context diagrams, container diagrams, component diagrams, code diagrams, deployment diagrams, or any software architecture visualization following the C4 model. Also applies when discussing architecture at different zoom levels or explaining system boundaries.

C4 Architecture Diagrams with D2

Create C4 model diagrams using D2's text-to-diagram syntax. Supports both graphical (SVG/PNG) and ASCII output.

description	argument-hint	allowed-tools	context
execute a single bd issue	<issue key>	Bash(bd ), Bash(git ), Bash(tea *), Read(.)	fork

Execute Single BD Issue

Overview

Execute a single bd issue with proper status tracking, commenting, and git workflow integration. This command handles one issue in isolation, keeping context clean.

description	allowed-tools
execute a set of bd issues	Bash(bd:*)

Execute BD Plan Command

Overview

Execute a bd plan by working through issues with proper status tracking, commenting, and git workflow integration. Do not ask which one to start with. Start with any ready task by priority, if there is a tie, choose the first one. Please continue implementing until all ready tasks are complete, or you hit a critical question that demands a human answer.

Execute Plan Command

Overview

Execute a numerically-prefixed plan file from the plans folder based on the provided argument.

Instructions

Plan Selection

Read the plan file with prefix matching $ARGUMENTS from the plans folder
Check plans/index.md to see if the plan file has changed since last worked (compare Last Modified vs Last Worked timestamps)

	---
	- name: ruby build dependencies
	apt:
	pkg:
	- git
	- build-essential
	- libssl-dev
	- zlib1g-dev
	- libreadline-dev
	- libffi-dev

	#!/bin/bash
	input=$(cat)
	MODEL=$(echo "$input" \| jq -r '.model.display_name // "Claude"')
	DIR=$(echo "$input" \| jq -r '.workspace.current_dir // "~"')
	FOLDER="${DIR##*/}"

	# Git branch
	BRANCH=""
	if git -C "$DIR" rev-parse --git-dir > /dev/null 2>&1; then
	BRANCH=$(git -C "$DIR" branch --show-current 2>/dev/null)

	#!/bin/bash

	# start_gunicorn.sh - Start Cellxgene Gateway with Gunicorn
	#
	# PREREQUISITES:
	# - Gunicorn installed (included with cellxgene 1.3.0, or: pip install gunicorn)
	# - Virtual environment activated or .venv present
	# - .env file with CELLXGENE_LOCATION and CELLXGENE_DATA (or CELLXGENE_BUCKET)
	#
	# USAGE:

	require 'active_support/concern'

	# The {FiltersConcern} provides a <tt>filter_params</tt> scope which takes a hash <tt>{ col1: term, col2: term }</tt>
	#
	# see app/assets/javascripts/filterable.js
	#
	# == type sensitive filtering
	# * strings - fuzzy search of %term%
	# * dates -
	# * July - => month