Are Rebuild

Reconstruct a project from specification documents using agents-reverse-engineer.

Steps

1. Read version: Read .claude/ARE-VERSION → store as $VERSION. Show the user: agents-reverse-engineer v$VERSION

2. Run the rebuild command in the background using run_in_background: true:

   npx agents-reverse-engineer@$VERSION rebuild --backend claude $ARGUMENTS
   

3. Monitor progress by polling the latest progress log:

   • Wait ~15 seconds (use sleep 15 in Bash), then use Glob to find the latest .agents-reverse-engineer/progress-*.log file, and Read it (use the offset parameter to read only the last ~20 lines for long files)
   • Show the user a brief progress update (e.g. "4/12 rebuild units completed")
   • Check whether the background task has completed using TaskOutput with block: false
   • Repeat until the background task finishes
   • Important: Keep polling even if no progress log exists yet (the command takes a few seconds to start writing)

4. On completion, read the full background task output and summarize:

   • Number of rebuild units processed
   • Files generated and output directory
   • Any failures or partial completions

This reads spec files from specs/, partitions them into ordered rebuild units, and processes each via AI to generate source files.

Options:

• --dry-run: Show rebuild plan without making AI calls
• --output <path>: Output directory (default: rebuild/)
• --force: Wipe output directory and start fresh
• --concurrency N: Control number of parallel AI calls (default: auto)
• --fail-fast: Stop on first failure
• --debug: Show AI prompts and backend details
• --trace: Enable concurrency tracing to .agents-reverse-engineer/traces/

Exit codes: 0 (success), 1 (partial failure), 2 (total failure)

Converted and distributed by TomeVault — claim your Tome and manage your conversions.