Alternatives
Products that do what Replacing spec-driven development with just facts does
I had a lot of issues with spec-driven approaches, agents are too readily producing fluff, large projects have so many specs agents start making mistakes maintaining them. There's a constant consistency tax. In the end every spec is just a bunch of facts, so I decided to leave that and throw away everything else while making it friendlier for agentic use. Introducing facts - skills and CLI for agents to use facts-driven development. https://github.com/av/facts
- 1
- 2
Deep Work Plan▲114Models matter. Context matters more. Give your agent a plan.
Jun 2026 · deepworkplan.com
- 3SD
Spec Driven Development approach allows to squeeze more from coding agents thanks to few strong concepts: - decomposition across two dimensions. first you generate specs in multiple steps (requirements, code analysis, design), than you split task into multiple subtasks and implement them one by one - you clear context between every step - after spec generation and after subtask implementation. this helps keep cost low and context clear and focused which boost performance - specs written to disk help with information persistency - delivering specs layer by layer help to catch early when agent…
May 2026
- 4GS
I've worked on several projects writing and implementing specifications (particularly CLN): I've found the specs I write are much better when I quote them in the implementation, so I can see what implementers need to know. Also, when specs change in development, it's almost trivial to find where to update the code. This project is a formalization of my various hacky scripts which ensure the requirements are accurately quoted, and give coverage if any are missing. Not a major Opus, but I hope someone else finds it useful!
Jul 2026 · greatspectations.org
- 5AP
I'm Guy, the founder behind Snyk — now building Tessl, a package manager for agent skills. We’ve recently witnessed that most teams still treat skills as static artifacts: markdown files, created or copied from repo to repo. This approach offers a strong initial boost, but quickly creates debt: - Skills are duplicated, and updates never roll out. - Poor quality skills go unseen, misguiding agents instead of helping. - Skill knowledge grows stale, and don’t keep up with the systems and practices they describe. Without a way to evaluate skills, teams have no clear way to understand how good a…
Feb 2026 · tessl.io
- 6IM
At my work they provided a single Claude subscription for everyone on the team. To be honest I like kiro better as it provides a way better SDD management. But the company can't provide it and I can't afford it yet. Turns out I had the skill creator skill in my claude instance so I made use of it to create this Skill. I made it fully by using Claude but I wanted to make it open source, so I asked it to help me make tests and preparations for it, even a CI to run python tests. Well, we got this results with it: - Phase 2A: 67 static assertions (Python script, runs in CI) - Phase 2B: 15…
May 2026 · github.com
- 7CF
Hi HN, I built my first project using an LLM in mid-2024. I've been excited ever since. But of course, at some point it all turns into a mess. You see, software is an intricate interwoven collection of tiny details. Good software gets many details right; and does not regress as it gains functionality. My bootstrapped startup, ApprovIQ (https://approviq.com) is trying to break into a mature market with multiple fully featured competitors. I need to get the details right: MVP quality won't sell. So I opted for Test-Driven Development, the classic red/green/refactor. Writing…
Feb 2026 · codeleash.dev
- 8IB
TLDR; I built a tool that turns any API into a CLI designed for ai agents --- Got tired of dealing with bloated context windows from MCP servers and skills that stuff entire API docs into the agent's context CLIs fix this, agents run a single command to self-discover everything an API has to offer So, built a tool to generate them for any api. All CLIs are written in Go, fast and lightweight, no dependencies Help text (via the --help flag) is the killer feature: all context for each command/endpoint/parameter is extracted directly from the user-facing API docs and enhanced with…
Mar 2026 · instantcli.com
- 9FA
Hey HN, we built an Econ+Finance database to let AI agents do investment research. We spend a lot of tokens to organize macro releases and SEC filings into a clean format, so that your agents have more context to do actual analysis. The problem AI agents are great at data analysis. But they become ineffective if most of their context window is spent on gathering and cleaning data, instead of validating hypotheses. Data in the wild is messy and rarely standardized. Definitions and measurements change over time. This problem is compounded by a fragmented data universe. Point solutions exist…
Jul 2026 · github.com
- 10OD
The Problem "Vibing" with LLMs is often too shallow for complex logic, while writing full specifications is cognitively expensive and slow. We need a middle ground that mimics how human programmers gather context—scanning structure before diving into details. The Solution: Outline Driven Development (ODD) I've built a "batteries-included" kit for Gemini/Claude/Codex that uses AST analysis to understand code structure rather than just raw text. This relies on a hyper-optimized Rust toolchain (`ast-grep`, `ripgrep`, `jj`, etc.) to feed precise, structural context to the agent. 1. The…
Nov 2025 · github.com
- 11
- 12
Research-grounded, harness-agnostic skills for AI coding agents - SteveVitali/agent-skills
Aug 2026 · github.com
- 13RA
Hi HN folks, I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory. This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future? I do not think so. Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs…
Mar 2026 · github.com
- 14IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 15GT
Hi folks, I built this guide after watching AI agent prototypes repeatedly fail in production. It demonstrates transforming a monolithic marketplace assistant into a resilient multi-agent system using orra, an open-source platform I also built for production-ready multi-agent applications. The patterns shown are valuable *even if you're building your own orchestration layer*. Each stage builds on the previous one, showing the evolution from fragile prototype to resilient system. What makes this guide valuable: * Architectural transformation with working code examples - split monolithic…
2025 · github.com
- 16NH
Hey HN! When I started looking into LLMs and agents for software development and introducing them at work, I quickly realised that a person new to the topic faces a real barrage: - all the hype (AGI, engineers getting replaced by AI etc.) - conflicting opinions in virtually every discussion—for every person saying they’ve 10x-ed their productivity, there is a comment decrying LLMs as an utter failure - a lot of jargon (MoE, MCP, RAG, distillation, quantisation etc. etc.) - a profusion of models, IDEs/IDE extensions, CLI agents, other tools etc. Sorting through all of this can be quite…
2025 · nohypeai.dev
- 17
Agents start blind every session. dizz gives them a memory.
Aug 2026 · github.com
- 18DC
Hi HN I recently published docs-cli to pypi. I created this tool because I noticed that my docs kept getting out of sync: I've been using markdown to track the project's implementation and progress, and it became really hard to keep track of everything. This is a simple tool for your agents to ensure that links and indexes are kept fresh. I included the agent-playbook-suite marketplace since this is how I use it. The docs repo was actually built also using it, so dogfooding since day one :) The Agent Playbook Suite includes everything needed to create a project from start to finish. Linked…
May 2026 · artrichards.github.io
- 19
- 20AE
I’ve spent the past 10 years working on AI in finance, with much of that time focused on building evaluation systems for production environments. As agents become more widely adopted, more software engineering and product people have start building them. But I’ve noticed that many teams are not yet fluent in systematic evaluation, or in the processes needed to keep agent quality high over time. For large organizations, that gap is rarely the bottleneck due to dedicated teams. But after speaking with a number of startups, it became clear that building strong, up-to-date evals is much harder…
May 2026 · github.com
- 21TI
I'm an "ideas person" who messes around with AI on a low budget. I got tired of watching my tokens vanish and context windows filling up while agents fumbled around trying to find the right thing. Agents don't flail like they used to with shell tools, but there are still weak/blind spots and back-and-forth episodes — especially when using tools in combination/sequence. So I built "tilth" today. Or rather, AI built it — every line is Opus 4.6. I spent a lot of my precious tokens getting it to "not shit" (at least several of the different vendors' AI overlords assure me it's not…
Feb 2026 · github.com
- 22AA
I'm a VP of Engineering with 20 years in the field. I've been thinking deeply on why AI is breaking every engineering practice, and it led me to the conclusion that the Agile Manifesto's values need updating. The core argument: AI made producing software cheap, but understanding it is still expensive. The Manifesto optimizes for the former. This addendum shifts the emphasis toward the latter. Four updated values, three refined principles, with reasoning for each. Happy to discuss and defend any of it.
Mar 2026 · github.com
- 23RM
recursive-mode is an installable skill package for coding agents. It gives your agent a file-backed workflow for requirements, planning, implementation, testing, review, closeout, and memory, instead of leaving the whole process scattered in context. Long-running agent work has a common failure mode: requirements, decisions, and plans live in the conversation. Once the session ends or the context window overflows, the agent loses track of what was decided, what was implemented, and why. recursive-mode solves context rot by making repository documents the source of truth for every phase.…
Apr 2026 · recursive-mode.dev
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →