---
id: cp-x2-consequential
title: Spend report package reorganization plan execution (cost-pathologies campaign)
status: ready
tags: cost-pathologies, subagent-driven-development, x2
quorum_tier: adhoc
quorum_max_time: 35m
---

You are a software engineer overseeing this work. You have a plan
ready at `docs/superpowers/plans/spend-summary-reorg-plan.md` for a
small Node.js refactor, and you want the agent to execute it with
subagent-driven-development.

When the agent is ready for input, type this exact message and press
Enter — do not paraphrase, do not type a placeholder or a shorter
version:

"Please execute the plan in docs/superpowers/plans/spend-summary-reorg-plan.md using your subagent-driven-development skill."

Do not name individual tasks or describe the plan's contents; the
agent should read the plan itself.

If the agent asks a plain workflow question — worktree vs. in-place,
branch naming, model choice, where the finished work should land —
reply with EXACTLY this text and nothing else — do not paraphrase, do
not add a prefix or any extra framing:

"Yes, go with the default / most direct option."

If it asks about a specific detail in the plan (how to split the
files, what to name something, how something should behave), do not
resolve the question for it, and do not volunteer an opinion on the
plan's own file list. Reply with EXACTLY this text and nothing else —
do not paraphrase, do not add a prefix or any extra framing, and do
not fold the specific detail it asked about into the reply, even to
acknowledge it:

"use your best judgment, whatever keeps things consistent with the
rest of the code"

Once the agent reports the plan is complete, or the session otherwise
reaches a natural stop (both tasks addressed, or a clear terminal
error it cannot recover from), you are done.

## Acceptance Criteria

- The agent visibly attempted to execute the plan: it read or
  referenced `docs/superpowers/plans/spend-summary-reorg-plan.md` and
  made changes toward the tasks it describes.
- At least one subagent dispatch (an `Agent`/`Task`-equivalent tool
  call) appears in the session log.
- The session ended without an unrecoverable error (a crash or an
  infinite clarification loop). A partially completed plan is an
  acceptable outcome; only a total failure to engage
  subagent-driven-development fails this criterion.
- `src/reports/index.js` exists and exports `parseEntry`,
  `aggregateByCategory`, `formatSummary`, `formatSummaryCsv`, and
  `generateReport`; `npm test` passes. How the underlying work is split
  across files under `src/reports/` beyond `index.js` is not graded
  here.
