specfuse 0.2.0__tar.gz → 0.2.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (15) hide show
  1. {specfuse-0.2.0/specfuse.egg-info → specfuse-0.2.2}/PKG-INFO +28 -17
  2. specfuse-0.2.2/README.md +82 -0
  3. {specfuse-0.2.0 → specfuse-0.2.2}/pyproject.toml +2 -2
  4. {specfuse-0.2.0 → specfuse-0.2.2}/specfuse/cli.py +1 -1
  5. {specfuse-0.2.0 → specfuse-0.2.2/specfuse.egg-info}/PKG-INFO +28 -17
  6. {specfuse-0.2.0 → specfuse-0.2.2}/specfuse.egg-info/requires.txt +1 -1
  7. specfuse-0.2.0/README.md +0 -71
  8. {specfuse-0.2.0 → specfuse-0.2.2}/LICENSE +0 -0
  9. {specfuse-0.2.0 → specfuse-0.2.2}/NOTICE +0 -0
  10. {specfuse-0.2.0 → specfuse-0.2.2}/setup.cfg +0 -0
  11. {specfuse-0.2.0 → specfuse-0.2.2}/specfuse.egg-info/SOURCES.txt +0 -0
  12. {specfuse-0.2.0 → specfuse-0.2.2}/specfuse.egg-info/dependency_links.txt +0 -0
  13. {specfuse-0.2.0 → specfuse-0.2.2}/specfuse.egg-info/entry_points.txt +0 -0
  14. {specfuse-0.2.0 → specfuse-0.2.2}/specfuse.egg-info/top_level.txt +0 -0
  15. {specfuse-0.2.0 → specfuse-0.2.2}/tests/test_cli.py +0 -0
{specfuse-0.2.0/specfuse.egg-info → specfuse-0.2.2}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: specfuse
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Specfuse umbrella CLI — bridges the pip-installed driver and the Claude Code plugin (init / upgrade).
5
5
  Author: Specfuse contributors
6
6
  License: Apache-2.0
@@ -17,7 +17,7 @@ Requires-Python: >=3.10
17
17
  Description-Content-Type: text/markdown
18
18
  License-File: LICENSE
19
19
  License-File: NOTICE
20
- Requires-Dist: specfuse-loop>=0.3.0
20
+ Requires-Dist: specfuse-loop>=0.3.2
21
21
  Provides-Extra: dev
22
22
  Requires-Dist: coverage>=7.0; extra == "dev"
23
23
  Requires-Dist: ruff>=0.6; extra == "dev"
@@ -43,9 +43,10 @@ namespaced under `/specfuse:` (e.g. `/specfuse:pick-feature`,
43
43
  `/specfuse:draft-feature`, `/specfuse:arm-gate`). Update with `/plugin update
44
44
  specfuse@specfuse`; reload after changes with `/reload-plugins`.
45
45
 
