Specdd – Spec-driven development as a Claude/Codex/Cursor skill
Another spec framework competing with GitHub's spec-kit but as a skill file.
High-reasoning Claude Code orchestration skill with guarded PLAN-BUILD-JUDGE contracts and optional Cursor headless acceleration
Splitting thinking and typing by having Claude plan and judge while Cursor 'types' is a neat, pragmatic trade-off — you keep expensive reasoning where it matters and push bulk work to cheap, fast agents. The repo actually enforces safety: destructive command gates, scoped file access, install and preflight scripts, and a PLAN→BUILD→JUDGE contract rather than a toy demo. The downside is obvious: it's niche (requires Claude + Cursor CLIs and accounts) and adds orchestration complexity compared with single-model flows.
Developers who use AI-assisted coding (solo devs, engineering teams) looking to reduce model costs and add structured orchestration and safety
The idea: Claude acts as orchestrator: it plans tasks, breaks them into bounded units, and judges the output. Cursor agents (basic plan, almost unlimited and super fast) handle the actual code generation, which doesn't need frontier-level reasoning.
A guarded loop (PLAN -> BUILD -> JUDGE) enforces safety constraints between steps (no destructive ops, scoped file access, bounded iterations).
In practice, this brings my AI-assisted coding cost to ~$40/month while keeping the quality of having a strong model in the loop for architecture and review decisions.
The core tradeoff: you give up the simplicity of one model doing everything, but you gain cost control and a natural separation between "thinking" and "typing."
Repo: https://github.com/clementrog/claude-relais
Would love feedback on the orchestration approach, especially if others have tried similar multi-model setups and hit failure modes I haven't seen yet.
Another spec framework competing with GitHub's spec-kit but as a skill file.
Claude Code on autopilot with worktree isolation and rate-limit-aware scheduling.
Crontab scheduler documentation for Cursor /loop—no actual product, just a prompt.
Independent critic agent with no access to builder's reasoning catches blind spots.
Runs the agent locally and pushes live streams to a browser tab or your phone using WebSockets + the Web Push API, so approvals no longer block when you step away from the terminal. The PIN-based web auth, per-worktree session model, and direct use of Anthropic's Agent SDK are pragmatic choices that keep everything on-device while solving a very specific, annoying UX gap.
Durable memory outside model sessions beats Cursor's context loss between runs.