[Bundle]: Add Agentstandards Multi-Vendor Architecture

[bbjwz]

Bundle ID

agentstandards

Bundle Name

Agentstandards Multi-Vendor Architecture

Version

0.1.1

Role or Team

architecture-governance

Description

Installs a Codex-orchestrated, multi-vendor architecture council, its hard task gate, and the supporting Spec Kit workflow.

Author

bbjwz

Repository URL

https://github.com/bbjwz/agentstandards

Download URL

https://github.com/bbjwz/agentstandards/releases/download/v0.1.1/agentstandards-bundle-0.1.1.zip

Documentation URL

https://github.com/bbjwz/agentstandards/blob/v0.1.1/bundles/agentstandards/README.md

License

MIT

Required Spec Kit Version

=1.0.8,<2.0.0

Integration Target (optional)

codex

Components Provided

• extensions: agentstandards@0.1.1
• presets: agentstandards-gate@0.1.1
• workflows: agentstandards-architecture@0.1.1
• steps: None

Required Component Catalogs

• Extensions: https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.1/catalogs/extensions.json
• Presets: https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.1/catalogs/presets.json
• Workflows: https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.1/catalogs/workflows.json

Tags

architecture, governance, multi-vendor, codex

Key Features

• Installs the complete Agentstandards extension, task-gate preset, and architecture workflow as one pinned stack.
• Runs 13 architecture roles across Codex, Anthropic, and all enabled optional vendors.
• Uses fresh model instances for every gate and labels peer work for disclosed review passes.
• Pauses for human decisions and records their rationale before final validation.
• Keeps task generation blocked until the aggregate architecture gate is READY.

Testing Checklist

• Validation succeeds with specify bundle validate --path <bundle-directory>
• Build succeeds with specify bundle build --path <bundle-directory> and produces the submitted artifact
• Bundle installs successfully from the built artifact
• The submitted distribution path was tested end to end, including bundle-ID installation from an install-allowed catalog when a catalog entry is proposed
• Installation was tested in a clean Spec Kit project
• Required component catalogs are documented and were included in testing, or no extra catalogs are required
• Documentation is complete and accurate

Submission Requirements

• Valid bundle.yml manifest included
• README.md explains the bundle's intended role, installed components, and installation steps
• LICENSE file included
• GitHub release created with version tag
• Bundle ID matches the manifest and follows naming conventions
• Every extension, preset, workflow, and step reference is pinned where the manifest requires a version

Testing Details

Tested on:

• macOS with Spec Kit 1.0.8 and 1.0.10
• GitHub Actions on Python 3.11 and 3.14

Test projects: Clean Spec Kit Codex projects created specifically for release verification.

Test scenarios:

1. Validated bundles/agentstandards with the official Spec Kit bundle validator.
2. Built it with specify bundle build --path bundles/agentstandards.
3. Downloaded the submitted v0.1.1 bundle asset and installed it in a clean project after registering the three required component catalogs.
4. Registered the public v0.1.1 bundle catalog with install-allowed policy and installed agentstandards by bundle ID in another clean Spec Kit 1.0.10 project.
5. Verified Spec Kit reports the bundle at v0.1.1 with all three v0.1.1 components, the Codex integration target, five extension commands, and two hooks.
6. Ran 31 automated tests, Ruff, release metadata checks, full-history secret scanning, Python 3.11/3.14 CI, and Spec Kit 1.0.8/1.0.10 clean-install CI.

The monorepo release builder uses a distinct agentstandards-bundle-0.1.1.zip filename to avoid colliding with the extension archive in the same GitHub release. Its bundle payload is the validated manifest and README plus the required top-level MIT LICENSE. Both the official CLI-built archive and the submitted release archive installed successfully.

Example Usage

specify extension catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.1/catalogs/extensions.json \
  --name agentstandards --install-allowed

specify preset catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.1/catalogs/presets.json \
  --name agentstandards --install-allowed

specify workflow catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.1/catalogs/workflows.json \
  --name agentstandards

