Metadata-Version: 2.4
Name: gsd-lean
Version: 0.2.1
Summary: Lightweight meta-prompting and spec-driven development plugin for Claude Code
Project-URL: Homepage, https://github.com/Bifurcate-Loops/gsd-lean
Project-URL: Repository, https://github.com/Bifurcate-Loops/gsd-lean
Project-URL: Issues, https://github.com/Bifurcate-Loops/gsd-lean/issues
Project-URL: Changelog, https://github.com/Bifurcate-Loops/gsd-lean/blob/main/CHANGELOG.md
Author: Bifurcate-Loops
License-Expression: MIT
License-File: LICENSE
Keywords: claude-code,development,meta-prompting,plugin,spec-driven
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Requires-Python: <3.15,>=3.12
Requires-Dist: click>=8.3.1
Requires-Dist: pyyaml>=6.0
Description-Content-Type: text/markdown

# GSD-Lean

> A lightweight Python plugin/add-on for [Get-Shit-Done](https://github.com/glittercowboy/get-shit-done)

## What is GSD?

[GSD](https://github.com/glittercowboy/get-shit-done) is a meta-prompting, context engineering, and spec-driven development system for Claude Code. It solves context rot by breaking projects into phases with fresh contexts per task, using a discuss → plan → execute → verify loop. Written in JavaScript.

## What is GSD-Lean?

A Python reimplementation of GSD's core ideas as a lightweight plugin. Rather than the full system, GSD-Lean focuses on being minimal and easy to extend.

**Status:** Early development — not yet functional.

## How It Works

GSD-Lean guides development through a 5-phase workflow:

```mermaid
stateDiagram-v2
    [*] --> discuss : gsd-lean init

    discuss --> plan : requirements populated
    plan --> discuss : plan rejected
    plan --> execute : plan verified
    execute --> verify
    verify --> execute : tasks remaining
    verify --> complete : all tasks done
    complete --> discuss : new cycle
```

| Phase | What Happens |
|-------|-------------|
| **discuss** | Research subagent investigates codebase + web; user preferences probed; REQUIREMENTS.md and DECISIONS.md populated |
| **plan** | Requirements decomposed into tasks (T-NNN) in PLAN.md; plan-review subagent verifies completeness |
| **execute** | Tasks implemented one by one, status tracked in PLAN.md |
| **verify** | Lint, typecheck, tests run against task verification criteria |
| **complete** | Summary generated, cycle can restart |

Each phase is driven by a skill (`/discuss`, `/plan`, `/execute`, `/verify`, `/complete`) that calls CLI commands (`gsd-lean transition`, `gsd-lean plan-status`) to manage state.

See [PROJECT_KNOWLEDGE.md](./PROJECT_KNOWLEDGE.md) for detailed architecture — transitions, preconditions, subagents, and CLI reference.