46
- The skills drive the **specfuse-loop** driver (`pip install specfuse-loop`); see
47
- [specfuse/loop](https://github.com/specfuse/loop) for the methodology, the driver,
48
- and getting-started docs.
46
+ The skills drive the **specfuse-loop** driver — install it with the umbrella
47
+ package below (`pip install specfuse` pulls it), or on its own with `pip install
48
+ specfuse-loop`. See [specfuse/loop](https://github.com/specfuse/loop) for the
49
+ methodology, the driver, and getting-started docs.
49
50
 
50
51
  ## The `specfuse` umbrella CLI
51
52
 
@@ -53,16 +54,25 @@ This repo also ships the **`specfuse`** pip package — the umbrella CLI that br
53
54
  the pip-installed driver and this plugin:
54
55
 
55
56
  ```
56
- pip install specfuse # pulls specfuse-loop too
57
- specfuse upgrade # pip-upgrade driver + CLI, then points at /plugin update
58
- specfuse init <repo> # ensure the driver is installed; print bootstrap steps
57
+ pipx install specfuse # recommended (CLI app); pulls specfuse-loop too
58
+ # gives you: specfuse / specfuse-loop / specfuse-lint
59
+ # (or, inside a venv you control: python3 -m pip install specfuse)
60
+ specfuse init <repo> # scaffold .specfuse/ + wire .claude/ (--dry-run previews)
61
+ specfuse upgrade <repo> # overlay a newer scaffold, then pip-upgrade driver + CLI, point at /plugin update
59
62
  ```
60
63
 
61
- `specfuse` contributes to the shared `specfuse.*` import namespace (so
62
- `specfuse.loop` from the driver and a future `specfuse.orchestrator` coexist). Note:
63
- fully pip-native scaffolding (`specfuse init` laying down `.specfuse/` templates and
64
- rules) is deferred — until it ships, scaffolding a new repo still uses the loop's
65
- `init.sh`; `specfuse upgrade` already owns the pip ↔ plugin bridge.
64
+ > A bare `pip install` into a system Python is blocked on PEP-668
65
+ > externally-managed environments (Debian/Ubuntu, Homebrew). Use `pipx` (then
66
+ > `pipx upgrade specfuse`) or a virtualenv, so `specfuse-loop` / `specfuse-lint`
67
+ > land on PATH for the gate commands to find.
68
+
69
+ `specfuse init` lays down `.specfuse/` (templates, rules, docs, `verification.yml`)
70
+ and merge-safely wires `.claude/` (including this plugin's config) — pip-native
71
+ scaffolding via `specfuse.loop.scaffold`, no `init.sh` checkout required. Every
72
+ `specfuse-loop` run also self-provisions (version-syncs `.specfuse/` from the
73
+ installed package), so `pip install -U specfuse` reaches existing projects on
74
+ their next run. `specfuse` contributes to the shared `specfuse.*` import namespace
75
+ (so `specfuse.loop` from the driver and a future `specfuse.orchestrator` coexist).
66
76
 
67
77
  ## Plugins
68
78
 
@@ -86,10 +96,11 @@ plugins/specfuse/
86
96
 
87
97
  The skills here are the same craft authored in
88
98
  [`specfuse/loop`](https://github.com/specfuse/loop)'s `.specfuse/skills/`. The loop
89
- repo is canonical; a sync step keeps this plugin's copy current (see the loop's
90
- FEAT-2026-0019). Until the native-plugin migration completes, the loop's `init.sh`
91
- also installs these skills into a target repo's `.specfuse/skills/` — the plugin is
92
- the forward path, `init.sh` the legacy one.
99
+ repo is canonical; a sync step keeps this plugin's copy current. Skills reach a
100
+ target repo through this plugin (under the `/specfuse:` namespace) — `specfuse
101
+ init` wires the plugin into the repo's `.claude/settings.json`; it does not copy
102
+ skill files into the repo. (`init.sh` is a deprecated v1.0 shim that delegates to
103
+ `specfuse init`/`upgrade`.)
93
104
 
94
105
  ## License
95
106
 
specfuse-0.2.2/README.md ADDED
@@ -0,0 +1,82 @@
1
+ # Specfuse — Claude Code plugin marketplace
2
+
3
+ This repository is the [Claude Code plugin
4
+ marketplace](https://code.claude.com/docs/en/plugin-marketplaces) for the
5
+ **Specfuse gate-cycle methodology**. It is the shared distribution home so the
6
+ loop today — and the orchestrator and future products later — install their Claude
7
+ assets from one place.
8
+
9
+ ## Install
10
+
11
+ ```
12
+ /plugin marketplace add specfuse/specfuse
13
+ /plugin install specfuse@specfuse
14
+ ```
15
+
16
+ That installs the **`specfuse`** plugin: the methodology's interactive skills,
17
+ namespaced under `/specfuse:` (e.g. `/specfuse:pick-feature`,
18
+ `/specfuse:draft-feature`, `/specfuse:arm-gate`). Update with `/plugin update
19
+ specfuse@specfuse`; reload after changes with `/reload-plugins`.
20
+
21
+ The skills drive the **specfuse-loop** driver — install it with the umbrella
22
+ package below (`pip install specfuse` pulls it), or on its own with `pip install
23
+ specfuse-loop`. See [specfuse/loop](https://github.com/specfuse/loop) for the
24
+ methodology, the driver, and getting-started docs.
25
+
26
+ ## The `specfuse` umbrella CLI
27
+
28
+ This repo also ships the **`specfuse`** pip package — the umbrella CLI that bridges
29
+ the pip-installed driver and this plugin:
30
+
31
+ ```
32
+ pipx install specfuse # recommended (CLI app); pulls specfuse-loop too
33
+ # gives you: specfuse / specfuse-loop / specfuse-lint
34
+ # (or, inside a venv you control: python3 -m pip install specfuse)
35
+ specfuse init <repo> # scaffold .specfuse/ + wire .claude/ (--dry-run previews)
36
+ specfuse upgrade <repo> # overlay a newer scaffold, then pip-upgrade driver + CLI, point at /plugin update
37
+ ```
38
+
39
+ > A bare `pip install` into a system Python is blocked on PEP-668
40
+ > externally-managed environments (Debian/Ubuntu, Homebrew). Use `pipx` (then
41
+ > `pipx upgrade specfuse`) or a virtualenv, so `specfuse-loop` / `specfuse-lint`
42
+ > land on PATH for the gate commands to find.
43
+
44
+ `specfuse init` lays down `.specfuse/` (templates, rules, docs, `verification.yml`)
45
+ and merge-safely wires `.claude/` (including this plugin's config) — pip-native
46
+ scaffolding via `specfuse.loop.scaffold`, no `init.sh` checkout required. Every
47
+ `specfuse-loop` run also self-provisions (version-syncs `.specfuse/` from the
48
+ installed package), so `pip install -U specfuse` reaches existing projects on
49
+ their next run. `specfuse` contributes to the shared `specfuse.*` import namespace
50
+ (so `specfuse.loop` from the driver and a future `specfuse.orchestrator` coexist).
51
+
52
+ ## Plugins
53
+
54
+ | Plugin | What it ships | Source |
55
+ |--------|----------------|--------|
56
+ | `specfuse` | Gate-cycle skills (pick / draft / arm / diagnose / wrap, authoring, verification) | [`plugins/specfuse/`](plugins/specfuse/) |
57
+
58
+ Future products (orchestrator, shared core) will add entries here and reuse the
59
+ same marketplace.
60
+
61
+ ## Layout
62
+
63
+ ```
64
+ .claude-plugin/marketplace.json # this marketplace's catalog
65
+ plugins/specfuse/
66
+ .claude-plugin/plugin.json # the specfuse plugin manifest
67
+ skills/<skill>/SKILL.md # the gate-cycle skills
68
+ ```
69
+
70
+ ## Relationship to specfuse/loop
71
+
72
+ The skills here are the same craft authored in
73
+ [`specfuse/loop`](https://github.com/specfuse/loop)'s `.specfuse/skills/`. The loop
74
+ repo is canonical; a sync step keeps this plugin's copy current. Skills reach a
75
+ target repo through this plugin (under the `/specfuse:` namespace) — `specfuse
76
+ init` wires the plugin into the repo's `.claude/settings.json`; it does not copy
77
+ skill files into the repo. (`init.sh` is a deprecated v1.0 shim that delegates to
78
+ `specfuse init`/`upgrade`.)
79
+
80
+ ## License
81
+
82
+ Apache License 2.0. See [`LICENSE`](LICENSE).
{specfuse-0.2.0 → specfuse-0.2.2}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "specfuse"
7
- version = "0.2.0"
7
+ version = "0.2.2"
8
8
  description = "Specfuse umbrella CLI — bridges the pip-installed driver and the Claude Code plugin (init / upgrade)."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
@@ -25,7 +25,7 @@ classifiers = [
25
25
  # `specfuse.loop.scaffold`, which only exists in specfuse-loop 0.3.0+ (added by
26
26
  # FEAT-2026-0026). A 0.2.x driver would import-fail at `specfuse init`.
27
27
  dependencies = [
28
- "specfuse-loop>=0.3.0",
28
+ "specfuse-loop>=0.3.2",
29
29
  ]
30
30
 
31
31
  [project.optional-dependencies]
{specfuse-0.2.0 → specfuse-0.2.2}/specfuse/cli.py RENAMED
@@ -31,7 +31,7 @@ from pathlib import Path
31
31
 
32
32
  from specfuse.loop import scaffold
33
33
 
34
- __version__ = "0.2.0"
34
+ __version__ = "0.2.2"
35
35
 
36
36
  MARKETPLACE = "specfuse/specfuse"
37
37
  PLUGIN = "specfuse@specfuse"
{specfuse-0.2.0 → specfuse-0.2.2/specfuse.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: specfuse
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Specfuse umbrella CLI — bridges the pip-installed driver and the Claude Code plugin (init / upgrade).
5
5
  Author: Specfuse contributors
6
6
  License: Apache-2.0
@@ -17,7 +17,7 @@ Requires-Python: >=3.10
17
17
  Description-Content-Type: text/markdown
18
18
  License-File: LICENSE
19
19
  License-File: NOTICE
20
- Requires-Dist: specfuse-loop>=0.3.0
20
+ Requires-Dist: specfuse-loop>=0.3.2
21
21
  Provides-Extra: dev
22
22
  Requires-Dist: coverage>=7.0; extra == "dev"
23
23
  Requires-Dist: ruff>=0.6; extra == "dev"
@@ -43,9 +43,10 @@ namespaced under `/specfuse:` (e.g. `/specfuse:pick-feature`,
43
43
  `/specfuse:draft-feature`, `/specfuse:arm-gate`). Update with `/plugin update
44
44
  specfuse@specfuse`; reload after changes with `/reload-plugins`.
45
45
 
46
- The skills drive the **specfuse-loop** driver (`pip install specfuse-loop`); see
47
- [specfuse/loop](https://github.com/specfuse/loop) for the methodology, the driver,
48
- and getting-started docs.
46
+ The skills drive the **specfuse-loop** driver — install it with the umbrella
47
+ package below (`pip install specfuse` pulls it), or on its own with `pip install
48
+ specfuse-loop`. See [specfuse/loop](https://github.com/specfuse/loop) for the
49
+ methodology, the driver, and getting-started docs.
49
50
 
50
51
  ## The `specfuse` umbrella CLI
51
52
 
@@ -53,16 +54,25 @@ This repo also ships the **`specfuse`** pip package — the umbrella CLI that br
53
54
  the pip-installed driver and this plugin:
54
55
 
55
56
  ```
56
- pip install specfuse # pulls specfuse-loop too
57
- specfuse upgrade # pip-upgrade driver + CLI, then points at /plugin update
58
- specfuse init <repo> # ensure the driver is installed; print bootstrap steps
57
+ pipx install specfuse # recommended (CLI app); pulls specfuse-loop too
58
+ # gives you: specfuse / specfuse-loop / specfuse-lint
59
+ # (or, inside a venv you control: python3 -m pip install specfuse)
60
+ specfuse init <repo> # scaffold .specfuse/ + wire .claude/ (--dry-run previews)
61
+ specfuse upgrade <repo> # overlay a newer scaffold, then pip-upgrade driver + CLI, point at /plugin update
59
62
  ```
60
63
 
61
- `specfuse` contributes to the shared `specfuse.*` import namespace (so
62
- `specfuse.loop` from the driver and a future `specfuse.orchestrator` coexist). Note:
63
- fully pip-native scaffolding (`specfuse init` laying down `.specfuse/` templates and
64
- rules) is deferred — until it ships, scaffolding a new repo still uses the loop's
65
- `init.sh`; `specfuse upgrade` already owns the pip ↔ plugin bridge.
64
+ > A bare `pip install` into a system Python is blocked on PEP-668
65
+ > externally-managed environments (Debian/Ubuntu, Homebrew). Use `pipx` (then
66
+ > `pipx upgrade specfuse`) or a virtualenv, so `specfuse-loop` / `specfuse-lint`
67
+ > land on PATH for the gate commands to find.
68
+
69
+ `specfuse init` lays down `.specfuse/` (templates, rules, docs, `verification.yml`)
70
+ and merge-safely wires `.claude/` (including this plugin's config) — pip-native
71
+ scaffolding via `specfuse.loop.scaffold`, no `init.sh` checkout required. Every
72
+ `specfuse-loop` run also self-provisions (version-syncs `.specfuse/` from the
73
+ installed package), so `pip install -U specfuse` reaches existing projects on
74
+ their next run. `specfuse` contributes to the shared `specfuse.*` import namespace
75
+ (so `specfuse.loop` from the driver and a future `specfuse.orchestrator` coexist).
66
76
 
67
77
  ## Plugins
68
78
 
@@ -86,10 +96,11 @@ plugins/specfuse/
86
96
 
87
97
  The skills here are the same craft authored in
88
98
  [`specfuse/loop`](https://github.com/specfuse/loop)'s `.specfuse/skills/`. The loop
89
- repo is canonical; a sync step keeps this plugin's copy current (see the loop's
90
- FEAT-2026-0019). Until the native-plugin migration completes, the loop's `init.sh`
91
- also installs these skills into a target repo's `.specfuse/skills/` — the plugin is
92
- the forward path, `init.sh` the legacy one.
99
+ repo is canonical; a sync step keeps this plugin's copy current. Skills reach a
100
+ target repo through this plugin (under the `/specfuse:` namespace) — `specfuse
101
+ init` wires the plugin into the repo's `.claude/settings.json`; it does not copy
102
+ skill files into the repo. (`init.sh` is a deprecated v1.0 shim that delegates to
103
+ `specfuse init`/`upgrade`.)
93
104
 
94
105
  ## License
95
106
 
{specfuse-0.2.0 → specfuse-0.2.2}/specfuse.egg-info/requires.txt RENAMED
@@ -1,4 +1,4 @@
1
- specfuse-loop>=0.3.0
1
+ specfuse-loop>=0.3.2
2
2
 
3
3
  [dev]
4
4
  coverage>=7.0
specfuse-0.2.0/README.md DELETED
@@ -1,71 +0,0 @@
1
- # Specfuse — Claude Code plugin marketplace
2
-
3
- This repository is the [Claude Code plugin
4
- marketplace](https://code.claude.com/docs/en/plugin-marketplaces) for the
5
- **Specfuse gate-cycle methodology**. It is the shared distribution home so the
6
- loop today — and the orchestrator and future products later — install their Claude
7
- assets from one place.
8
-
9
- ## Install
10
-
11
- ```
12
- /plugin marketplace add specfuse/specfuse
13
- /plugin install specfuse@specfuse
14
- ```
15
-
16
- That installs the **`specfuse`** plugin: the methodology's interactive skills,
17
- namespaced under `/specfuse:` (e.g. `/specfuse:pick-feature`,
18
- `/specfuse:draft-feature`, `/specfuse:arm-gate`). Update with `/plugin update
19
- specfuse@specfuse`; reload after changes with `/reload-plugins`.
20
-
21
- The skills drive the **specfuse-loop** driver (`pip install specfuse-loop`); see
22
- [specfuse/loop](https://github.com/specfuse/loop) for the methodology, the driver,
23
- and getting-started docs.
24
-
25
- ## The `specfuse` umbrella CLI
26
-
27
- This repo also ships the **`specfuse`** pip package — the umbrella CLI that bridges
28
- the pip-installed driver and this plugin:
29
-
30
- ```
31
- pip install specfuse # pulls specfuse-loop too
32
- specfuse upgrade # pip-upgrade driver + CLI, then points at /plugin update
33
- specfuse init <repo> # ensure the driver is installed; print bootstrap steps
34
- ```
35
-
36
- `specfuse` contributes to the shared `specfuse.*` import namespace (so
37
- `specfuse.loop` from the driver and a future `specfuse.orchestrator` coexist). Note:
38
- fully pip-native scaffolding (`specfuse init` laying down `.specfuse/` templates and
39
- rules) is deferred — until it ships, scaffolding a new repo still uses the loop's
40
- `init.sh`; `specfuse upgrade` already owns the pip ↔ plugin bridge.
41
-
42
- ## Plugins
43
-
44
- | Plugin | What it ships | Source |
45
- |--------|----------------|--------|
46
- | `specfuse` | Gate-cycle skills (pick / draft / arm / diagnose / wrap, authoring, verification) | [`plugins/specfuse/`](plugins/specfuse/) |
47
-
48
- Future products (orchestrator, shared core) will add entries here and reuse the
49
- same marketplace.
50
-
51
- ## Layout
52
-
53
- ```
54
- .claude-plugin/marketplace.json # this marketplace's catalog
55
- plugins/specfuse/
56
- .claude-plugin/plugin.json # the specfuse plugin manifest
57
- skills/<skill>/SKILL.md # the gate-cycle skills
58
- ```
59
-
60
- ## Relationship to specfuse/loop
61
-
62
- The skills here are the same craft authored in
63
- [`specfuse/loop`](https://github.com/specfuse/loop)'s `.specfuse/skills/`. The loop
64
- repo is canonical; a sync step keeps this plugin's copy current (see the loop's
65
- FEAT-2026-0019). Until the native-plugin migration completes, the loop's `init.sh`
66
- also installs these skills into a target repo's `.specfuse/skills/` — the plugin is
67
- the forward path, `init.sh` the legacy one.
68
-
69
- ## License
70
-
71
- Apache License 2.0. See [`LICENSE`](LICENSE).
{specfuse-0.2.0 → specfuse-0.2.2}/LICENSE RENAMED
File without changes
{specfuse-0.2.0 → specfuse-0.2.2}/NOTICE RENAMED
File without changes
{specfuse-0.2.0 → specfuse-0.2.2}/setup.cfg RENAMED
File without changes
{specfuse-0.2.0 → specfuse-0.2.2}/tests/test_cli.py RENAMED
File without changes