v0.3

Everything approved now sits in the solution folder's spec/ folder, and the solution has a name of its own. The spec names its items with references, paths that walk spec/ such as requirements.remind.at-most-weekly, and another repo points at the same items by putting the solution's name and a colon in front. Specs written against v0.2 stay pinned to v0.2 until they're revised.

solution-planner.zip and solution-planner.skill are the same zip, with the solution-planner folder inside. Use whichever your agent takes.

v0.2

Plans now go through a draft before approval, and stay with the planner afterwards. Later work that finds a problem reports it in findings/ and stops, and the planner revises the plan, which includes bringing a spec up to a newer format. Specs written against v0.1 stay pinned to v0.1 until they're revised.

solution-planner.zip and solution-planner.skill are the same zip, with the solution-planner folder inside. Use whichever your agent takes.

v0.1

First version, and an experiment. The format may change between versions, and specs stay pinned to the version they link to.

solution-planner.zip and solution-planner.skill are the same zip, with the solution-planner folder inside. Use whichever your agent takes.