diff options
| author | Claude Code <claude@terst.org> | 2026-08-15 18:06:00 +0000 |
|---|---|---|
| committer | Claude Code <claude@terst.org> | 2026-08-15 18:06:00 +0000 |
| commit | a6d58e009efcc06e7b5221d75ebed36533786dce (patch) | |
| tree | cfeded4c1bb8e61a4c117aced0b42e7d4aa0e15a /feedback_default_subagent_driven_execution.md | |
| parent | eb0932bddad0daa47c36cd20599944c3dc45482a (diff) | |
Titanium and tungsten had grown two separate, unreconciled memory sets
for the same -workspace scope. Ports over 18 titanium-only entries
(12 claudomator files, the fork-scope-creep lesson, the doot Google
Tasks OAuth limitation, the default-subagent-driven-execution
preference, scout's Facebook priority, Hawaii GIS endpoints), merges
two true duplicates into their existing tungsten files rather than
keeping parallel copies (the migration-rename incident -- same
022->023 rename, same commit, titanium's version added the
confirmed-safe-to-patch-prod-directly carve-out tungsten's didn't
have; the APK build OOM note, folded into project_doot_widget_build.md
as a RAM-constrained-host fallback), and marks
doot_future_task_scheduling_ideas.md as historical now that all four
of its backlog items (budgets, labels/projects, buckets, chains) are
built.
Diffstat (limited to 'feedback_default_subagent_driven_execution.md')
| -rw-r--r-- | feedback_default_subagent_driven_execution.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/feedback_default_subagent_driven_execution.md b/feedback_default_subagent_driven_execution.md new file mode 100644 index 0000000..a13c646 --- /dev/null +++ b/feedback_default_subagent_driven_execution.md @@ -0,0 +1,14 @@ +--- +name: feedback-default-subagent-driven-execution +description: "User wants Subagent-Driven Development as the default execution choice for implementation plans, without being asked each time" +metadata: + node_type: memory + type: feedback + originSessionId: 61c70ef2-1b1b-456c-9cbd-ad1f76ea2401 +--- + +When presenting the writing-plans skill's execution-choice prompt ("1. Subagent-Driven" vs "2. Inline Execution"), default to Subagent-Driven Development without waiting for the user to pick. + +**Why:** User replied "1, always" when asked — explicitly signaling this choice should stick across future plans in this project (doot), not just this one instance. + +**How to apply:** Still present the two options briefly for transparency/interruptibility, but proceed straight into `superpowers:subagent-driven-development` (dispatch Task 1's implementer) rather than pausing to wait for an answer, unless the user says otherwise for a specific plan. |