plan_driven 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 49e95b18ac3191d34d9d526ba2fea2428ea662fab966da32c15239ba39573e5d
+  data.tar.gz: '099d0a1fae1854e186a894e95354118b086722ecb6b13c72e90e28dfa2a2bc13'
+SHA512:
+  metadata.gz: 2bd6c949e802f2f2e7ccc1b98052ebc3c744b5e4bb381666cddbe79f7849e7ff1cf4205bde8a8f00b560bbce70f85ebac584c2ddd76f12156a8adf3f06843520
+  data.tar.gz: c6605b055a96b9f2779038c2915ae2bf2585dfa28b66cd289a6b9a2dcbf295ed1ebda16d2df4476ea0d71b6dfd26ea05e9da39b596c905bbe18aeda6c6aa98a8

data/CHANGELOG.md

@@ -0,0 +1,76 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project adheres to
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-09-30
+
+First public release.
+
+### Plans
+
+- `plan-driven new` interviews the team in the terminal (what, why, where, who, when,
+  background, out of scope) and drafts the rest of the plan from the answers and the
+  application's schema, following the usual Confluence implementation plan template.
+- `edit` in `$EDITOR`, `redraft` with an instruction, `check`, `submit`, `approve` and
+  `reject`. Approvals belong to a revision, so editing an approved plan asks for approval again.
+- Plans are written to `docs/plans/<plan>/plan.{md,html,pdf}`, with the PDF rendered by
+  headless Chrome or any configured renderer.
+
+### Tickets
+
+- `tickets` splits an approved plan into tickets with a type, kind, description, acceptance
+  criteria, estimate, dependencies and the tables they touch. `tickets PLAN "instruction"`
+  redrafts the whole set.
+- `approve-tickets` approves them and creates a GitHub issue for each. Issue numbers and
+  names in ticket text (`#1`, `@event`) don't turn into links or mentions.
+
+### Development
+
+- `develop` starts one Cursor cloud agent per ready ticket, within `max_parallel_agents`. A
+  ticket is ready once every ticket it depends on is merged.
+- `status` follows agents to their pull requests, notices pull requests merged on GitHub, and
+  suggests the next step.
+- `review` lists every check it ran, not only the failures. `approve-pr`, `feedback` (a
+  follow-up to the same agent) and `merge`, which needs the ticket key typed, waits for CI and
+  marks an agent's draft pull request ready before merging.
+
+### Guards
+
+- PlanGuard: required sections, minimum length, a security risk level, placeholders, and an
+  Existing Data Structure section that cites only models, files and columns that exist.
+- MigrationGuard: one-step removals and renames, NOT NULL without a default or backfill, and
+  non-concurrent indexes on PostgreSQL.
+- TicketNormalizer: keys, kinds, types, title prefixes and estimates corrected in code, and
+  every correction reported.
+- TicketGuard: acceptance criteria, estimates, dependency cycles, expand and contract order
+  per table, and coverage of the plan's tables.
+- PrGuard: size, specs, migrations only in migration tickets, a Cucumber scenario for every
+  acceptance criterion, CI results, and a warning when the branch is behind the base branch.
+- Guard errors go back to the model as a list to fix, up to `max_repair_attempts` times.
+
+### Evidence
+
+- `evidence` runs the plan's Cucumber scenarios, or imports a JSON run with `--from`, and maps
+  each acceptance criterion to the scenarios tagged for it.
+- `report` writes the delivery report: tickets and pull requests, the acceptance criteria
+  proof matrix, guard findings, approvals and the timeline.
+- `log` prints the append-only audit trail.
+
+### Setup
+
+- A `plan_driven:install` generator for the tables, the initializer and `docs/plans`.
+- OpenAI and Anthropic over `net/http`, any OpenAI-compatible endpoint through `llm_api_base`.
+- `llm_provider :cursor` drafts plans and tickets with a model on the user's Cursor account
+  (Claude Opus 5.5 by default) through the Cursor SDK. The agent reads the application's code
+  with read-only tools.
+- Keys from the environment, then `~/.plan_driven/config` (mode 0600), written by
+  `plan-driven configure`; the GitHub token can also come from `gh auth token`.
+- `plan-driven doctor` checks keys, the repository, the PDF browser, the Cursor API, the agent
+  model, and Node and the SDK for `:cursor`.
+
+[Unreleased]: https://github.com/blaz1988/plan-driven/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/blaz1988/plan-driven/releases/tag/v0.1.0

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Ivan Blazevic, Rubycode (https://rubycode.co)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.