Redesign the ticket-takedown process: one design phase takes up to an hour and millions of tokens #966

New issue

Open

opened 2026-10-07 17:51:34 +00:00 by jared · 0 comments

jared commented

2026-10-07 17:51:34 +00:00

Owner

Problem

One ticket-takedown design phase takes 20 to 66 minutes and uses millions of tokens. Five parallel runs on 2026-10-07 ran for over an hour, and the owner stopped three of them. The process must be redesigned before more tickets go through it.

Observed

Run times from run.yaml:

Run	Rounds	Duration
cc-plugins `docs/takedown/83`, 2026-10-05	1	21 min
cc-plugins `docs/takedown/86`, 2026-10-05	2	46 min
cc-os `docs/takedown/964`, 2026-10-07	0	22 min
cc-os `docs/takedown/965`, 2026-10-07	3	66 min

Each round takes about 20 minutes in both sets. The 2026-10-07 runs also had five runs in parallel and an owner direction that leads to larger designs.

Likely causes, from the #965 run (16 dispatched agents, plus sub-agents that the designers started):

Blast radius runs on every design: 5 times on #965, 15 to 21 minutes each.
Each designer and challenger builds the design in a scratch copy, writes the tests, and runs the full suite. /os-sdlc:implement then does the same work again.
Rounds are serial: challenger, then blast radius, then judge, about 20 to 30 minutes for each round.
Every role runs on opus, and each agent uses 100k to 170k tokens.

Related: #962 (the eval harness and the skill run different pipelines).

Owner's plan for this ticket

Review how the takedown process is built, and compare the 2026-10-05 runs with the 2026-10-07 runs to find what differs.
Brainstorm ideas.
Write a rough-draft process from the best idea.
Tune that draft with /autoresearch.

This ticket gives no approach on purpose (see #960).

Reproduce

n/a: process ticket. Run files are in docs/takedown/96*/ (cc-os, branch prism-architect) and /home/jared/dev/cc-plugins/docs/takedown/.

Origin

Trigger: takedown design phase on #960 to #965, 2026-10-07
Improvised this session: stopped the #960, #961 and #962 runs after their entry verdict, by owner decision
Chain: design phase takes over an hour ← every design gets a full build, suite run and blast radius, in serial rounds ← DESIGN: plugins/os-sdlc/skills/ticket-takedown/SKILL.md steps 4 to 8
Root candidate: this ticket
Where: plugins/os-sdlc/skills/ticket-takedown/SKILL.md; plugins/os-sdlc/skills/ticket-takedown/references/
Session: 1e202fec-cce9-40fd-aeb9-24a9faa69d96
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-prism-architect/1e202fec-cce9-40fd-aeb9-24a9faa69d96.jsonl

## Problem One ticket-takedown design phase takes 20 to 66 minutes and uses millions of tokens. Five parallel runs on 2026-10-07 ran for over an hour, and the owner stopped three of them. The process must be redesigned before more tickets go through it. ## Observed Run times from `run.yaml`: | Run | Rounds | Duration | | --- | --- | --- | | cc-plugins `docs/takedown/83`, 2026-10-05 | 1 | 21 min | | cc-plugins `docs/takedown/86`, 2026-10-05 | 2 | 46 min | | cc-os `docs/takedown/964`, 2026-10-07 | 0 | 22 min | | cc-os `docs/takedown/965`, 2026-10-07 | 3 | 66 min | Each round takes about 20 minutes in both sets. The 2026-10-07 runs also had five runs in parallel and an owner direction that leads to larger designs. Likely causes, from the #965 run (16 dispatched agents, plus sub-agents that the designers started): 1. Blast radius runs on every design: 5 times on #965, 15 to 21 minutes each. 2. Each designer and challenger builds the design in a scratch copy, writes the tests, and runs the full suite. `/os-sdlc:implement` then does the same work again. 3. Rounds are serial: challenger, then blast radius, then judge, about 20 to 30 minutes for each round. 4. Every role runs on opus, and each agent uses 100k to 170k tokens. Related: #962 (the eval harness and the skill run different pipelines). ## Owner's plan for this ticket 1. Review how the takedown process is built, and compare the 2026-10-05 runs with the 2026-10-07 runs to find what differs. 2. Brainstorm ideas. 3. Write a rough-draft process from the best idea. 4. Tune that draft with `/autoresearch`. This ticket gives no approach on purpose (see #960). ## Reproduce n/a: process ticket. Run files are in `docs/takedown/96*/` (cc-os, branch prism-architect) and `/home/jared/dev/cc-plugins/docs/takedown/`. ## Origin - Trigger: takedown design phase on #960 to #965, 2026-10-07 - Improvised this session: stopped the #960, #961 and #962 runs after their entry verdict, by owner decision - Chain: design phase takes over an hour ← every design gets a full build, suite run and blast radius, in serial rounds ← `DESIGN`: plugins/os-sdlc/skills/ticket-takedown/SKILL.md steps 4 to 8 - Root candidate: this ticket - Where: plugins/os-sdlc/skills/ticket-takedown/SKILL.md; plugins/os-sdlc/skills/ticket-takedown/references/ - Session: 1e202fec-cce9-40fd-aeb9-24a9faa69d96 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-prism-architect/1e202fec-cce9-40fd-aeb9-24a9faa69d96.jsonl

jared added the

plugin/os-sdlc

filed-by/user

labels

2026-10-07 17:51:34 +00:00

jared referenced this issue

2026-10-07 18:49:57 +00:00

Make evidence collect skip git-ignored files #967

jared added the

category/investigation

label

2026-10-10 13:31:42 +00:00