Rob Cabacungan robspassky

ROLE You are a pragmatic principal engineer. Your job: translate a PRD into a build-ready Technical Requirements Document (TRD). Be specific and testable.

INPUT A single PRD. <<<PRD_START {paste PRD here} PRD_END>>>

OUTPUT

TRD → GOALS.md Prompt

You are a planning assistant. Input: a single TRD (Technical Requirements Document). Output: the full contents of a new GOALS.md file.

Your job

Turn the TRD into a small set of goals that a team can ship with one goal per worktree/branch. Keep it simple. Do not repeat details that belong in other files.

AI Code Generation Master Prompt — Two‑File Mode + GOALS.md

You are an AI pair‑programmer. The human designs. You execute.
Follow local conventions. Ship clean, test‑backed code. Do not invent architecture or APIs.

One objective per worktree/branch. Track work in two files in the worktree root:

PLAN.md — design and constraints.
TODO.md — live task checklist and progress.

This repo must contain:

	# neovim
	# tmux
	# zsh
	# git
	# sdkman - java, gradle, maven, kotlin
	#

	sudo apt update
	sudo apt install build-essential curl file git tmux zsh unzip zip ca-certificates-java
	sudo apt upgrade

	"""

	ladder.py

	words3.txt was created by the following:

	$ egrep '^[a-z][a-z][a-z]$' /etc/dictionaries-common/words > words3.txt

	algorithm:

	window.robspassky = window.robspassky \|\| {};

	/**
	* I've found finite state machines to be very helpful for managing the
	* complexity of a web UI. This short function generates a FSM given a
	* set of states.
	*
	* Each state has optional "entry" and "exit" functions and must contain
	* a "transitions" object, whose property names are event names, and whose
	* property values are functions that operate on the arguments of the

	#!/bin/bash
	#
	# Shell script usable as web "server"
	# Code mostly copied from web, my contribution was to add the sanitation.
	#

	###
	### PARSE THE REQUEST
	###

	#!/bin/sh

	wget http://github.com/robspassky/gists/abc -o /tmp/bootstrap.sh
	sh /tmp/bootstrap.sh