Skip to content

Commit 0fe4dfa

Browse files
authored
Merge pull request #6 from Obsidian-Owl/fix/blog-post-broken-links
Fix broken links in Specwright blog post
2 parents 60646bf + e34fff4 commit 0fe4dfa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2026-02-16-specwright-spec-driven-development-that-closes-the-loop.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ I've written about this before. My early experiments with AI-assisted developmen
1717

1818
## What I Tried First
1919

20-
I went through the usual progression. I tried [Spec Kit](https://github.com/spec-kit/spec-kit) and genuinely liked the structured approach—spec-first development is the right idea. But it focused heavily on the planning side and didn't have the verification muscle I needed. Specs would get written beautifully, then the implementation would drift, and nothing would catch it until a human reviewed the PR.
20+
I went through the usual progression. I tried [Spec Kit](https://github.com/github/spec-kit) and genuinely liked the structured approach—spec-first development is the right idea. But it focused heavily on the planning side and didn't have the verification muscle I needed. Specs would get written beautifully, then the implementation would drift, and nothing would catch it until a human reviewed the PR.
2121

22-
I experimented with [Oh-My-ClaudeCode](https://github.com/anthropics/oh-my-claudecode) and appreciated the configurability. But it felt a bit too hands-off for my taste. I generally prefer a model where I'm heavily involved at key points in the cycle—design decisions and verification—rather than delegating the whole thing end-to-end.
22+
I experimented with [Oh-My-ClaudeCode](https://github.com/Yeachan-Heo/oh-my-claudecode) and appreciated the configurability. But it felt a bit too hands-off for my taste. I generally prefer a model where I'm heavily involved at key points in the cycle—design decisions and verification—rather than delegating the whole thing end-to-end.
2323

2424
None of the tools I found really focused on the git ops and quality controls I wanted. So I ended up accumulating skills, rules, and constitution files scattered across projects. Every project had its own flavour. Nothing was consistent, nothing got updated systematically, and the lessons from one project never made it to the next.
2525

0 commit comments

Comments
 (0)