Run any Skill in Manus with one click

workflowbuild-spec

Kick off autonomous feature development. Creates a git worktree, generates an implementation plan from a spec, configures the agent-loop prompt, and launches the agent loop in a new tmux pane. Use when starting work on a new feature. Triggers on "/workflow:build-spec".

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/pruett/dotfiles --skill workflowbuild-spec

Copy and paste this command into Claude Code to install the skill

Source

pruett/dotfiles

Stars9

Forks1

UpdatedFebruary 24, 2026 at 17:45

File Explorer

2 files

SKILL.md

readonly

name	workflow:build-spec
description	Kick off autonomous feature development. Creates a git worktree, generates an implementation plan from a spec, configures the agent-loop prompt, and launches the agent loop in a new tmux pane. Use when starting work on a new feature. Triggers on "/workflow:build-spec".

Feature Kickoff

Orchestrates the full setup for autonomous feature implementation in an isolated worktree. Takes a feature name, wires up the plan and prompt, and hands off to the agent loop.

Input

A feature name matching a spec in specs/<feature-name>.md.

Examples: real-time-transport, websocket-server, auth-flow

Process

1. Validate

Confirm specs/<feature-name>.md exists. Abort if not found.
Confirm AGENT-LOOP-PROMPT.md exists at project root. If missing, copy from assets/AGENT-LOOP-PROMPT.md and commit it so worktrees inherit it.

2. Create worktree

Follow git-worktree skill conventions:

mkdir -p .claude/.worktrees
git worktree add .claude/.worktrees/feat-<name> -b feat/<name>

3. Enter worktree

cd .claude/.worktrees/feat-<name>

All remaining steps happen inside the worktree.

4. Generate implementation plan

mkdir -p plans

Run /implementation-plan against specs/<feature-name>.md. Tell it to output the plan to plans/<feature-name>.md.

5. Update AGENT-LOOP-PROMPT.md

Edit the worktree's inherited copy:

Delete the entire <template-instructions> block (opening tag through closing tag, inclusive)
Replace <link-to-plan> with <feature-name> so the path reads @plans/<feature-name>.md

6. Initialize progress.txt

Create an empty progress.txt in the worktree root if one does not already exist. Ensure this file is empty.

7. Launch agent loop

Open a new tmux pane with remain-on-exit enabled so the pane stays open after the script finishes:

tmux split-window -h "tmux set-option remain-on-exit on; cd $(pwd) && caffeinate -ims agent-loop.sh"

Rules

Always validate the spec exists BEFORE creating the worktree
The worktree inherits AGENT-LOOP-PROMPT.md from main — edit the worktree copy, never the original
Do NOT commit the updated prompt or progress.txt — the agent loop handles its own commits

More from this repository

same repository

interrogate

pruett/dotfiles

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

2026-04-249

compose-component

pruett/dotfiles

Compose a new UI component following shadcn/ui authoring patterns — composable, modular, multi-export React components with Tailwind styling hooks. Use when the user wants to create a new React component, abstract an existing one, or build a composable component family (e.g., SwipeCard + SwipeCardHeader + SwipeCardItem). Triggers on "compose a component", "create a component", "abstract this into a component", "make this composable", "new UI component", "/compose-component", or when a user wants to follow shadcn/ui component patterns for a custom component.

2026-03-269

createagent-loop-prompt

pruett/dotfiles

Generate a agent-loop-prompt.md file at the project root that defines an agent loop — the repeatable task cycle an autonomous agent follows: study the plan, pick the next task, implement, validate, update progress, and commit. Also known as "Ralph" — trigger when the user says "Ralph", "the Ralph process", "set up Ralph", "create an agent loop", "generate a agent-loop-prompt.md", "set up the agent loop", or "/create:agent-loop-prompt".

2026-03-029

generateplan

pruett/dotfiles

Generate a structured, file-based implementation plan from a spec or PRD. Use when the user asks to turn a spec, PRD, or requirements document into an ordered set of implementation tasks, or requests an "implementation plan." Triggers on "/generate:plan".

2026-03-029

ingestissues

pruett/dotfiles

Triage a raw, ad-hoc markdown file of mixed issues, bugs, fixes, and feature requests into discrete, well-specified tasks written to a PRD.md file. Use when the user has a hastily written notes file containing scattered work items across multiple topics (UI fixes, backend changes, new features, bugs, etc.) and wants them organized into standalone, implementable task specs. Triggers on "/ingest:issues" or when the user asks to "triage issues", "turn notes into tasks", "organize my backlog", or "create a PRD from my notes".

2026-03-029

architecture-md

pruett/dotfiles

Generate or update an ARCHITECTURE.md file for a codebase. Use when the user asks to create, write, update, or improve an ARCHITECTURE.md, or asks for a high-level architectural overview document of their project.

2026-02-249

Source

pruett

pruett/dotfiles

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	workflow:build-spec
description	Kick off autonomous feature development. Creates a git worktree, generates an implementation plan from a spec, configures the agent-loop prompt, and launches the agent loop in a new tmux pane. Use when starting work on a new feature. Triggers on "/workflow:build-spec".

Feature Kickoff

Orchestrates the full setup for autonomous feature implementation in an isolated worktree. Takes a feature name, wires up the plan and prompt, and hands off to the agent loop.

Input

A feature name matching a spec in specs/<feature-name>.md.

Examples: real-time-transport, websocket-server, auth-flow

Process

1. Validate

Confirm specs/<feature-name>.md exists. Abort if not found.
Confirm AGENT-LOOP-PROMPT.md exists at project root. If missing, copy from assets/AGENT-LOOP-PROMPT.md and commit it so worktrees inherit it.

2. Create worktree

Follow git-worktree skill conventions:

mkdir -p .claude/.worktrees
git worktree add .claude/.worktrees/feat-<name> -b feat/<name>

3. Enter worktree

cd .claude/.worktrees/feat-<name>

All remaining steps happen inside the worktree.

4. Generate implementation plan

mkdir -p plans

Run /implementation-plan against specs/<feature-name>.md. Tell it to output the plan to plans/<feature-name>.md.

5. Update AGENT-LOOP-PROMPT.md

Edit the worktree's inherited copy:

Delete the entire <template-instructions> block (opening tag through closing tag, inclusive)
Replace <link-to-plan> with <feature-name> so the path reads @plans/<feature-name>.md

6. Initialize progress.txt

Create an empty progress.txt in the worktree root if one does not already exist. Ensure this file is empty.

7. Launch agent loop

Open a new tmux pane with remain-on-exit enabled so the pane stays open after the script finishes:

tmux split-window -h "tmux set-option remain-on-exit on; cd $(pwd) && caffeinate -ims agent-loop.sh"

Rules

Always validate the spec exists BEFORE creating the worktree
The worktree inherits AGENT-LOOP-PROMPT.md from main — edit the worktree copy, never the original
Do NOT commit the updated prompt or progress.txt — the agent loop handles its own commits