build-fast¶
Quick-iteration development for small, well-scoped tasks using the command-agent pattern.
Synopsis¶
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 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 |
--confirm-plan |
Flag | No | false |
Enable plan review checkpoint before implementation |
--review |
Flag | No | false |
Enable task-reviewer validation after implementation |
--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:
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.
Confirm Mode¶
For interactive review of plans before execution, use the --confirm-plan flag:
Confirm mode adds two checkpoints:
Plan Review Checkpoint¶
After planning, before implementation begins:
## Plan Review
**Scope**: Medium
**Estimated Effort**: 3 hours
**Artifact**: .rp1/work/quick-builds/20260201-143022-refactor-payment/plan.md
**Tasks**:
1. Extract payment validation logic
2. Create PaymentProcessor class
3. Update existing callers
**Files**: src/payment.ts, src/utils/validation.ts
Options:
1. "Continue" - Proceed with implementation
2. "Revise" - Re-plan with your feedback
3. "Stop" - Exit (artifact preserved for reference)
Post-Implementation Checkpoint¶
After implementation completes:
## Implementation Complete
**Branch**: quick-build-refactor-payment
**Artifact**: .rp1/work/quick-builds/20260201-143022-refactor-payment/plan.md
Review the changes, then:
1. "Done" - Finish workflow
2. "Add/Edit" - Describe additional changes needed
AFK overrides confirm-plan
When --afk is specified, --confirm-plan is automatically disabled since AFK mode is non-interactive.
Examples¶
Quick Fix¶
Small Enhancement¶
Performance Optimization¶
With Plan Review¶
Workflow¶
The command executes in four phases:
Phase 1: Planning¶
- KB loading - Progressively loads knowledge base based on request type
- Scope assessment - Categorizes as Small, Medium, or Large
- Large scope redirect - Redirects to
/buildwith options (if scope is Large) - Plan review checkpoint - Presents plan for approval (if
--confirm-planspecified)
Phase 2: Execution¶
- Task execution - Code changes following codebase patterns
- Quality checks - Format, lint, test
Phase 3: Review (Optional)¶
- Task review - Validates implementation against requirements (if
--reviewspecified) - Retry on failure - Re-executes tasks with reviewer feedback (max 1 retry)
Phase 4: Finalization¶
- Push - Push branch to remote (if
--git-pushspecified) - Post-implementation checkpoint - Opportunity for additional changes (if
--confirm-planspecified)
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-commit |
Commit changes after implementation |
--git-push |
Push branch to remote (requires --git-commit) |
Output¶
Summary Artifact¶
After completing a task, the command generates a summary document at:
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]
Related Commands¶
build- For larger features requiring full workflowcode-check- Verify changes