看到一个有趣的工具 issu, 思路是用 CLI 和 markdown 文件作为项目的 issue tracker, 比单纯的 TODO 文件更适合一人维护项目，也很方便 agent 操控。不过这个软件是付费的，说实话我并不排斥付费，但这让我开始思考一个问题，在创造软件的成本被 AI 大幅削减的今天，纯本地付费软件的价值是否在变得越来越弱？以及如果一个人仅根据付费软件的 文档就让 AI clone 了一个功能完全一样的版本出来，是否算是一种知识产权的侵犯？

为了做这个实验我给了 claude code 两段提示词让它来 clone 一个完全一致的版本出来:

fetch all the content of https://issu.dev/ and each page of https://issu.dev/docs/ , save them to refs/ dir

then read and understand all the feature of issu, the cli issue manager, to create its clone, issuka

requirements:
- use plan with files skill, plan first then execute
- create complete test suites according to the features described in refs/
- stop unless all features are completed and all test suites are completed
- use python and uv to develop, load python related skills to write code
- be smart, make decisions yourself

做完之后的对齐:

since our project issuka is a clone of issu, i want to you to test against it side by side with actual issu's behavior, our goal:
1. ensure all commands and options issu has we, and the behaviors are the same
2. ensure issue files manipulated by issu are the same as we do, like creating, updating, setting status, all have the same effect

i have created ../issu-example folder, with issu executable in it, you should test running issu there, and compare the issues it creates with the ones issuka created here in our project

write a special test suites to prepare clean dirs and run both commands and check if the results are the same 

use planning with files to plan and execute

Issu

Issu | Track Tasks and Issues in Your Code Repos

Issu is the easiest way to manage issues from within your code repositories. Create, label, and organize your issues in whatever way makes you the most productive. Issu makes it easy to maintain context within your repositories.