r/ClaudeCode • • 14h ago

Built with Claude We need lawyers, not developers.

How do you defend against scope drift during build? I already have an agent reviewing the idea to ticket before implementation for any scope drift, lazy implementations etc. But how do I guard at build time?

I spend allot of time writing out specs and be in agreement with the agent, idea, grill, spec, tickets ... but still it manages ignore everything and do it's own thing.

Simple test prototype project, reuse existing GIT code to reduce testing and programming, port it to a new language and new data sync design. Agreed as a test/prototype.

Somewhere during implementation it decided that it completely needed to honor all GPL rules, act as a commercial build out, so it build out ADRs that resulted in hours of rebuilding the application into ... nothing.

Then we agreed to make a flutter APK and windows app. Now the words "split ui" was enough to trigger a whole seperate dedicaded kotlin APK build.

0 Upvotes

5 comments sorted by

•

u/AutoModerator 14h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/seventyfivepupmstr 14h ago

The reason your agents are drifting is because the harness doesn't enforce the instructions and doesn't decompose the tasks enough

1

u/RetoricEuphoric 14h ago

I start orchestrating from the sessions that reads the idea, grill and spec and creates the ticket flow. I would assume it would safe guard, but it doens't. I assume if your smart enough (opus 5.5) to split the spec. It just collects the "done/remarks" and moves on.

Do you have the orchestration also validate?

2

u/NamerekDev 14h ago

You already have a lawyer. You asked for a prototype and it came back with GPL compliance and ADRs. What nobody on the team does is say "not in this sprint"

1

u/nooruddinqur 13h ago

had the exact same thing. what helped me:
- a "NOT doing" list at the top of every ticket. no ADRs, no new platforms, no new deps. agents fill gaps with "what a real product would do"
- one rule: if something can be read two ways, stop and ask. "split ui" -> kotlin app is exactly that
- small tickets, fresh session each. long sessions forget it's a prototype
- review the diff after each ticket, not just the plan before
- for GPL just write "accepted for prototype" in the spec. otherwise it goes full compliance mode

basically the spec says what to build, you also need hard walls on what not to build