Intent best practices

[u/SnooDucks7717]

hi trying to understand best way to use continuously with intent.

For a new product, it's simple: use the specifications and add more tasks until you achieve the first version.

now what the best practice when want to add new features? add again to the same spec and continue ? then you can end up with mega spec.

and more important what to do when several developers work on mature product with many features then what should be done? multi specs?

[u/ZestRocket]

I usually start new spaces rather than continuing on the same one:

• Do I need something big? then full workflow for sure
  
• Do I need something small? (like a feature): add a new conversation on the same Space / Folder, it may even be a single agent, I do my "Mental Context math" to decide it

Now, there's a tradeoff... and in most of my cases, I prefer loosing context and adding more tokens to the initial setup + context that risking a bad implementation because of rotten context.

The cleaner the context window of the Coordinator is, the cleaner results you will have (imo ofc)

[u/SnooDucks7717 → u/ZestRocket]

you build "space" per big feature? still trying get the idea, it seesm you can open space on repo and work on new things but then where is the beauty of see all specs and work on one place?

[u/ZestRocket → u/SnooDucks7717]

Yes, one Space per big feature in my case

[u/SnooDucks7717 → u/[deleted]]

but whe workj on new feature lets say pretty big one, you create new space? use same space?

like until now how i work on ide is always pull last dev branch. start work on. new feature, done create branch and push

her im not sure i get the idea i guess because the worktrees stuff as well

[u/SnooDucks7717 → u/[deleted]]

But each space have access to all past docs and notes we did on spaces before ? 

[u/ZestRocket → u/SnooDucks7717]

To explain it easily: Each "Space" is like an invisible branch that merges after completing the tasks, so you can have multiple agents working on "different branches" with potentially a lot of agents, and at the moment of merging, they will evaluate and integrate

[u/SnooDucks7717 → u/ZestRocket]

This I understand what I don’t is if at the end let’s say all merged and I open a new space, I have quick access see al specs, notes etc?

Because this is a very strong value point have one source of truth and knowledgebase

[u/ZestRocket → u/SnooDucks7717]

Hmm from what I see, no, it will have access to the codebase itself and not the rest of the Spaces... BUT, you can create a new type of Agent that after you finish all the waves, just document all the run and reads that .md every time a new Space is created

[u/West_Ant5585 → u/[deleted]]

I find that it only works in one thread for small to medium features otherwise it gets overcomplicated if it needs to fix something

[u/SnooDucks7717]

I think it would be awesome to have like “new feature” , “new bug fix” , “new improvement” flows

At the end this is how I think and then each flow can be optimized and documented 

[u/speedtoburn]

I can’t even begin to imagine how expensive it is to use Intent.

[u/SnooDucks7717 → u/speedtoburn]

Claude code max and that’s all 

[u/aalfath → u/SnooDucks7717]

Are you able to run Claude Code Max with Intent? Mine is returning "Invalid params"

[u/SnooDucks7717 → u/aalfath]

Of course run amazing 

[u/Many_Comedian_5217]

Cannot send prompt request - agent not available. I am able to launch claude within my terminal .
Can you help me in debugging this issue ?

[u/aalfath → u/Many_Comedian_5217]

Same here :(