104 karma · joined March 1, 2021
Example — MIT:
> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions
https://github.com/jbonatakis/differ
It helps when there’s a massive AI PR and it’s intimidating…seeing that it’s 70% tests, docs, and generated files can make it a bit more approachable. I’ve been integrating it into my CI pipelines so I get that breakdown as a comment on the PR
It breaks a spec (or freeform input) down into a structured json plan, then kicks off a new non-interactive session of Claude or codex for each task. Sounds like it could fit your workflow pretty well.
Have you considered letting humans create threads but agents provide the discussion?
https://github.com/jbonatakis/blackbird
At a high level it's my take on how the execution aspect of spec-driven development should be handled. Where as most tools that are popular right now break a spec down into a task list and instruct your agent to work through it in a single session, I am treating agents as stateless. By this I mean a separate (headless) session is started with selected context for each task. This avoids context exhaustion, compaction (and the resulting confusion that can occur), and means that Blackbird can work through effectively an arbitrarily large task list.
Right now it's BYO-spec, but then it:
* breaks the spec down into a dependent-aware plan (DAG) composed of parent and child tasks
* executes tasks one at a time based on their status (ready to execute if all dependencies are marked as completed)
* allows you to (optionally) pause execution after each task to review, approve and continue, approve and quit, or reject the changes altogether
* (soon) treats parent tasks as an automated reviewer for all child tasks and optionally auto-resume those sessions to address the feedback
* and more
It's entirely bootstrapped, and so far I'm quite pleased with it. I also wrote a post[1] today about some of the concepts I had in mind as I was defining the architecture.
What are you building?
As an experiment/exercise this is cool, but having a 100k loc codebase to maintain in a language I’ve never used sounds like a nightmare scenario.