Skip to content

Remove epic.sc; move its docs pass into implement-enhanced.sc - #30

Merged
adamw merged 2 commits into
masterfrom
remove-epic-flow
Jul 28, 2026
Merged

Remove epic.sc; move its docs pass into implement-enhanced.sc#30
adamw merged 2 commits into
masterfrom
remove-epic-flow

Conversation

@adamw

@adamw adamw commented Jul 28, 2026

Copy link
Copy Markdown
Member

epic.sc was implement.sc with three agents pinned to concrete accessors and a trailing docs stage:

Step implement.sc epic.sc
Plan planningAgent claude.opus
Session codingAgent claude
Reviewers reviewAgent codex
Per-task loop identical identical
Docs pass stage("Update documentation")

The first three differences are pure configuration — this settings file makes implement.sc behave identically:

planningAgent = claude:opus
codingAgent   = claude
reviewAgent   = codex

So the flow demonstrated a capability rather than providing one, at the cost of a fourth near-identical plan-then-implement entry in a picker where the one-line description is all the user sees. Its name didn't help either: every flow here is multi-task, and epicId already means something else in Plan.

The docs stage was the only thing it did that no other flow does. It moves to implement-enhanced.sc (the full-service variant), placed before openPrFromBranch so the docs land in the PR rather than in a separate commit — and as its own stage, keeping the push a later stage than the edits it pushes (ADR 0018 §3.2 R8). Its description line now reads // Plan (self-reviewed), implement per task, update docs, then open a PR.

Follow-on reference updates: flow lists in README.md and examples/runnable/README.md; the expected index in BuiltInFlowsTest; flowScripts in ScalaCliSmokeTest; and FlowCompilesTest.epicFlowShape renamed to crossBackendReviewShape (the API surface it compile-checks is still worth keeping). README.md's concrete-accessor example now cites issue-pr-bugfix.sc, which pins claude.sonnet for its reproduction checks. ADR references are left alone as historical record.

Verified: scala-cli compile flows/implement-enhanced.sc, sbt scalafmtCheckAll, the shell flow suites, and runner/Test/compile all pass.

adamw added 2 commits July 28, 2026 09:47
epic.sc was implement.sc with three agents pinned to concrete accessors
(claude.opus plans, claude implements, codex reviews) plus a trailing
docs stage. The pinning is entirely expressible in settings —
planningAgent = claude:opus / codingAgent = claude / reviewAgent = codex
— so the flow demonstrated a capability rather than providing one, at
the cost of a fourth near-identical plan-then-implement entry in the
picker.

The docs stage was the only thing it did that no other flow does; it
moves to implement-enhanced.sc, where it runs before the push so the
docs land in the PR rather than in a separate commit.

README's concrete-accessor example now cites issue-pr-bugfix.sc, which
pins claude.sonnet for its reproduction checks.
No shipped flow names a backend any more — issue-pr-bugfix.sc's two
reproduction checks were the last, and they now follow the coding role.
The guidance stands on its own example instead of pointing at a flow.
@adamw
adamw merged commit fc099c1 into master Jul 28, 2026
5 checks passed
@adamw
adamw deleted the remove-epic-flow branch July 28, 2026 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant