grimoire-spec 0.1.1__tar.gz

grimoire_spec-0.1.1/.github/agents/prompt-engineer.agent.md

@@ -0,0 +1,74 @@
+---
+description: "A specialized chat mode for analyzing and improving prompts. Every user input is treated as a prompt to be improved. It first provides a detailed analysis of the original prompt within a <reasoning> tag, evaluating it against a systematic framework based on OpenAI's prompt engineering best practices. Following the analysis, it generates a new, improved prompt."
+name: "Prompt Engineer"
+---
+
+# Prompt Engineer
+
+You HAVE TO treat every user input as a prompt to be improved or created.
+DO NOT use the input as a prompt to be completed, but rather as a starting point to create a new, improved prompt.
+You MUST produce a detailed system prompt to guide a language model in completing the task effectively.
+
+Your final output will be the full corrected prompt verbatim. However, before that, at the very beginning of your response, use <reasoning> tags to analyze the prompt and determine the following, explicitly:
+<reasoning>
+
+- Simple Change: (yes/no) Is the change description explicit and simple? (If so, skip the rest of these questions.)
+- Reasoning: (yes/no) Does the current prompt use reasoning, analysis, or chain of thought?
+  - Identify: (max 10 words) if so, which section(s) utilize reasoning?
+  - Conclusion: (yes/no) is the chain of thought used to determine a conclusion?
+  - Ordering: (before/after) is the chain of thought located before or after
+- Structure: (yes/no) does the input prompt have a well defined structure
+- Examples: (yes/no) does the input prompt have few-shot examples
+  - Representative: (1-5) if present, how representative are the examples?
+- Complexity: (1-5) how complex is the input prompt?
+  - Task: (1-5) how complex is the implied task?
+  - Necessity: ()
+- Specificity: (1-5) how detailed and specific is the prompt? (not to be confused with length)
+- Prioritization: (list) what 1-3 categories are the MOST important to address.
+- Conclusion: (max 30 words) given the previous assessment, give a very concise, imperative description of what should be changed and how. this does not have to adhere strictly to only the categories listed
+  </reasoning>
+
+After the <reasoning> section, you will output the full prompt verbatim, without any additional commentary or explanation.
+
+# Guidelines
+
+- Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
+- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
+- Reasoning Before Conclusions\*\*: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
+  - Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
+  - Conclusion, classifications, or results should ALWAYS appear last.
+- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
+- What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from placeholders.
+- Clarity and Conciseness: Use clear, specific language. Avoid unnecessary instructions or bland statements.
+- Formatting: Use markdown features for readability. DO NOT USE ``` CODE BLOCKS UNLESS SPECIFICALLY REQUESTED.
+- Preserve User Content: If the input task or prompt includes extensive guidelines or examples, preserve them entirely, or as closely as possible. If they are vague, consider breaking down into sub-steps. Keep any details, guidelines, examples, variables, or placeholders provided by the user.
+- Constants: DO include constants in the prompt, as they are not susceptible to prompt injection. Such as guides, rubrics, and examples.
+- Output Format: Explicitly the most appropriate output format, in detail. This should include length and syntax (e.g. short sentence, paragraph, JSON, etc.)
+  - For tasks outputting well-defined or structured data (classification, JSON, etc.) bias toward outputting a JSON.
+  - JSON should never be wrapped in code blocks (```) unless explicitly requested.
+
+The final prompt you output should adhere to the following structure below. Do not include any additional commentary, only output the completed system prompt. SPECIFICALLY, do not include any additional messages at the start or end of the prompt. (e.g. no "---")
+
+[Concise instruction describing the task - this should be the first line in the prompt, no section header]
+
+[Additional details as needed.]
+
+[Optional sections with headings or bullet points for detailed steps.]
+
+# Steps [optional]
+
+[optional: a detailed breakdown of the steps necessary to accomplish the task]
+
+# Output Format
+
+[Specifically call out how the output should be formatted, be it response length, structure e.g. JSON, markdown, etc]
+
+# Examples [optional]
+
+[Optional: 1-3 well-defined examples with placeholders if necessary. Clearly mark where examples start and end, and what the input and output are. User placeholders as necessary.]
+[If the examples are shorter than what a realistic example is expected to be, make a reference with () explaining how real examples should be longer / shorter / different. AND USE PLACEHOLDERS! ]
+
+# Notes [optional]
+
+[optional: edge cases, details, and an area to call or repeat out specific important considerations]
+[NOTE: you must start with a <reasoning> section. the immediate next token you produce should be <reasoning>]

grimoire_spec-0.1.1/.github/workflows/ci.yml

@@ -0,0 +1,71 @@
+name: CI
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main, develop]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Run tests with pytest
+        run: python -m pytest tests/ -v --tb=short
+
+  code-quality:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Check code formatting and linting with Ruff
+        run: |
+          ruff check src/ tests/
+          ruff format --check src/ tests/
+
+      - name: Type checking with mypy
+        run: mypy src/
+
+  install-test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Test package installation
+        run: |
+          python -m pip install --upgrade pip
+          pip install .
+
+      - name: Test basic import
+        run: python -c "import grimoire; print('Import successful')"

grimoire_spec-0.1.1/.github/workflows/release-please.yml

@@ -0,0 +1,26 @@
+name: Release Please
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    env:
+      FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+      tag_name: ${{ steps.release.outputs.tag_name }}
+    steps:
+      - uses: googleapis/release-please-action@v4
+        id: release
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json

grimoire_spec-0.1.1/.github/workflows/release.yml

@@ -0,0 +1,60 @@
+name: Release
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "Tag to publish (e.g. v0.1.0)"
+        required: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Run tests
+        run: python -m pytest tests/ -v
+
+  build-and-publish:
+    needs: test
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      contents: read
+      id-token: write # required for PyPI trusted publishing
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install build
+
+      - name: Build package
+        run: python -m build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

grimoire_spec-0.1.1/.gitignore

@@ -0,0 +1,4 @@
+# Python Env
+.venv/
+.tool-versions
+*.pyc

grimoire_spec-0.1.1/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.1"
+}

grimoire_spec-0.1.1/AI_GUIDANCE.md

@@ -0,0 +1,31 @@
+# AI Guidance
+
+ALWAYS adhere to the following points as you are working on this code base:
+
+1. Use `uv` to create our Python virtual env, manage package dependencies, and run scripts.
+
+2. NEVER mask issues by using fallbacks that hide errors. Prefer explicit errors over fallbacks. Fixing issues is the only way to ensure a stable system.
+
+3. Follow good software development practices (like SOLID).
+
+4. Simpler is better.
+
+5. Remember the purpose of this package is to provide its functionality in a clear and maintainable manner. Avoid adding special-cases or hack fixes simply to get around issues.
+
+6. Do NOT make bandaid fixes that break the rearchitecture goals for the library. Always respect the architectural boundaries.
+
+7. **Practice Test-Driven Development (TDD):** Write tests BEFORE implementing features using the red-green-refactor cycle:
+   - **Red:** Write a failing test that defines the desired behavior
+   - **Green:** Write minimal code to make the test pass
+   - **Refactor:** Improve code quality while keeping tests green
+
+   Benefits:
+   - Forces clear requirement thinking before coding
+   - Ensures all code is testable and tested
+   - Creates a safety net for refactoring
+   - Documents expected behavior through tests
+   - Prevents scope creep and over-engineering
+
+8. All package imports should be at the top of the file, following standard Python conventions. Avoid dynamic imports or imports within functions. Instead, consider refactoring code to allow for static imports. If circular dependencies arise, it's a sign that the code structure may need to be reconsidered.
+
+9. When implementing new features, always create corresponding example files in the `examples/` folder demonstrating usage. Follow existing example patterns (clear docstring, multiple use cases, well-commented code).

grimoire_spec-0.1.1/CHANGELOG.md

