ai-forge-cli 2.0.0__tar.gz → 2.0.1__tar.gz

{ai_forge_cli-2.0.0/src/ai_forge_cli.egg-info → ai_forge_cli-2.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ai-forge-cli
-Version: 2.0.0
+Version: 2.0.1
 Summary: Context walker for the Forge spec system
 Requires-Python: >=3.11
 License-File: LICENSE

{ai_forge_cli-2.0.0 → ai_forge_cli-2.0.1}/README.md

@@ -25,7 +25,7 @@ A hierarchical YAML spec system, a Python CLI for context assembly, and **six ag
 
 Built on the premise that **people explain systems well under questioning but poorly when cold-prompted**. Forge inverts the default "human prompts agent → agent implements" loop into "agent interviews human → structured spec emerges → agent implements from spec".
 
-Runs in **Claude Code** and any **agentskills.io-compatible client** (VS Code Copilot, Cursor).
+Runs in any agent client that supports skills: **Claude Code**, **OpenAI Codex CLI**, **VS Code Copilot**, **Cursor**, and any other agentskills.io-compatible client.
 
 ---
 
@@ -64,7 +64,7 @@ uv venv --python 3.13 .venv && uv pip install -e . pytest
 ./scripts/install-skills.sh install
 ```
 
-This wires the `forge` binary into `~/.local/bin/` and symlinks the six skills into `~/.claude/skills/` and `~/.agents/skills/` — discoverable by every supported client.
+This wires the `forge` binary into `~/.local/bin/` and symlinks the six skills into `~/.claude/skills/`, `~/.codex/skills/`, and `~/.agents/skills/` — discoverable by every supported client.
 
 ### Verify
 
@@ -80,7 +80,7 @@ forge --help              # shows: init, update, context, list, inspect, find, v
 |---|---|
 | Python | ≥ 3.13 |
 | Package manager | [`uv`](https://docs.astral.sh/uv/) recommended; pip works |
-| Agent client | Claude Code or an agentskills.io-compatible client |
+| Agent client | Claude Code, Codex CLI, or any agentskills.io-compatible client |
 
 If `forge: command not found`: add `~/.local/bin` to PATH.
 
@@ -156,7 +156,7 @@ Spec-dir resolution order: `--spec-dir` flag > `$FORGE_SPEC_DIR` env var > auto-
 | **forge-build** | Implementation orchestrator | Reviewed spec corpus | Code + tests dispatched via parallel subagents, each using `forge context <id>` |
 | **forge-validate** | Post-implementation validator | Implemented system + spec | Static analysis, test coverage, behavioral probes, workbench/validation.md |
 
-Skills activate via natural-language prompts (universal) or slash-commands (Claude Code only).
+Skills activate via natural-language prompts in any supported client, or slash-commands where the client supports them.
 
 ---
 

{ai_forge_cli-2.0.0 → ai_forge_cli-2.0.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ai-forge-cli"
-version = "2.0.0"
+version = "2.0.1"
 description = "Context walker for the Forge spec system"
 requires-python = ">=3.11"
 dependencies = ["pyyaml>=6.0"]
@@ -17,7 +17,7 @@ where = ["src"]
 include = ["cli*"]
 
 [tool.setuptools.package-data]
-cli = ["framework.yaml"]
+cli = ["framework.yaml", "skills/*/SKILL.md", "skills/*/references/*", "skills/*/assets/**/*"]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

{ai_forge_cli-2.0.0 → ai_forge_cli-2.0.1/src/ai_forge_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ai-forge-cli
-Version: 2.0.0
+Version: 2.0.1
 Summary: Context walker for the Forge spec system
 Requires-Python: >=3.11
 License-File: LICENSE

ai_forge_cli-2.0.1/src/ai_forge_cli.egg-info/SOURCES.txt

@@ -0,0 +1,57 @@
+LICENSE
+README.md
+pyproject.toml
+src/ai_forge_cli.egg-info/PKG-INFO
+src/ai_forge_cli.egg-info/SOURCES.txt
+src/ai_forge_cli.egg-info/dependency_links.txt
+src/ai_forge_cli.egg-info/entry_points.txt
+src/ai_forge_cli.egg-info/requires.txt
+src/ai_forge_cli.egg-info/top_level.txt
+src/cli/__init__.py
+src/cli/__main__.py
+src/cli/bundle.py
+src/cli/common.py
+src/cli/forge.py
+src/cli/framework.yaml
+src/cli/index.py
+src/cli/walker.py
+src/cli/commands/__init__.py
+src/cli/commands/base.py
+src/cli/commands/context.py
+src/cli/commands/find.py
+src/cli/commands/graph.py
+src/cli/commands/init.py
+src/cli/commands/inspect.py
+src/cli/commands/list_cmd.py
+src/cli/commands/update.py
+src/cli/commands/validate.py
+src/cli/skills/forge-build/SKILL.md
+src/cli/skills/forge-build/references/framework.md
+src/cli/skills/forge-build/references/framework.yaml
+src/cli/skills/forge-build/references/templates.yaml
+src/cli/skills/forge-cast/SKILL.md
+src/cli/skills/forge-cast/references/framework.md
+src/cli/skills/forge-cast/references/framework.yaml
+src/cli/skills/forge-cast/references/templates.yaml
+src/cli/skills/forge-design/SKILL.md
+src/cli/skills/forge-design/references/framework.md
+src/cli/skills/forge-design/references/framework.yaml
+src/cli/skills/forge-design/references/templates.yaml
+src/cli/skills/forge-review/SKILL.md
+src/cli/skills/forge-review/references/framework.md
+src/cli/skills/forge-review/references/framework.yaml
+src/cli/skills/forge-review/references/templates.yaml
+src/cli/skills/forge-spec/SKILL.md
+src/cli/skills/forge-spec/references/framework.md
+src/cli/skills/forge-spec/references/framework.yaml
+src/cli/skills/forge-spec/references/templates.yaml
+src/cli/skills/forge-validate/SKILL.md
+src/cli/skills/forge-validate/references/framework.md
+src/cli/skills/forge-validate/references/framework.yaml
+src/cli/skills/forge-validate/references/templates.yaml
+tests/test_cli.py
+tests/test_find.py
+tests/test_index.py
+tests/test_init.py
+tests/test_update.py
+tests/test_walker.py

{ai_forge_cli-2.0.0 → ai_forge_cli-2.0.1}/src/cli/commands/init.py

@@ -1,8 +1,8 @@
 """`forge init` — scaffold a new Forge project in the current directory.
 
 Creates spec/ with framework.yaml (bundled vocabulary) and a blank
-conception.yaml stub. The directory layout under spec/ is created by the
-user as they build out the spec; init only provides the anchors.
+conception.yaml stub. Also symlinks the six Forge skills into the agent
+skill directories used by Claude Code, Codex CLI, and agentskills.io clients.
 """
 
 from __future__ import annotations
@@ -18,15 +18,32 @@ import cli
 NAME = "init"
 HELP = "Scaffold a new Forge project in the current directory."
 DESCRIPTION = (
-    "Creates the spec/ directory and copies framework.yaml (the bundled "
-    "framework vocabulary: enums, built-in scalars, built-in errors) into it. "
-    "Also writes a blank conception.yaml stub. Run in a new or empty project "
-    "directory to bootstrap."
+    "Creates the spec/ directory, copies framework.yaml (the bundled "
+    "framework vocabulary: enums, built-in scalars, built-in errors), "
+    "writes a blank conception.yaml stub, and symlinks the six Forge skills "
+    "into ~/.claude/skills/, ~/.codex/skills/, and ~/.agents/skills/."
 )
 
 # Markers that indicate an existing Forge project.
 _EXISTING_MARKERS = ("conception.yaml", "framework.yaml")
 
+# Skill names bundled with the package.
+SKILL_NAMES = (
+    "forge-design",
+    "forge-spec",
+    "forge-review",
+    "forge-build",
+    "forge-validate",
+    "forge-cast",
+)
+
+# Global skill scan directories (one per supported agent client).
+_SKILL_SCAN_DIRS = (
+    Path.home() / ".claude" / "skills",
+    Path.home() / ".codex" / "skills",
+    Path.home() / ".agents" / "skills",
+)
+
 # --- Banner -------------------------------------------------------------------
 
 _RESET = "\033[0m"
@@ -132,6 +149,10 @@ def register(sub: argparse._SubParsersAction) -> None:
         "--no-banner", action="store_true",
         help="Skip the init banner animation.",
     )
+    p.add_argument(
+        "--skip-skills", action="store_true",
+        help="Skip skill symlink installation.",
+    )
     p.set_defaults(handler=run)
 
 
@@ -170,6 +191,11 @@ def run(args: argparse.Namespace) -> int:
     # Write blank conception.yaml stub.
     _install_conception(spec_dir, force=args.force, ok=ok)
 
+    # Symlink skills into agent client scan directories.
+    if not args.skip_skills:
+        print()
+        _install_skills(force=args.force, ok=ok)
+
     print()
     print(_divider("Next steps"))
     print()
@@ -217,3 +243,60 @@ def _install_conception(spec_dir: Path, *, force: bool, ok: str) -> None:
         return
     dest.write_text(_CONCEPTION_STUB, encoding="utf-8")
     print(f"  {ok} spec/conception.yaml {_dim('(fill in your conception details)')}")
+
+
+def _skills_src() -> Path | None:
+    """Return the bundled skills directory, or None if not found."""
+    cli_dir = Path(cli.__file__).resolve().parent
+    skills_dir = cli_dir / "skills"
+    return skills_dir if skills_dir.is_dir() else None
+
+
+def _install_skills(*, force: bool, ok: str) -> None:
+    """Symlink each bundled skill into all agent client scan directories."""
+    skills_dir = _skills_src()
+    if skills_dir is None:
+        print(_dim("  - skills directory not found in package; skipping"))
+        return
+
+    linked = 0
+    skipped = 0
+    errors = 0
+
+    for scan_dir in _SKILL_SCAN_DIRS:
+        try:
+            scan_dir.mkdir(parents=True, exist_ok=True)
+        except OSError:
+            continue
+
+        for name in SKILL_NAMES:
+            src = skills_dir / name
+            if not src.is_dir():
+                continue
+            dest = scan_dir / name
+
+            if dest.is_symlink():
+                if force:
+                    dest.unlink()
+                else:
+                    skipped += 1
+                    continue
+            elif dest.exists():
+                errors += 1
+                print(f"  {_color(160, '✗')} {dest} exists and is not a symlink — skipping")
+                continue
+
+            try:
+                dest.symlink_to(src)
+                linked += 1
+            except OSError as e:
+                errors += 1
+                print(f"  {_color(160, '✗')} could not link {dest}: {e}")
+
+    if linked:
+        short_dirs = ", ".join(f"~/{d.relative_to(Path.home())}" for d in _SKILL_SCAN_DIRS)
+        print(f"  {ok} {linked} skill link{'s' if linked != 1 else ''} → {short_dirs}")
+    if skipped:
+        print(_dim(f"  - {skipped} skill link{'s' if skipped != 1 else ''} already present; use --force to refresh"))
+    if not linked and not skipped and not errors:
+        print(_dim("  - no skills to install"))

{ai_forge_cli-2.0.0 → ai_forge_cli-2.0.1}/src/cli/commands/update.py

@@ -64,6 +64,9 @@ def run(args: argparse.Namespace) -> int:
 
     init_cmd._install_framework(spec_dir, force=args.force, ok=ok)
 
+    print()
+    init_cmd._install_skills(force=args.force, ok=ok)
+
     print()
     print(init_cmd._divider("Done"))
     print()

ai_forge_cli-2.0.1/src/cli/skills/forge-build/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: forge-build
+description: >
+  Forge implementation orchestrator. Use when the spec is complete and reviewed (forge-review
+  has run clean) and the user wants to generate working implementation code and tests.
+  Writes a dynamic task list to workbench/build-plan.md, then dispatches subagents to implement
+  each task using `forge context` to pull their own context from the CLI. Subagent granularity
+  is determined dynamically based on system size. Orchestrator retries failures automatically
+  before surfacing to the human.
+  Triggers on: "implement this", "build the code", "forge-build", or any request to generate
+  implementation from a complete Forge spec.
+---
+
+# forge-build
+
+Read `references/framework.md` before starting. Read `workbench/discovery.md` for system context.
+
+## Purpose
+
+Orchestrate implementation of a complete, reviewed Forge spec. The orchestrator plans, dispatches subagents, tracks progress, and retries failures. Subagents are isolated — each one receives only a task ID and runs `forge context` to get everything it needs.
+
+## Step 1 — System Assessment
+
+Before writing anything:
+
+```bash
+forge list --kind element --ids-only   # enumerate all elements
+forge list --kind module               # understand module boundaries
+forge validate                         # must be clean before proceeding
+```
+
+If `forge validate` has errors, stop and tell the human to run `forge-review` first.
+
+Count elements and determine task granularity:
+
+| System size | Granularity |
+|-------------|-------------|
+| < 10 elements | module-level tasks (one subagent implements all elements in a module) |
+| 10–40 elements | element-level tasks (one subagent per element) |
+| > 40 elements | element-level tasks with parallel dispatch (multiple subagents concurrently) |
+
+## Step 2 — Build Plan
+
+Write `workbench/build-plan.md` before dispatching any subagents:
+
+```markdown
+# Build Plan — <date>
+
+## System: <system-id>
+## Granularity: <module | element>
+## Total tasks: <N>
+
+## Tasks
+
+| ID | Target | Dependencies | Status | Attempts |
+|----|--------|-------------|--------|----------|
+| task_001 | <element-or-module-id> | [] | pending | 0 |
+| task_002 | <element-or-module-id> | [task_001] | pending | 0 |
+...
+
+## Architecture Decisions
+[Extract from workbench/discovery.md: language, runtime, framework, DI pattern, error handling style, test framework]
+```
+
+**Dependency ordering**: tasks whose target element has operations called by other elements must complete before their dependents. Use `forge inspect <id>` to discover caller/callee relationships. Tasks with no inter-dependencies can run in parallel.
+
+Present the build plan to the human and get confirmation before dispatching.
+
+## Step 3 — Subagent Dispatch
+
+For each task in dependency order:
+
+### Subagent prompt template
+
+```
+You are implementing a single unit of a Forge spec.
+
+Target: <element-or-module-id>
+Task ID: <task_id>
+
+## Your context
+
+Run this command to get your full implementation context:
+  forge context <element-or-module-id> --format markdown
+
+The output contains: the element with all properties and operations, parent module/domain/system,
+all referenced types (transitive), errors, contracts, interactions, cascaded policies, and datastores.
+
+## Architecture
+
+<paste the Architecture Decisions section from build-plan.md>
+
+## What to produce
+
+For each operation in the element:
+1. Tests first — write tests derived from the operation's declared inputs, outputs, errors,
+   and any example/edge cases in the spec. Tests must be runnable and specific to the spec values.
+2. Implementation — write the minimal code that satisfies the spec contract. No extra abstractions,
+   no error handling beyond what's declared, no feature flags.
+
+## Rules
+
+- Implement exactly what the spec declares. Nothing more.
+- Every output field declared in an operation must be present in the implementation.
+- Every error declared in `raises` must have a corresponding error-return path.
+- Integration tests (flows, interactions) must run against live infrastructure — no internal mocks.
+- External third-party APIs (integrations) may be mocked with test credentials or sandbox environments.
+- If the spec is ambiguous on a decision the architecture block doesn't resolve, report it as
+  an `architecture_conflict` instead of guessing. Do not write files on conflict.
+
+## Output
+
+Write files to the paths implied by the module's `packaging.runtime` and the project's source structure.
+Report: files written, tests passing, or architecture_conflict with the specific ambiguity.
+```
+
+### Tracking
+
+After each subagent completes, update `workbench/build-plan.md`:
+- Mark task as `done` with files written.
+- On failure: increment attempts, note failure reason.
+
+## Step 4 — Failure Handling
+
+On subagent failure:
+1. **Attempt 1 retry**: Re-dispatch the same subagent with the error reason appended to the prompt.
+2. **Attempt 2 retry**: Re-dispatch with explicit guidance targeting the reported error.
+3. **After 2 retries**: Surface to the human with the full failure reason. Ask whether to skip, fix the spec, or provide manual guidance.
+
+On `architecture_conflict`:
+- Do not retry. Surface immediately with the specific ambiguity.
+- Ask the human to resolve it (add to `workbench/discovery.md` or update relevant spec files), then re-dispatch.
+
+## Step 5 — Completion
+
+When all tasks are `done`:
+1. Run `forge validate` to confirm spec is still clean.
+2. Provide a summary: modules implemented, files written, any skipped tasks.
+3. Recommend running `forge-validate` to verify behavioral correctness.
+
+## Key Constraints
+
+- Do not dispatch subagents until `workbench/build-plan.md` is written and human-confirmed.
+- Subagents never read other subagents' output files — isolation is strict.
+- Orchestrator never writes implementation code directly — only subagents do.
+- `forge validate` must pass before dispatch and should pass after completion.