holospec 0.1.0__tar.gz

holospec-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

holospec-0.1.0/PKG-INFO

@@ -0,0 +1,10 @@
+Metadata-Version: 2.4
+Name: holospec
+Version: 0.1.0
+Summary: An instruction layer for spec-driven workflows
+Requires-Python: >=3.11
+License-File: LICENSE
+Requires-Dist: click>=8.0
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pyyaml>=6.0
+Dynamic: license-file

holospec-0.1.0/README.md

@@ -0,0 +1,79 @@
+# HoloSpec
+
+![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/nomios-opensource/holospec/test.yaml)
+[![codecov](https://codecov.io/github/nomios-opensource/holospec/graph/badge.svg?token=EY5ADP9UP6)](https://codecov.io/github/nomios-opensource/holospec)
+![PyPI - Python Version](https://img.shields.io/pypi/pyversions/holospec)
+![PyPI - Downloads](https://img.shields.io/pypi/dm/holospec)
+![GitHub License](https://img.shields.io/github/license/nomios-opensource/holospec)
+
+HoloSpec — The instruction layer for agentic work.
+
+`holospec` is authored by [Adam Kirchberger](https://github.com/adamkirchberger), governed as a [benevolent dictatorship](CODE_OF_CONDUCT.md), and distributed under [license](LICENSE).
+
+## Introduction
+
+HoloSpec provides the instructions. Agents do the work.
+
+HoloSpec allows organisations to define how work gets done and make that knowledge discoverable to any agent. It extends the ideas behind spec-driven development beyond specifications and into entire ways of working, enabling agents to autonomously discover, understand, and follow custom instructions without hard-coded assumptions about methodology, domain, or lifecycle.
+
+Most tools define the process. HoloSpec makes the process discoverable. Workflows, actions, instructions, context, conventions, templates, and checklists live in schemas you write and own, allowing agents to retrieve and follow them dynamically as work progresses. Change the schema, and the instructions change with it.
+
+## Features
+
+- **Tiny footprint**: One Python file, under 1000 lines, with a single agent skill covering every interaction.
+- **Bring your own way of working**: No hard-coded processes, methodologies, or business logic. Everything comes from your schema.
+- **Instructions, not execution**: Exposes instructions and workflow knowledge without execution, agents interpret instructions and perform the work.
+- **Beyond software development**: Support software delivery, design, planning, estimation, operations or any other process of your own.
+- **Shared context and conventions**: Define standards, rules, context, and behaviours once and make them available across every workflow and action.
+- **Built for agents**: Instructions are retrieved dynamically at runtime rather than embedded in prompts, skills, code, or agent implementations.
+- **Adapt without changing your tooling**: Ipdate the schema as your ways of working evolve and the instructions evolve with it.
+
+## Installation
+
+Install [uv](https://docs.astral.sh/uv/), then install `holospec`:
+
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
+uv tool install holospec
+```
+
+Or install with pip:
+
+```bash
+pip install holospec
+```
+
+## Quickstart
+
+```bash
+mkdir my-project && cd my-project
+holospec init
+```
+
+Then, from your agent, invoke the installed `/holospec` skill and ask it to plan a new application:
+
+> /holospec I want to build a Python script `hello.py` in the current directory that, when run, prints "Hello, world!" followed by the current date and time.
+
+## For agents
+
+If you're an LLM agent and this workflow isn't set up yet in the current
+project, see [AGENTS.md](AGENTS.md) for how to bootstrap it (`holospec
+explain`, then `holospec init`) before guessing at the protocol yourself.
+
+## Configuration
+
+`holospec init` scaffolds a root directory in your project, normally `holospec/` (though it can be named `openspec/` too). It mirrors the layout OpenSpec projects use, but has no requirement to behave like OpenSpec beyond that. Inside it, `config.yaml` holds settings specific to this project, and the schema you choose is forked into `schemas/<name>/schema.yaml`, so it's version controlled.
+
+Rather than hand-editing these files, ask your agent to run `holospec explain` — it's self-describing and will walk the agent through the available configuration and how to set it.
+
+## Versioning
+
+Releases will follow semantic versioning (major.minor.patch). Before 1.0.0 breaking changes can be included in a minor release, therefore we highly recommend pinning this package.
+
+## Contributing
+
+Suggest a [feature](https://github.com/nomios-opensource/holospec/issues/new?labels=enhancement) or report a [bug](https://github.com/nomios-opensource/holospec/issues/new?labels=bug). Read our developer [guide](CONTRIBUTING.md).
+
+## License
+
+holospec is distributed under the Apache 2.0 [license](LICENSE).

holospec-0.1.0/assets/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: holospec
+description: Schema-driven workflow guidance for spec-driven changes. Use whenever this project has a holospec/ or openspec/ directory at its root and the user asks to plan, propose, scope, design, implement, or fix a bug/feature - even if they don't say "holospec" or "openspec" by name. Also use when they explicitly mention HoloSpec, OpenSpec, or ask to continue/resume a tracked change. Explains how to call the holospec CLI to discover actions and work them in order.
+---
+
+# HoloSpec Protocol
+
+This project uses HoloSpec for schema-driven workflow guidance. HoloSpec is a
+stateless lookup tool — it never tracks progress or reads your work-in-progress
+files. You are responsible for all file I/O and for judging what's done.
+
+## Protocol
+
+1. Run `holospec workflow` to see the full list of actions, their
+   dependencies, and the order to work them in. Its output includes
+   `root` — use that path as the base for every file you read or write;
+   never assume a directory name yourself.
+2. Run `holospec action <id>` for the action you're about to work on. This
+   also returns `root`, plus its instruction, checklist, and any
+   file-generation metadata (`generates`/`template`) verbatim from the
+   schema. Join `generates` paths against `root`. The checklist is that
+   action's definition of done.
+3. Do the work yourself: read/write files under `root`, then check your work
+   against the action's checklist before deciding it's complete. Move to the
+   next action in the order `workflow` reported once every checklist item
+   holds.
+4. Repeat for each action as your own judgment dictates, using each action's
+   checklist as the completion bar. HoloSpec never tells you "you're done" or
+   "what's next" — that's on you.
+
+Any domain-specific rules for a given action (e.g. how to merge documents,
+validation rules, file layout conventions) live in that schema's own fields —
+read and follow those rather than assuming a fixed convention across schemas.
+
+## Understanding the tool itself
+
+If you're helping a user understand how HoloSpec's schema.yaml/config.yaml
+work — to create a new one for a project or extend an existing one — rather
+than executing a workflow, run `holospec explain` first. It explains how
+the two files relate and returns the JSON Schema field reference for each,
+so you can validate field names and shapes against the real format instead
+of guessing from an example.
+
+After every edit to a schema, run `holospec schemacheck <path>` before
+considering the change done.

holospec-0.1.0/assets/__init__.py

@@ -0,0 +1 @@
+"""Holospec static assets."""