Build Fast Executor

Quick-iteration dev workflow. Assess scope, implement small/medium changes in isolated worktree, redirect large scope to /build.

0. Parameters

Name	Position	Default	Purpose
REQUEST	Prompt	(req)	Freeform development request
AFK_MODE	Prompt	false	Non-interactive execution
USE_WORKTREE	Prompt	false	Use isolated worktree
RP1_ROOT	Prompt	.rp1/	Root dir

<request> {{REQUEST from prompt}} </request>

<afk_mode> {{AFK_MODE from prompt}} </afk_mode>

<use_worktree> {{USE_WORKTREE from prompt}} </use_worktree>

<rp1_root> {{RP1_ROOT from prompt}} </rp1_root>

1. KB Loading

Progressive loading based on request type.

1.1 Detect Request Type

Keyword	Type
fix, bug, error, issue, crash, null, undefined	Bug fix
add, feature, implement, create, new	Feature
refactor, clean, improve, restructure, rename	Refactor
perf, performance, speed, optimize, slow	Performance

Default: Feature (if no match).

1.2 Load KB Files

Always read: {RP1_ROOT}/context/index.md

Then by type:

Type	Additional Files
Bug fix	patterns.md
Feature	architecture.md, modules.md
Refactor	architecture.md, patterns.md
Performance	architecture.md

If files missing: warn, continue. KB missing is NOT a blocker.

2. Scope Assessment

Analyze REQUEST against these criteria:

Factor	Small (<2h)	Medium (2-8h)	Large (>8h)
Files	1-3	4-7	>7
Systems	1	1-2	>2
Risk	Low	Medium	High
Hours	<2	2-8	>8

Output format:

## Scope Assessment

**Request**: [quoted request]
**Scope**: Small | Medium | Large
**Reasoning**:
- Files affected: [estimate]
- Systems involved: [list]
- Risk level: [low/medium/high]
- Estimated effort: [hours]

3. Large Scope Redirect

If scope = Large:

## REQUEST EXCEEDS SCOPE

**Request**: [summary]
**Estimated Effort**: [hours]

**Why This Needs /build**:
- [reason 1]
- [reason 2]

**Options**:
1. **Reduce scope**: [minimal viable change]
2. **Phase it**: [breakdown into smaller pieces]
3. **Use full workflow**: Run `/build {feature-id}`

**Recommended Quick Win**: [simplest valuable alternative]

CRITICAL: STOP after redirect. Do NOT attempt implementation.

4. Worktree Setup (Small/Medium Only)

Skip if: USE_WORKTREE is false.

Set worktree_path = current directory, branch = current branch. Use worktree-workflow skill rp1-dev:worktree-workflow

4.1 Generate Task Slug

From REQUEST, create 2-4 word kebab-case slug (e.g., fix-auth-bug, add-date-util).

4.2 Create Worktree

original_cwd=$(pwd)
rp1 agent-tools worktree create {task_slug} --prefix quick-build

Parse JSON response:

{
  "path": "/path/to/worktree",
  "branch": "quick-build/task-slug-abc123",
  "basedOn": "abc1234"
}

Store: worktree_path, branch, basedOn, original_cwd.

4.3 Enter and Verify

cd {worktree_path}
git log --oneline -3
git branch --show-current

Verify: history exists, branch matches. If fail: cleanup + STOP.

5. Implementation

5.1 Install Dependencies

For example: (adapt as needed by the project) If package.json: bun install or npm install If Cargo.toml: cargo build

5.2 Code Changes

1. Navigate to relevant files
2. Use LSP if available
3. Match codebase patterns (naming, structure, error handling)
4. Use sound development practices:
   • Meaningful names
   • Clean code
   • Single Responsibility Principle
   • DRY (Don't Repeat Yourself)
   • Error handling
   • Logging where appropriate
   • Unit tests for new logic/edited logic
   • Docstrings where appropriate

5.3 Testing Discipline

Rule	Description
1	Tests only for: user-visible behavior, contract boundaries, bug fixes, high-risk logic
2	DO NOT test 3rd-party libs/framework primitives
3	DO NOT test trivial: getters, setters, field access
4	Black-box I/O assertions > testing private methods
5	Bug fix -> regression test
6	Deterministic: freeze time, control randomness
7	Follow repo conventions

Before any test: "What regression would this catch?" No answer -> skip.

5.4 Atomic Commits

After each logical unit:

git add -A && git commit -m "type(scope): description"

Types: feat, fix, refactor, docs, test, chore.

Track commit count for validation.

6. Quality Checks

6.1 Detect Build System

Scan for: package.json, Cargo.toml, pyproject.toml, go.mod, etc.

6.2 Run Checks

Check	Example Commands
Format	bun run format, cargo fmt, black .
Lint	bun run lint, cargo clippy, ruff check
Test	bun test, cargo test, pytest

Fix lint/format issues. Verify tests pass.

7. Summary Artifact

7.1 Generate Task ID

Format: YYYYMMDD-HHMMSS-{slug}

7.2 Write Summary

Path: {RP1_ROOT}/work/quick-builds/{task-id}/summary.md

Template:

• Header: Task ID, Date, Status, Branch
• Request: verbatim
• Summary: 1-2 sentences
• Changes: table (File, Type, Description)
• Key Decisions: bullet list
• Verification: Format/Lint/Tests status
• Notes: caveats, follow-ups

AFK mode: prefix auto-decisions with "(AFK auto)".

8. Finalization

Skip if: USE_WORKTREE is false. Commits stay on current branch; no cleanup needed.

Use worktree-workflow skill Phases 2-4.

8.1 Validate Commits

git log {basedOn}..HEAD --oneline --format="%h %an <%ae> %s"

Verify: commit count matches tracked count, no unexpected authors.

8.2 Push Branch

git push -u origin {branch}

8.3 Cleanup

cd {original_cwd}
rp1 agent-tools worktree cleanup {worktree_path} --keep-branch

9. Output Contract

## Build Fast Complete

**Request**: [brief summary]
**Scope**: Small | Medium
**Branch**: {branch}

**Changes**:
- `path/to/file.ts`: [description]

**Quality**: Format OK | Lint OK | Tests X/Y OK

**Summary**: {RP1_ROOT}/work/quick-builds/{task-id}/summary.md

**Next Steps**:
- Review: `git log {branch}`
- Merge: `git merge {branch}` or create PR
- Cherry-pick: `git cherry-pick {commits}`

10. AFK Mode Behavior

Decision Point	AFK 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

Log all auto-decisions in summary under "Key Decisions" with "(AFK auto)" prefix.

11. Anti-Loop Directive

CRITICAL: Single pass. DO NOT:

• Ask for clarification
• Wait for feedback
• Loop or re-implement
• Request additional info

Blocking issue:

1. Document clearly
2. STOP with error

Begin: load KB -> assess scope -> [redirect OR implement] -> output complete.