robmclarty

Execute a Trellis task list by dispatching each task to a Claude Code subagent in its own context window. Use when the user says "build with sub-agents", "build with subagents", or when a feature has 5-20 tasks with dependencies between them. Reads `.specs/<feature>/tasks.md` produced by the tasks skill. Each subagent gets focused context (guidelines + plan + task + learnings) and returns results to the orchestrating session. Supports parallel execution of independent tasks via background subagents with worktree isolation.

Execute a Trellis task list using Claude Code's /batch command for bulk, patterned changes across many files. Use when the user says "build with batch" or when a feature involves repetitive changes across dozens or hundreds of files (e.g., migrating from one library to another, applying naming conventions, adding error handling patterns). Reads `.specs/<feature>/tasks.md` produced by the tasks skill. Translates the task list into one or more /batch invocations with worktree-isolated parallel agents.

Creates or updates .specs/guidelines.md with project-wide stack, conventions, and principles. Use when starting a project or when a fundamental technology decision has changed.

Use when user wants to Creates a pitch document at .specs/{feature}/pitch.md defining a problem domain with constraints, appetite, and solution shape. Use to frame a feature before writing a spec.

Use when user wants to Creates a technical plan at .specs/{feature}/plan.md translating a spec's functional requirements into architecture, technology, and code decisions.

Use when user wants to Creates a lightweight experiment document at .specs/sketches/{slug}.md to test a technical hypothesis before committing to a larger initiative.

Use when user wants to Creates a full functional specification at .specs/{feature}/spec.md defining what a system does and why. Use to write or revise feature requirements.

Executes implementation from tasks.json through a check-driven feedback loop. Use when all spec artifacts are ready and implementation should begin.

Validate that the repo and a build's directory are ready for `ridgeline build`. Runs `npm run check`, parses `.check/summary.json`, verifies the planner has produced phases, checks node_module deps, git state, and spec-vs-repo consistency. Identifies anything that would hang up a build agent or burn budget on retries — missing system deps, broken tests, stale phase artifacts, spec referents that don't exist. Writes build-check.md with status ready, needs-attention, or broken. Use when the user runs `/build-check [build-name]` or asks to validate readiness before `ridgeline build`.

Read a build's build-check.md and fix repo issues so `ridgeline build` can run cleanly. Plans fixes, dispatches parallel subagents grouped by disjoint file sets, re-runs `npm run check` and `/build-check`, and loops until status reaches ready or a 3-iteration cap is hit. Use when the user runs `/build-fix [build-name]` or asks to repair the repo after `/build-check` flagged issues.

Validate that a build's spec.md is ready for the ridgeline planner. Checks required sections, internal consistency, cross-file alignment with constraints/taste/design, and feasibility against the repo. Writes spec-check.md with status ready, needs-attention, or broken. Use when the user runs `/spec-check [build-name]` or asks to validate a build's spec before planning. Run before `ridgeline plan` to catch spec issues that would cause the planner to hallucinate phases.

Read a build's spec-check.md and fix the spec/constraints/taste/design files so the spec is ready for the ridgeline planner. Plans fixes, dispatches one or more fix agents, re-runs `/spec-check`, and loops until the status reaches ready or a 3-iteration cap is hit. Use when the user runs `/spec-fix [build-name]` or asks to repair a build's spec after `/spec-check` flagged issues.

Convert an arbitrary spec, PRD, RFC, or design doc (or a directory of related docs) into a ridgeline-ready trio of `spec.md` + `constraints.md` + `taste.md` (and optional `design.md`) saved to a target directory. Use this skill whenever the user wants to feed a freeform specification into ridgeline, asks to "ridgeline-ify" or "split" a spec, mentions converting a PRD/RFC/design doc into ridgeline inputs, or requests producing constraints/taste/spec files from a source document or document folder. Do NOT trigger for editing an existing constraints.md/taste.md/spec.md — only for the initial extraction from source material.

Bump the project version in `package.json` via scripts/bump-version.mjs, summarize every commit since the last release into a new CHANGELOG.md section, commit with a `vX.Y.Z` message, and push an annotated tag. Use when cutting a release.

Validate and cross-compile GLSL, WGSL, and SPIR-V shaders using naga. Use when writing shaders, checking shader compilation, debugging shader errors, converting between shader languages, or verifying WebGL/WebGPU shader code.

Capture annotated browser screenshots with numbered element labels for visual verification. Use when building or reviewing web UIs, verifying responsive layouts, checking visual output of canvas/WebGL content, or inspecting rendered pages. Trigger when asked to screenshot, verify layout, check rendering, or visually inspect a running web app.

Collapse this monorepo into a single-package layout. The chosen app's contents move to the root (src/, test/, docs/); each lib becomes a deep module at src/<lib>/. Workspace-name imports are rewritten to relative paths, dependencies are merged into the root package.json, pnpm-workspace.yaml is deleted, the root tsconfig.json switches from a references solution-config to a standard single-package config, and fallow.toml / cspell.json are reshaped to match. Run optionally on a fresh project (right after /scaffold-init) when a single-app layout fits better than the apps/libs split. The deterministic work happens in scripts/scaffold-flatten.mjs; this skill collects inputs, runs the script, and summarizes the result.

One-shot rebrand of a freshly-cloned ts-check-scaffold repo into a true empty shell for a new project. Rewrites root package.json (name, version reset to 0.0.0, description), LICENSE (author, year, license id), README.md, deletes any root CHANGELOG.md so the derived project starts with a clean release history, deletes placeholder my-app and tools packages, and scaffolds the user's requested apps and libs as bare shells. The deterministic work happens in scripts/scaffold-init.mjs; this skill just collects inputs, runs the script, and summarizes the result. Use exactly once, right after cloning the scaffold.

Bump one target's version via scripts/bump-version.mjs, summarize every commit since that target's last release into a new section in its CHANGELOG.md, and commit with a `<short>-vX.Y.Z` message. Target is either a workspace package (apps/* or libs/*) or the root pseudo-package — the scaffold itself — when no name is passed.

Verify that everything this scaffold needs is installed at the right version (node, pnpm, git, uvx for the ast-grep MCP, fallow-mcp, optional claude CLI) and that `pnpm install` has been run. Renders a checklist with copy-pasteable install hints for whatever is missing. Read-only — never installs anything itself.

Bump every workspace package in lockstep (root package.json, every packages/*/package.json, every packages/*/src/version.ts that exists) via scripts/bump-version.mjs, summarize every commit since the last release into a new CHANGELOG.md section, and commit with a `vX.Y.Z` message. Also supports `--repair-skew` to force-align the lockstep set to the root's current version without bumping. Use when cutting a release or recovering from version drift.

Bump the project version (major, minor, or patch) and add a changelog entry. Use when preparing a release, bumping versions, or the user says "/version".