The trick is to parametrize the /compact. Something like "/compact focus on the XZY, the next steps will be FOOBAR, and keep a high level summary of BARFOO"

That makes the compaction summary a lot more focused and useful.

edit: But a work log/PRD is essential regardless!

▲

felciano 5 days ago | parent | next [-]

I’ve been using PRD specs at kick things off, but curious about how to a “work log”. Are there examples of how to do this with CC?

	▲	danielbln 5 days ago \| parent [-]
		"Implement phase 1 of the PRD, when done update the PRD and move on to phase 2."

▲

raduan 5 days ago | parent | prev | next [-]

yep, exactly, using it like this myself

I think both /compact and /clear are valuable / have their own use cases.

my small mental mode: - really quick fix / need to go over board with context -> just /compact + continue pushing - next phase -> ask for handover document or update worklog, and then send fresh one to new phase.

▲

xd1936 5 days ago | parent | prev [-]

Thank you for this. I didn't know this was an option.