Skip to content

build

End-to-end feature workflow orchestrator. Runs the complete 6-step lifecycle (requirements → design → build → verify → follow-up → archive) in a single command.

Synopsis

/build feature-id [requirements] [--afk] [--git-worktree] [--git-commit] [--git-push] [--git-pr]

/rp1-dev/build feature-id [requirements] [--afk] [--git-worktree] [--git-commit] [--git-push] [--git-pr]

Description

The build command is the primary entry point for feature development. It orchestrates all workflow steps automatically with smart resumption — detecting existing artifacts and continuing from where you left off.

Key Features

  • Single command: No need to run individual steps manually
  • Smart resumption: Detects existing artifacts and resumes from the right step
  • AFK mode: Run autonomously without user interaction
  • Safe defaults: No git operations unless explicitly requested via flags
  • Opt-in git operations: Use --git-* flags for worktree, commit, push, PR
  • Builder-reviewer architecture: Quality-gated implementation with feedback loops

Parameters

Parameter Position Required Default Description
FEATURE_ID $1 Yes - Feature identifier (used for directory and branch names)
REQUIREMENTS $2 No "" Initial requirements text or context
--afk flag No false Non-interactive mode (auto-proceed, no prompts)
--git-worktree flag No false Use isolated git worktree
--git-commit flag No false Commit changes after build
--git-push flag No false Push branch to remote
--git-pr flag No false Create PR (implies --git-push and --git-commit)

Workflow Steps

The command orchestrates these steps:

Step What Happens Artifact
1. Requirements Collect and document requirements requirements.md
2. Design Generate technical design + tasks design.md, tasks.md
3. Build Implement via builder-reviewer Code changes
4. Verify Validate against acceptance criteria verification-report.md
4.1 User Review Manual verification checkpoint User decision
5. Follow-up Add more work if needed Loops to Build
6. Archive Store completed feature Archived artifacts

Interactive Mode (Default)

By default, /build runs in interactive mode, presenting approval gates between major workflow stages. These gates allow you to review artifacts, provide feedback, and control workflow progression.

Approval Gates

Gate After Options Purpose
Gate 1 Requirements Continue, Revise, Stop Review requirements before design
Gate 2 Design Continue, Revise, Stop Review design and task breakdown
Gate 3 Tasks Continue, Revise, Stop Review implementation plan
Gate 4 Build Continue, Add Task, Stop Review implementation before verify

Gate Options

At each gate, you can choose:

Option Behavior
Continue Proceed to the next workflow stage
Revise Provide feedback and re-run the current stage
Stop Exit the workflow (all artifacts preserved)
Add Task (Gate 4 only) Add additional implementation work

Feedback Loop

When you select Revise, you're prompted for feedback. This feedback is incorporated into the re-execution:

Stage How Feedback is Used
Requirements Appended to REQUIREMENTS parameter
Design Appended to requirements.md as addendum
Tasks Passed as UPDATE_CONTEXT to feature-tasker
Build Creates ad-hoc task for builder-reviewer

AFK Mode

Use --afk to bypass all gates and run the workflow autonomously:

/build my-feature --afk

In AFK mode:

  • All approval gates are skipped
  • Workflow proceeds automatically through all stages
  • Changes remain in working directory unless --git-commit is specified

Smart Resumption

The command detects existing artifacts and resumes from the appropriate step:

Existing Artifacts Resumes From
None Requirements
requirements.md Design
requirements.md + design.md Build
All + tasks.md (completed) Verify
All + verification-report.md Archive

If you stopped at a gate, resuming /build continues from the next stage.

Examples

Start a New Feature

/build user-authentication

/rp1-dev/build user-authentication

With Initial Requirements

/build dark-mode "Add dark mode toggle to settings page with system preference detection"

/rp1-dev/build dark-mode "Add dark mode toggle to settings page with system preference detection"

AFK Mode (Autonomous)

/build api-refactor --afk

/rp1-dev/build api-refactor --afk

Your code is safe

Even in AFK mode, all changes are isolated to a separate branch. Nothing is merged until you review and approve.

With PR Creation

/build new-feature --git-pr

/rp1-dev/build new-feature --git-pr

With Git Commit Only

/build new-feature --git-commit

/rp1-dev/build new-feature --git-commit

Output

Location: $RP1_ROOT/work/features/<feature-id>/

Contents:

  • requirements.md - Feature requirements
  • design.md - Technical design
  • tasks.md - Implementation tasks
  • verification-report.md - Verification results
  • field-notes.md - Implementation notes (if any)
Command When to Use
build-fast Small, well-scoped tasks that don't need full planning
feature-edit Mid-stream changes during build
feature-unarchive Restore archived features
validate-hypothesis Test risky design assumptions

See Also