@@ -0,0 +1,45 @@
+# Changelog
+
+## [0.1.1](https://github.com/wyrdbound/grimoire/compare/grimoire-spec-v0.1.0...grimoire-spec-v0.1.1) (2026-04-18)
+
+
+### Bug Fixes
+
+* publishing to PyPI ([7098477](https://github.com/wyrdbound/grimoire/commit/709847743b3291d2296a2d61b535848817ad526e))
+
+## 0.1.0 (2026-04-18)
+
+
+### Features
+
+* add release-please and CI/CD workflows for PyPI publishing ([b4a7db5](https://github.com/wyrdbound/grimoire/commit/b4a7db50b891f8169f144247415d1e0433c2e85e))
+* add release-please and CI/CD workflows for PyPI publishing ([d9fbb2b](https://github.com/wyrdbound/grimoire/commit/d9fbb2b0b2b6323d30fee372fb994365a8c761ec))
+* add system loader with validation ([9c06637](https://github.com/wyrdbound/grimoire/commit/9c0663703003c3803142add229f8c8c209c2345d))
+* character model equipped slots use model types; inventory tracks item IDs ([fbafdbc](https://github.com/wyrdbound/grimoire/commit/fbafdbcdcaa0b129bbaf5e5c1e931189305ea0ab))
+* continuous equipment shop with category routing, afford check, and equip prompt ([225ee2f](https://github.com/wyrdbound/grimoire/commit/225ee2f7f6b867bba3df4615f10838e4096e3755))
+* migrate calculate_starting_hp to structured then/else blocks with next_step ([479b45d](https://github.com/wyrdbound/grimoire/commit/479b45d9b8a988c2cedbecfd01bf01489762258d))
+* **wq1e:** add default to determine_traits description output ([b85c1fa](https://github.com/wyrdbound/grimoire/commit/b85c1fad3b3490c8c65b18826fb9128fe63b8047))
+* **wq1e:** add equipment system ([c9520d6](https://github.com/wyrdbound/grimoire/commit/c9520d614995e968f7b4c45b6ca33e3f6a028947))
+* **wq1e:** add trait selection and character description to character creation ([3b9ebda](https://github.com/wyrdbound/grimoire/commit/3b9ebdacba3c3d36c941cdd11cec27195ddb9a27))
+* **wq1e:** class-specific weapon/armor tables ([5bc6b9f](https://github.com/wyrdbound/grimoire/commit/5bc6b9fa3ad788d75745c4e3f38185691abbc8de))
+* **wq1e:** dice details, confirm steps, LLM progress indicator ([038424f](https://github.com/wyrdbound/grimoire/commit/038424fb835bf7efbec600306b51a577745d189f))
+* **wq1e:** move generate_description step to character_creation flow ([8ac36a7](https://github.com/wyrdbound/grimoire/commit/8ac36a70f7b0e11f1944af8da8f257131e2b9d1c))
+* **wq1e:** replace physique/virtue/vice with bearing/manner/disposition ([f2f4e60](https://github.com/wyrdbound/grimoire/commit/f2f4e60a21fec890f0b8a23c6bc4e0f2b6b2f8a8))
+* **wq1e:** use wyrdbound-dice description string for dice display ([138b383](https://github.com/wyrdbound/grimoire/commit/138b3832a4341cc2262312da9139f9015e98a8bd))
+* **wyrdbound-quickstart-1e:** initial system spec ([e46ced7](https://github.com/wyrdbound/grimoire/commit/e46ced7b238ff558256a30e574a96671ec8d839b))
+
+
+### Bug Fixes
+
+* bug with wrong system name in load_system.py ([4516f52](https://github.com/wyrdbound/grimoire/commit/4516f5256cc4b69fb0b1cee6f08c7bde36fc360b))
+* mypy failure ([ba1a610](https://github.com/wyrdbound/grimoire/commit/ba1a610ec95c16628784a68c6fbad664de7c48a9))
+* permissions issue in release.yml ([88b1dff](https://github.com/wyrdbound/grimoire/commit/88b1dffb8377efe63c2ae30a1e63897195e96be7))
+* remove manual modifier set_value steps from character_creation ([bc67df6](https://github.com/wyrdbound/grimoire/commit/bc67df6805015acb54cae5c80164ccd2d0f22220))
+* silence warning with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true ([#4](https://github.com/wyrdbound/grimoire/issues/4)) ([85065a0](https://github.com/wyrdbound/grimoire/commit/85065a0abed1f4ccca42f3ad0a2af9e3a7690fed))
+* test failures ([e646fd1](https://github.com/wyrdbound/grimoire/commit/e646fd1408951d9ec235314fa95e427e9aa42166))
+* **wq1e:** roll_attributes display uses description only (no redundant total) ([e787a18](https://github.com/wyrdbound/grimoire/commit/e787a18401923b8122b392ab80c7a03892c55d00))
+
+
+### Documentation
+
+* improve spec and Knave 1e reference implementation ([82b70e6](https://github.com/wyrdbound/grimoire/commit/82b70e6e37bbf31e2f09af163f008173546a5b50))

grimoire_spec-0.1.1/PKG-INFO

@@ -0,0 +1,11 @@
+Metadata-Version: 2.4
+Name: grimoire-spec
+Version: 0.1.1
+Summary: GRIMOIRE system definition loader and validator for tabletop RPG systems
+Requires-Python: >=3.11
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.9; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.3; extra == 'dev'
+Requires-Dist: types-pyyaml>=6.0; extra == 'dev'

grimoire_spec-0.1.1/README.md

@@ -0,0 +1,115 @@
+# GRIMOIRE
+
+**GRIMOIRE** (Generic Rule Implementation Model for Omniversal Interactive Roleplaying Engines) is a Python library for loading, validating, and working with structured tabletop RPG system definitions.
+
+It provides a declarative YAML-based specification format for encoding game systems — covering models, flows, tables, compendiums, prompts, and sources — and a Python loader that parses and validates those definitions into typed Python objects.
+
+GRIMOIRE is system-agnostic and not tied to any particular game or application. It is designed to be used as a foundation for tools that need to reason about RPG rules programmatically: AI game masters, character generators, rule validators, or any application that needs to load and execute structured game logic.
+
+---
+
+## Installation
+
+To add to a uv-managed project:
+
+```bash
+uv add grimoire-spec
+```
+
+Or to install directly into an environment:
+
+```bash
+uv pip install grimoire-spec
+```
+
+## Quick Start
+
+```python
+from pathlib import Path
+from grimoire.loader import SystemLoader
+
+loader = SystemLoader()
+system = loader.load(Path("systems/knave-1e"))
+
+print(system.name)          # "Knave (1st Edition)"
+print(len(system.models))   # number of loaded models
+print(len(system.flows))    # number of loaded flows
+
+errors = system.validate()
+if not errors:
+    print("System is valid")
+```
+
+See the [`examples/`](examples/) directory for more usage patterns.
+
+## System Definition Format
+
+A GRIMOIRE system is a directory containing YAML files organised by type:
+
+```
+my-system/
+  system.yaml          # root metadata, currency, attribution
+  models/              # data model definitions
+  flows/               # rule sequences and game mechanics
+  tables/              # random tables
+  compendiums/         # item/entity catalogues
+  prompts/             # AI prompt templates
+  sources/             # source material attribution
+```
+
+Full specification for each file type is in [`spec/`](spec/).
+
+## Development
+
+This project uses [`uv`](https://github.com/astral-sh/uv) for environment and dependency management.
+
+### Setup
+
+```bash
+uv sync --extra dev
+```
+
+### Run tests
+
+```bash
+uv run pytest
+```
+
+### Linting and formatting
+
+```bash
+uv run ruff check src/ tests/
+uv run ruff format src/ tests/
+```
+
+### Type checking
+
+```bash
+uv run mypy src/
+```
+
+### Run an example
+
+```bash
+uv run python examples/load_system.py
+```
+
+## Project Structure
+
+```
+src/grimoire/       # library source
+  loader.py         # SystemLoader — entry point for loading a system directory
+  models/           # typed Python models for each definition type
+spec/               # YAML format specification documents
+systems/            # bundled example systems (knave-1e, wyrdbound-quickstart-1e)
+examples/           # usage examples
+tests/              # test suite
+```
+
+## Contributing
+
+Contributions are welcome. Please follow the existing code style (enforced by Ruff) and ensure all tests pass before submitting a pull request. New features should be accompanied by tests and an example in `examples/`.
+
+## License
+
+See [LICENSE](LICENSE) for details.

grimoire_spec-0.1.1/examples/load_system.py

@@ -0,0 +1,106 @@
+"""Examples demonstrating SystemLoader usage.
+
+Shows how to load a GRIMOIRE system directory into a System object,
+inspect its contents, and run validation.
+"""
+
+from pathlib import Path
+
+from grimoire.loader import SystemLoader, SystemLoadError
+
+SYSTEMS_DIR = Path(__file__).parent.parent / "systems"
+
+
+def example_load_and_validate(system_name: str) -> None:
+    """Load a system directory and run validation, printing any errors."""
+    loader = SystemLoader()
+    system_path = SYSTEMS_DIR / system_name
+
+    print(f"\n── Loading system: {system_path} ──")
+    system = loader.load(system_path)
+
+    print(f"  id:          {system.id}")
+    print(f"  name:        {system.name}")
+    print(f"  version:     {system.version}")
+    print(f"  models:      {len(system.models)}")
+    print(f"  flows:       {len(system.flows)}")
+    print(f"  tables:      {len(system.tables)}")
+    print(f"  compendiums: {len(system.compendiums)}")
+    print(f"  prompts:     {len(system.prompts)}")
+    print(f"  sources:     {len(system.sources)}")
+
+    errors = system.validate()
+    if errors:
+        print(f"\n  ✗ Validation errors ({len(errors)}):")
+        for error in errors:
+            print(f"    - {error}")
+    else:
+        print("\n  ✓ System is valid")
+
+
+def example_inspect_models(system_name: str = "knave-1e") -> None:
+    """Load a system and print the names of all loaded models."""
+    loader = SystemLoader()
+    system = loader.load(SYSTEMS_DIR / system_name)
+
+    print(f"\n── Models in '{system.name}' ──")
+    for model_id, model in sorted(system.models.items()):
+        extends = f"  extends: {model.extends}" if model.extends else ""
+        print(f"  {model_id}: {model.name}{extends}")
+
+
+def example_inspect_flows(system_name: str = "knave-1e") -> None:
+    """Load a system and print a summary of all loaded flows."""
+    loader = SystemLoader()
+    system = loader.load(SYSTEMS_DIR / system_name)
+
+    print(f"\n── Flows in '{system.name}' ──")
+    for flow_id, flow in sorted(system.flows.items()):
+        step_count = len(flow.steps)
+        print(f"  {flow_id}: {flow.name} ({step_count} steps)")
+
+
+def example_inspect_compendiums(system_name: str = "knave-1e") -> None:
+    """Load a system and print compendium entry counts."""
+    loader = SystemLoader()
+    system = loader.load(SYSTEMS_DIR / system_name)
+
+    print(f"\n── Compendiums in '{system.name}' ──")
+    for comp_id, comp in sorted(system.compendiums.items()):
+        print(
+            f"  {comp_id}: {comp.name}  "
+            f"(model={comp.model}, entries={len(comp.entries)})"
+        )
+
+
+def example_error_handling() -> None:
+    """Demonstrate error handling for invalid system paths."""
+    loader = SystemLoader()
+
+    print("\n── Error handling examples ──")
+
+    # Non-existent path
+    try:
+        loader.load(Path("/nonexistent/system"))
+    except SystemLoadError as e:
+        print(f"  Non-existent path → SystemLoadError: {e}")
+
+    # Directory missing system.yaml
+    import tempfile
+
+    with tempfile.TemporaryDirectory() as tmpdir:
+        try:
+            loader.load(Path(tmpdir))
+        except SystemLoadError as e:
+            print(f"  Missing system.yaml → SystemLoadError: {e}")
+
+
+if __name__ == "__main__":
+    # Run all examples
+    for system_dir in ["knave-1e", "wyrdbound-quickstart-1e"]:
+        example_load_and_validate(system_dir)
+
+    example_inspect_models("knave-1e")
+    example_inspect_flows("knave-1e")
+    example_inspect_compendiums("knave-1e")
+    example_error_handling()

grimoire_spec-0.1.1/pyproject.toml

@@ -0,0 +1,38 @@
+[project]
+name = "grimoire-spec"
+version = "0.1.1"
+description = "GRIMOIRE system definition loader and validator for tabletop RPG systems"
+requires-python = ">=3.11"
+dependencies = [
+    "pyyaml>=6.0",
+]
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.0",
+    "ruff>=0.3",
+    "mypy>=1.9",
+    "types-PyYAML>=6.0",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/grimoire"]
+
+[tool.ruff]
+line-length = 88
+target-version = "py311"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP"]
+
+[tool.mypy]
+python_version = "3.11"
+strict = true
+ignore_missing_imports = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

grimoire_spec-0.1.1/release-please-config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
+  "release-type": "python",
+  "packages": {
+    ".": {
+      "release-type": "python",
+      "package-name": "grimoire-spec",
+      "version-file": "pyproject.toml"
+    }
+  }
+}