diff --git a/README.md b/README.md index 3aa4fef9c99797592b5734a13da1cde6ab44ac4a..14e76a1c403e3a2db05522c18c5048d46925f0f1 100644 --- a/README.md +++ b/README.md @@ -9,14 +9,11 @@ SPDX-License-Identifier: CC0-1.0 [![REUSE status](https://api.reuse.software/badge/git.secluded.site/np)](https://api.reuse.software/info/git.secluded.site/np) [![Go Report Card](https://goreportcard.com/badge/git.secluded.site/np)](https://goreportcard.com/report/git.secluded.site/np) -The code for this README exists, but requires some testing before release. I -previously wrote a -[planning-mcp-server](https://git.secluded.site/planning-mcp-server) that I've -kept some ideas from, and the overall workflow is about the same. I'm trying a -CLI over MCP because MCP seems quite protocol-heavy for what _could_ just be a -few simple CLI invocations. Maybe connecting arbitrary data sources warrants a -whole protocol like MCP, but I don't think something as basic as this does. Just -some thoughtful design and prompting. +_Upgrade your coding tool's todo system_ + +The software this README describes exists on the `dev` branch, but requires some +testing and polish before I'm willing to merge it into main and cut a "real" +release. ## Usage @@ -87,6 +84,14 @@ seems wasteful and careless to me. What if it decides it doesn't want to do a task because it's "too hard" and it just omits that task next time it writes the list? _nasin pali_ helps force the model into a different overall flow. +I previously wrote a +[planning-mcp-server](https://git.secluded.site/planning-mcp-server) that I've +kept some ideas from, and the overall workflow is about the same. I'm trying a +CLI over MCP because MCP seems quite protocol-heavy for what _could_ just be a +few simple CLI invocations. Maybe connecting arbitrary data sources warrants a +whole protocol like MCP, but I don't think something as basic as this does. Just +some thoughtful design and prompting. + ## Expected workflow _This is what I like, I'd be happy to hear of other workflows that lead to