Skip to content

build-fast

Quick-iteration development for small, well-scoped tasks using the command-agent pattern.

Synopsis

/build-fast <development-request> [--afk] [--git-worktree] [--git-commit] [--git-push]

/rp1-dev/build-fast <development-request> [--afk] [--git-worktree] [--git-commit] [--git-push]

Description

The build-fast command handles development requests that don't warrant the full feature workflow. It assesses request scope and either implements the changes (for small/medium scope) or redirects to /build (for large scope).

By default, changes are made in your current working directory without any git operations. Use --git-* flags to enable worktree isolation, commits, or pushing.

This command uses the command-agent pattern with scope gating and AFK mode support.

Parameters

Parameter Position Required Default Description
DEVELOPMENT_REQUEST $ARGUMENTS Yes - Freeform description of what to build
--afk Flag No false AFK (Away From Keyboard) mode — non-interactive for automation
--git-worktree Flag No false Use isolated git worktree
--git-commit Flag No false Commit changes
--git-push Flag No false Push branch to remote

Scope Assessment

The command assesses request complexity before execution:

Scope Hours Behavior
Small <2 Implements changes
Medium 2-8 Implements changes
Large >8 Redirects to /build

Assessment criteria:

Factor Small Medium Large
Files 1-3 4-7 >7
Systems 1 1-2 >2
Risk Low Medium High

AFK Mode

For automation scenarios (CI, scripts), use the --afk flag:

/build-fast "update dependency versions" --afk

/rp1-dev/build-fast "update dependency versions" --afk

AFK mode behavior:

Decision Point Behavior
KB missing Warn, continue
Tech choice Use patterns.md preference
Test scope Conservative (minimal)
Commit message Generate from request
Dirty state Commit with WIP message

All auto-decisions are logged in the summary artifact with "(AFK auto)" prefix.

Examples

Quick Fix

/build-fast "Fix the authentication bug when token expires"

/rp1-dev/build-fast "Fix the authentication bug when token expires"

Small Enhancement

/build-fast "Add a date formatting utility to utils/date.ts"

/rp1-dev/build-fast "Add a date formatting utility to utils/date.ts"

Performance Optimization

/build-fast "Optimize the database query in reports module"

/rp1-dev/build-fast "Optimize the database query in reports module"

Workflow

  1. KB loading - Progressively loads knowledge base based on request type
  2. Scope assessment - Categorizes as Small, Medium, or Large
  3. Branch: Large scope - Redirects to /build with options
  4. Branch: Small/Medium - Continues to implementation
  5. Worktree setup - Creates isolated git worktree (if --git-worktree specified)
  6. Implementation - Code changes following codebase patterns
  7. Quality checks - Format, lint, test
  8. Summary artifact - Writes documentation
  9. Finalization - Commit (if --git-commit), push (if --git-push), cleanup worktree

KB Loading

The command loads KB context progressively based on request type:

Request Type KB Files Loaded
Always index.md
Bug fix + patterns.md
Feature + architecture.md, modules.md
Refactor + architecture.md, patterns.md
Performance + architecture.md

If KB files are missing, the command warns but continues.

Git Operations

By default, build-fast makes changes in your current working directory without any git operations. Use flags to opt-in:

Flag Effect
--git-worktree Create isolated git worktree for changes
--git-commit Commit changes after implementation
--git-push Push branch to remote (requires --git-commit or --git-worktree)

With Worktree Isolation

When using --git-worktree:

  • Your changes are safe: Uncommitted work in your main repository is never touched
  • Agent works on HEAD: Changes are based on your last commit
  • Easy integration: After completion, you get a branch ready to merge or PR

After Completion

On success with git operations enabled, you receive integration options:

# Merge the branch
git merge quick-build-fix-auth

# Or cherry-pick specific commits
git cherry-pick quick-build-fix-auth

# Or create a PR
git push -u origin quick-build-fix-auth

Output

Summary Artifact

After completing a task, the command generates a summary document at:

{RP1_ROOT}/work/quick-builds/{YYYYMMDD-HHMMSS-slug}/summary.md

This provides:

  • Original request documentation
  • Files modified with change descriptions
  • Key implementation decisions
  • Verification steps performed
  • Notes and follow-up considerations

Large Scope Redirect

When scope is assessed as Large:

## REQUEST EXCEEDS SCOPE

Request: [summary]
Estimated Effort: [hours]

Why This Needs /build:
- [reasons]

Options:
1. Reduce scope: [minimal solution]
2. Phase it: [breakdown]
3. Use full workflow: Run /build {feature-id}

Recommended Quick Win: [simplest valuable alternative]

Git 2.15+ Required

Worktree isolation requires git 2.15 or later. Check your version with git --version.

  • build - For larger features requiring full workflow
  • code-check - Verify changes