Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Extension]: Add Agentstandards Architecture Council

Abierto
#4,720 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
65/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
ai, cli, tooling

Línea de trabajo

This is a request to add a new extension to the Spec Kit catalog. The extension is already built and released. The work involves understanding the Spec Kit extension system, reviewing the provided extension.yml and the proposed catalog entry JSON, and integrating it. Start by reading the repository's documentation on extensions and the catalog structure. The 'extension.yml' manifest and the release package at the provided download URL need to be verified. The task is done when the extension is successfully listed in the catalog and passes any integration tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Extension ID

agentstandards

Extension Name

Agentstandards Architecture Council

Version

0.1.0

Description

Runs a Codex-orchestrated, multi-vendor architecture council with human decisions and a hard gate before Spec Kit task generation.

Author

bbjwz

Repository URL

https://github.com/bbjwz/agentstandards

Download URL

https://github.com/bbjwz/agentstandards/releases/download/v0.1.0/agentstandards-0.1.0.zip

License

MIT

Homepage (optional)

https://github.com/bbjwz/agentstandards

Documentation URL (optional)

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

Changelog URL (optional)

https://github.com/bbjwz/agentstandards/blob/v0.1.0/CHANGELOG.md

Required Spec Kit Version

=1.0.8,<2.0.0

Required Tools (optional)
  • uv - required
  • Codex CLI - required
  • Anthropic API credentials - required only for live council runs
Number of Commands

5

Number of Hooks (optional)

2

Tags

architecture, multi-vendor, governance, codex

Key Features
  • Runs 13 architecture personas across Codex, Anthropic, and every enabled optional provider.
  • Gives each gate a fresh model context, then performs labeled peer-review passes.
  • Pauses for an auditable human decision manifest before final validation.
  • Blocks speckit.tasks until required validators agree or a documented human exception exists.
  • Keeps source code, diffs, tasks, secrets, and implementation artifacts out of external-provider prompts.
Testing Checklist
  • Extension installs successfully via download URL
  • All commands execute without errors
  • Documentation is complete and accurate
  • No security vulnerabilities identified
  • Tested on at least one real project
Submission Requirements
  • Valid extension.yml manifest included
  • README.md with installation and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • All command files exist and are properly formatted
  • Extension ID follows naming conventions (lowercase-with-hyphens)
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 project: A clean Spec Kit 1.0.10 Codex project created specifically for release verification.

Test scenarios:

  1. Installed the v0.1.0 extension archive directly from its release URL.
  2. Verified all five Codex skills and both hooks were installed and discoverable.
  3. Ran the complete 13-persona lifecycle against fake providers, including independent and disclosed passes.
  4. Exercised initialization, status, human-decision pause/resume, validation disagreement, exception handling, and offline gate verification.
  5. Verified provider failure handling, schema repair, secret detection, path allowlisting, transcript hashing, and resumability.
  6. Ran 30 automated tests, Ruff, release metadata checks, and full-history Gitleaks scanning.

Live paid-provider calls are intentionally excluded from ordinary CI.

Example Usage
specify extension add agentstandards \
  --from https://github.com/bbjwz/agentstandards/releases/download/v0.1.0/agentstandards-0.1.0.zip

# In Codex:
# $speckit-agentstandards-init
# $speckit-agentstandards-architect
# Complete the human decision manifest, then:
# $speckit-agentstandards-resume
Proposed Catalog Entry
{
  "agentstandards": {
    "name": "Agentstandards Architecture Council",
    "id": "agentstandards",
    "description": "A Codex-orchestrated, multi-vendor architecture council with human decisions and a hard pre-tasks gate.",
    "author": "bbjwz",
    "version": "0.1.0",
    "download_url": "https://github.com/bbjwz/agentstandards/releases/download/v0.1.0/agentstandards-0.1.0.zip",
    "repository": "https://github.com/bbjwz/agentstandards",
    "homepage": "https://github.com/bbjwz/agentstandards",
    "documentation": "https://github.com/bbjwz/agentstandards/blob/v0.1.0/README.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=1.0.8,<2.0.0",
      "tools": [
        {"name": "uv", "required": true},
        {"name": "codex", "required": true}
      ]
    },
    "provides": {
      "commands": 5,
      "hooks": 2
    },
    "tags": ["architecture", "multi-vendor", "governance", "codex"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-09-24T00:00:00Z",
    "updated_at": "2026-09-24T00:00:00Z"
  }
}
Additional Context

Release v0.1.0 publishes checksums and GitHub build-provenance attestations for every artifact. The project is MIT-licensed and its repository has required CI checks, secret scanning, push protection, private vulnerability reporting, and an explicit security policy.

Lenguaje dominante
Python
Estrellas
138k
Forks
12.4k
Merge medio
3 d 2 h
PR fusionados (30 d)
169

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/spec-kit

Todos los issues de github/spec-kit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.