curl --fail --location \
  https://github.com/bbjwz/agentstandards/releases/download/v0.1.1/agentstandards-bundle-0.1.1.zip \
  --output agentstandards-bundle-0.1.1.zip

specify bundle install ./agentstandards-bundle-0.1.1.zip --integration codex

Proposed Catalog Entry

{
  "agentstandards": {
    "name": "Agentstandards Multi-Vendor Architecture",
    "id": "agentstandards",
    "version": "0.1.1",
    "role": "architecture-governance",
    "description": "Installs a Codex-orchestrated, multi-vendor architecture council, its hard task gate, and the supporting Spec Kit workflow.",
    "author": "bbjwz",
    "license": "MIT",
    "download_url": "https://github.com/bbjwz/agentstandards/releases/download/v0.1.1/agentstandards-bundle-0.1.1.zip",
    "repository": "https://github.com/bbjwz/agentstandards",
    "requires": {
      "speckit_version": ">=1.0.8,<2.0.0"
    },
    "provides": {
      "extensions": 1,
      "presets": 1,
      "steps": 0,
      "workflows": 1
    },
    "tags": ["architecture", "governance", "multi-vendor", "codex"],
    "verified": false
  }
}

Additional Context

Release v0.1.1 publishes SHA-256 checksums and GitHub build-provenance attestations for every artifact. Live provider calls are explicit only; normal CI and bundle installation are offline from model providers.

SHA-256

0306cdc780f4107e6702cd25680afede8acea866dfbb0ba81f9ea9c8f960a9dc

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Validation failed for this submission. The artifact download itself completed with HTTP 200, and the downloaded archive digest was f15baa79a01467d2fef9b5fac1971cf73c9e34d0b114d0054a714c0e7dce8542.

Failed checks:

• Manifest metadata mismatch: bundles/agentstandards/bundle.yml describes the bundle as “Install the Agentstandards council, task gate, and Spec Kit architecture workflow together.”, which does not match the submitted Description (“Installs a Codex-orchestrated, multi-vendor architecture council, its hard task gate, and the supporting Spec Kit workflow.”). Update the submission or manifest so they match exactly.
• Integration target not represented in the manifest: the submission specifies codex, but bundle.yml does not declare or otherwise match that integration target. Add the target to the manifest if supported, or correct the submission.
• Documentation URL is incomplete: bundles/agentstandards/README.md identifies the components and required catalogs but does not provide the installation commands/steps; it points readers to the repository root README instead. Make the submitted documentation URL self-contained, including the required catalog setup and bundle installation steps.

The release tag and exact ZIP asset were present, the repository contained bundle.yml, README.md, and LICENSE, and the proposed catalog entry had valid counts, tags, and verified: false. Please correct the failed items and submit again.

Workflow run: https://github.com/github/spec-kit/actions/runs/36000313833

Generated by 📦 Add Community Bundle from Issue Submission for #4722 · copilot · gpt52codex · 2.36 AIC · ⌖ 6.81 AIC · ⊞ 24K · ◷

[KSchlobohm]

Based on the Copilot reviewer’s findings, please align the submitted description with bundle.yml, declare or remove the codex integration target, and make the bundle README self-contained with the required catalog setup and installation steps. Maintainers will review the updated revision.

[bbjwz]

Published and verified v0.1.1, then updated the submission body with the corrected manifest metadata, documentation URL, download URL, component versions, installation example, and SHA-256.

The revision addresses every reported item:

• bundle.yml, the companion catalog, and the submitted Description now use the same exact text.

• bundle.yml declares the supported top-level integration target as integration.id: codex.

• The bundle-scoped README is self-contained and includes all three required component catalog commands, bundle-catalog installation, direct artifact installation, prerequisites, and post-install usage.

• A clean Spec Kit 1.0.10 catalog-backed install resolved and installed the bundle and all three v0.1.1 components.

• Release: https://github.com/bbjwz/agentstandards/releases/tag/v0.1.1

• Corrective PR: Address Spec Kit catalog review feedback bbjwz/agentstandards#11

• Bundle README: https://github.com/bbjwz/agentstandards/blob/v0.1.1/bundles/agentstandards/README.md

Ready for maintainer re-review.