Solatis Claude Config

[interconnectedMe]

Hello,

I can't quite remember how I discovered this repo...but essentially I am trying to herd cats, and think I hit a wall with guardrails, hooks, red-team checks, hold points, adversarial reviews....it was getting silly.

Perhaps I found your repo while looking for 'smaller context' solutions. And I liked the engineering-style approach a lot.

So, currently, broad brushtrokes, I'm using a forked & customised kanbn task card system for tasks, with tasks created by a Planner. Coder does task. Planner Review, reviews task.

It started so simply ;-)

Then Codex destroyed days of work by overwriting a 'dirty repo' because it 'needed to work out what had been done from a clean state'....and my journey into insanity ensued.

I have gone through an 'expand the rules/gates etc', then, realising that does not work, and there is too much 'technical debt', and Claude and Codex are still failing, and I am sinking....I am now going more down the route in your repo: atomic tasks, much tighter context control, leading to simpler verification.

I was using a task card numbering convention, eventually arriving on WBS format with a little tweak that seems to work for my project. Layered with concurrent Worktree batches for concurrency, and Expand/Contract/Fowler kind of process if e.g. refactoring.

Right now at this minute, I'm implementing the Incoherence skill to my repo, that should sort out at least some of my recent issues.

Just wanted to say thanks for putting this up on Github.