Skip to content

magnus919/hermes-droid / factory-droid

factory-droid

Verified

Use this skill when delegating coding work to Factory Droid's droid CLI for code analysis, edits, specification-first implementation, worktree isolation, or multi-agent missions. Do not use it for small direct edits or when Factory Droid is unavailable.

references/advanced-operations.md

View on GitHub
# Advanced Operations

Load this reference when a coding task must continue across runs, needs a bounded tool surface, or needs deliberate quality/cost control.

## Continue or Fork a Session

Continue when the same task needs more work; fork when testing a different approach without changing the original session.

```sh
droid exec --session-id session-id "Run the focused tests and address the remaining failure."
droid exec --fork session-id "Try the smaller implementation without the new dependency."
```

Capture a session ID from structured output when the task may need follow-up.

## Reasoning Effort

Use the model default unless the task warrants a deliberate trade-off. `--reasoning-effort` controls the main model; `--spec-reasoning-effort` controls planning in spec mode.

```sh
droid exec -r high "Review this migration plan for failure modes."
droid exec --use-spec --spec-reasoning-effort high --auto medium "Plan and implement the migration."
```

Supported levels depend on the selected model. Check `droid exec --help` before pinning one.

## Tool Surface

Inspect available tools before restricting them. Prefer the smallest useful tool surface for high-impact tasks.

```sh
droid exec --list-tools
droid exec --enabled-tools ApplyPatch "Refactor the module without shell commands."
droid exec --auto medium --disabled-tools execute-cli "Edit the documentation without running commands."
```

Tool identifiers depend on the selected model and installed Droid version.

## Working Directory

Use `--cwd` when the invoking environment cannot set the process working directory directly:

```sh
droid exec --cwd /path/to/repository --auto medium "Run focused tests and fix the reported failure."
```

Use one working-directory mechanism, not both, when they would disagree.

## Search Local History

Search local Droid sessions before repeating prior investigation:

```sh
droid search --json "authentication retry"
droid search --kind tool_result --limit-sessions 5 "pytest"
```

`--reindex` rebuilds the local search cache; use it only when search results are clearly stale.

## Source Check

These controls are version-sensitive. Verify them against `droid --help` and `droid exec --help` before updating this reference.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall