atdd 0.3.3__tar.gz → 0.4.7__tar.gz

{atdd-0.3.3/src/atdd.egg-info → atdd-0.4.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atdd
-Version: 0.3.3
+Version: 0.4.7
 Summary: ATDD Platform - Acceptance Test Driven Development toolkit
 License: MIT
 Requires-Python: >=3.10
@@ -16,6 +16,15 @@ Dynamic: license-file
 
 Acceptance Test Driven Development toolkit for structured planning and convention enforcement.
 
+ATDD covers the full software lifecycle, not just code. It starts from a job to be done (e.g., user problem or goal), turns it into deterministic requirements, validates them with tests, and then drives implementation.
+
+```mermaid
+flowchart LR
+    A[Job to be Done] -->|Planner| B[Wagon + Acceptance Criteria]
+    B -->|Tester| C[RED Tests]
+    C -->|Coder| D[GREEN Code]
+```
+
 ## Installation
 
 ### From PyPI
@@ -49,14 +58,20 @@ atdd --help
 ```bash
 atdd init                      # Initialize ATDD in your project
 atdd gate                      # ⚠️ START EVERY SESSION WITH THIS
-atdd session new my-feature    # Create a planning session
+atdd session new <task>        # Create a planning session
 atdd sync                      # Sync rules to agent config files
-atdd --test all                # Run validators
+atdd validate                  # Run all validators
 ```
 
 > **⚠️ `atdd gate` is required.** 
 > 🤖 Tell your agent: "Run `atdd gate` and follow ATDD rigorously." 
-> Agents skip instruction files but can't ignore tool output. No gate = no ATDD guarantees.
+> Agents skip instruction files but can't ignore tool ou
+
+
+
+
+
+tput. No gate = no ATDD guarantees.
 
 ## What It Does
 
@@ -67,6 +82,22 @@ ATDD provides:
 3. **ATDD Lifecycle** - Planner → Tester → Coder phase gates
 4. **Agent Config Sync** - Keep ATDD rules in sync across AI agent config files
 
+```mermaid
+flowchart LR
+    A[Job to be Done] -->|Planner| B[Wagon + Acceptance Criteria]
+    B -->|Tester| C[RED Tests]
+    C -->|Coder| D[GREEN Code]
+    D -->|Coder| E[REFACTOR]
+    E -.->|feedback| B
+
+    subgraph "ATDD Lifecycle"
+        B
+        C
+        D
+        E
+    end
+```
+
 ## Commands
 
 ### Project Initialization
@@ -196,19 +227,39 @@ Before starting work, confirm you have loaded these rules.
 ### Validation
 
 ```bash
-atdd --test all        # Run all validators
-atdd --test planner    # Planning artifacts only
-atdd --test tester     # Testing artifacts only
-atdd --test coder      # Implementation only
-atdd --quick           # Fast smoke test
+atdd validate              # Run all validators
+atdd validate planner      # Planning validators only
+atdd validate tester       # Testing validators only
+atdd validate coder        # Implementation validators only
+atdd validate --quick      # Fast smoke test
+atdd validate --coverage   # With coverage report
+atdd validate --html       # With HTML report
+```
+
+### Release Versioning
+
+ATDD enforces release versioning via coach validators. Recommended: keep a single root `VERSION` file as the canonical source (first line like `1.2.3 - short summary`; trailing summary is ignored). Configure the version file and tag prefix in `.atdd/config.yaml`:
+
+```yaml
+release:
+  version_file: "VERSION"  # recommended single source of truth
+  tag_prefix: "v"
 ```
 
+If you also publish with language-specific manifests (e.g., `pyproject.toml`, `package.json`), keep their version fields in sync with `VERSION`.
+
+Validation (`atdd validate coach` or `atdd validate`) requires:
+- Version file exists and contains a version
+- Git tag on HEAD matches `{tag_prefix}{version}`
+
 ### Other Commands
 
 ```bash
-atdd --status          # Platform status
-atdd --inventory       # Generate artifact inventory
-atdd --help            # Full help
+atdd status                    # Platform status
+atdd inventory                 # Generate artifact inventory
+atdd inventory --format json   # Inventory as JSON
+atdd registry update           # Update all registries
+atdd --help                    # Full help
 ```
 
 ## Project Structure
@@ -264,7 +315,7 @@ pytest --cov=atdd --cov-report=html
 
 1. Create `src/atdd/{phase}/validators/test_{name}.py`
 2. Write pytest test functions
-3. Run `atdd --test {phase}`
+3. Run `atdd validate {phase}`
 
 Validators are auto-discovered by pytest.
 

{atdd-0.3.3 → atdd-0.4.7}/README.md

@@ -2,6 +2,15 @@
 
 Acceptance Test Driven Development toolkit for structured planning and convention enforcement.
 
+ATDD covers the full software lifecycle, not just code. It starts from a job to be done (e.g., user problem or goal), turns it into deterministic requirements, validates them with tests, and then drives implementation.
+
+```mermaid
+flowchart LR
+    A[Job to be Done] -->|Planner| B[Wagon + Acceptance Criteria]
+    B -->|Tester| C[RED Tests]
+    C -->|Coder| D[GREEN Code]
+```
+
 ## Installation
 
 ### From PyPI
@@ -35,14 +44,20 @@ atdd --help
 ```bash
 atdd init                      # Initialize ATDD in your project
 atdd gate                      # ⚠️ START EVERY SESSION WITH THIS
-atdd session new my-feature    # Create a planning session
+atdd session new <task>        # Create a planning session
 atdd sync                      # Sync rules to agent config files
-atdd --test all                # Run validators
+atdd validate                  # Run all validators
 ```
 
 > **⚠️ `atdd gate` is required.** 
 > 🤖 Tell your agent: "Run `atdd gate` and follow ATDD rigorously." 
-> Agents skip instruction files but can't ignore tool output. No gate = no ATDD guarantees.
+> Agents skip instruction files but can't ignore tool ou
+
+
+
+
+
+tput. No gate = no ATDD guarantees.
 
 ## What It Does
 
@@ -53,6 +68,22 @@ ATDD provides:
 3. **ATDD Lifecycle** - Planner → Tester → Coder phase gates
 4. **Agent Config Sync** - Keep ATDD rules in sync across AI agent config files
 
+```mermaid
+flowchart LR
+    A[Job to be Done] -->|Planner| B[Wagon + Acceptance Criteria]
+    B -->|Tester| C[RED Tests]
+    C -->|Coder| D[GREEN Code]
+    D -->|Coder| E[REFACTOR]
+    E -.->|feedback| B
+
+    subgraph "ATDD Lifecycle"
+        B
+        C
+        D
+        E
+    end
+```
+
 ## Commands
 
 ### Project Initialization
@@ -182,19 +213,39 @@ Before starting work, confirm you have loaded these rules.
 ### Validation
 
 ```bash
-atdd --test all        # Run all validators
-atdd --test planner    # Planning artifacts only
-atdd --test tester     # Testing artifacts only
-atdd --test coder      # Implementation only
-atdd --quick           # Fast smoke test
+atdd validate              # Run all validators
+atdd validate planner      # Planning validators only
+atdd validate tester       # Testing validators only
+atdd validate coder        # Implementation validators only
+atdd validate --quick      # Fast smoke test
+atdd validate --coverage   # With coverage report
+atdd validate --html       # With HTML report
+```
+
+### Release Versioning
+
+ATDD enforces release versioning via coach validators. Recommended: keep a single root `VERSION` file as the canonical source (first line like `1.2.3 - short summary`; trailing summary is ignored). Configure the version file and tag prefix in `.atdd/config.yaml`:
+
+```yaml
+release:
+  version_file: "VERSION"  # recommended single source of truth
+  tag_prefix: "v"
 ```
 
+If you also publish with language-specific manifests (e.g., `pyproject.toml`, `package.json`), keep their version fields in sync with `VERSION`.
+
+Validation (`atdd validate coach` or `atdd validate`) requires:
+- Version file exists and contains a version
+- Git tag on HEAD matches `{tag_prefix}{version}`
+
 ### Other Commands
 
 ```bash
-atdd --status          # Platform status
-atdd --inventory       # Generate artifact inventory
-atdd --help            # Full help
+atdd status                    # Platform status
+atdd inventory                 # Generate artifact inventory
+atdd inventory --format json   # Inventory as JSON
+atdd registry update           # Update all registries
+atdd --help                    # Full help
 ```
 
 ## Project Structure
@@ -250,7 +301,7 @@ pytest --cov=atdd --cov-report=html
 
 1. Create `src/atdd/{phase}/validators/test_{name}.py`
 2. Write pytest test functions
-3. Run `atdd --test {phase}`
+3. Run `atdd validate {phase}`
 
 Validators are auto-discovered by pytest.
 

{atdd-0.3.3 → atdd-0.4.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "atdd"
-version = "0.3.3"
+version = "0.4.7"
 description = "ATDD Platform - Acceptance Test Driven Development toolkit"
 requires-python = ">=3.10"
 readme = "README.md"