@cristiancorreau/forge 2.1.0

package/CHANGELOG.md

@@ -0,0 +1,228 @@
+# Changelog
+
+Todos los cambios notables de forge se documentan en este archivo.
+
+Formato: [Keep a Changelog](https://keepachangelog.com/es/1.0.0/)  
+Versioning: [Semantic Versioning](https://semver.org/lang/es/)
+
+---
+
+## [2.0.1] — 2026-05-18
+
+### Agregado
+- `forge wiki` subcomando: `status`, `ingest`, `query`, `lint` (F1-F01)
+- 45 tests nuevos: validador de project.yaml, migrador v1→v2, forge-generate-all, pre-bash-check
+- Copyright headers en 7 scripts principales (Apache 2.0, SocialWeb 2026)
+- `vscode-extension/forge-agent-framework-0.5.0.vsix` empaquetada y lista para instalar
+
+### Total: 509 tests pasando
+
+---
+
+## [2.0.0] — 2026-05-18
+
+### Agregado — Forge v2 Fase 3 (liberación pública)
+
+#### Limpieza (F3-01)
+- `LICENSE`: Apache 2.0, Copyright 2026 SocialWeb
+- `docs/RELEASE-CHECKLIST.md`: checklist de liberación pública (seguridad, técnico, legal, operativo)
+- Anonimización de referencias internas en `docs/plan/`: clientes reales → `Cliente-Media`, `Cliente-ONG`, etc.; proyectos internos → `proyecto-alpha`, `proyecto-beta`; `Bienes Nacionales` → `organismo-publico`
+
+#### README y documentación (F3-02)
+- README reescrito para público general: posicionamiento honesto, tabla comparativa vs cc-sdd/Bridle/wshobson, quick start de 4 pasos, sin referencias a clientes
+
+#### Extensión VS Code (F3-04)
+- Versión `0.2.1` → `0.5.0` (alineada con forge pre-milestone)
+- 3 nuevos comandos: `forge: Generate All Runtimes`, `forge: Validate project.yaml`, `forge: Migrate project.yaml to v2`
+- Handlers en `extension.ts` con confirmación para migración destructiva
+
+#### Artículos (F3-05)
+- `docs/content/linkedin-articles/`: 3 borradores listos para publicar
+  - "Por qué los agentes de IA necesitan un harness, no solo prompts"
+  - "Las cinco capas de un kit de desarrollo agéntico"
+  - "Cómo usamos agentes para enseñar gestión de proyectos de software"
+
+### Convenciones
+- Versión `2.0.0` corresponde a Forge v2 completo (Fases 0–3)
+- Milestone: `v2.0.0` — listo para publicación pública
+
+---
+
+## [0.5.0] — 2026-05-17
+
+### Agregado — Forge v2 Fase 2 (multi-runtime)
+
+#### OpenCode (F2-01/02/03/04)
+- `adapters/opencode/commands/`: 6 comandos adaptados para ejecución serial (plan, work, review, ship, session-start, session-close)
+- `/work` en OpenCode: modo serial equivalente a `--serial` de Claude Code (sin agent teams paralelos)
+- `/review`: veredicto APPROVED/CHANGES_REQUESTED/BLOCKED; escribe `.opencode/review-status.json`
+- `/ship`: usa `vercel deploy` vía CLI en vez de MCP tools
+- `adapters/opencode/HOOKS.md`: tabla de equivalencia hook-por-hook; todos los guardrails se embeben en AGENTS.md
+- `adapters/opencode/generate-agents-md.py`: agrega sección de comandos SDD y reglas de guardrail al AGENTS.md generado
+- `docs/runtimes/opencode.md`: guía completa con diferencias vs Claude Code, agent teams serial, limitaciones
+
+#### Codex CLI (F2-05/06/07/08)
+- `adapters/codex/commands/`: 6 prompt templates para uso con Codex CLI autónomo
+- `adapters/codex/hooks/codex.yaml.tpl`: template de configuración con hooks `onStart`/`onFinish`
+- `adapters/codex/hooks/forge-codex-start.sh`: checks determinísticos de entorno al inicio de sesión
+- `adapters/codex/hooks/forge-codex-finish.sh`: typecheck/lint post-sesión por tipo de archivo
+- `scripts/setup-codex.sh`: instalación automática del entorno Codex en 7 pasos
+- `adapters/codex/generate-codex-config.py`: agrega SDD workflow, production safety rules y branch guard al AGENTS.md
+- `docs/runtimes/codex.md`: guía completa con tabla de diferencias, uso diario y consideraciones de seguridad
+
+#### Kiro (F2-09)
+- `adapters/kiro/generate-steering.py`: agrega flujo SDD en `structure.md`, genera `commands.md` y hook `pre-edit-branch-guard.json`
+- `docs/runtimes/kiro.md`: tablas de equivalencia de conceptos, guía de uso, roadmap para soporte completo
+- `docs/architecture/adr/ADR-002-kiro-support-level.md`: decisión formal de soporte en nivel "monitoring"
+
+#### Capa de traducción (F2-10)
+- `scripts/forge-generate-all.py`: punto de entrada unificado para generar configs de todos los runtimes activos
+- Auto-detección por marcadores de filesystem (`.claude/`, `.opencode/`, `.kiro/`, `AGENTS.md`)
+- Flags: `--runtime`, `--dry-run`, `--force`
+- `templates/project.yaml.tpl`: nueva sección `runtimes.active` con los 4 runtimes soportados
+- `core/schemas/project.schema.json`: validación de la nueva sección `runtimes`
+- `docs/runtimes/README.md`: índice de runtimes con tabla de nivel de soporte
+
+---
+
+## [0.4.0] — 2026-05-17
+
+### Agregado — Forge v2 Fase 1 (core commands + full stack)
+
+#### Memory Layer (Capa 1)
+- Templates `core/templates/claude-md/`: `global.md`, `project.md`, `architecture.rules` (separación 3 capas de CLAUDE.md)
+- Template `core/templates/daily-note.md` con placeholders para `/session-close`
+- Template `core/templates/spec-template.md` con secciones obligatorias (Problem, Non-goals, Acceptance, Compliance, Edge cases)
+- `forge-init.py`: `_install_templates()` crea `docs/daily-notes/`, `docs/specs/_template.md`, `.claude/architecture.rules` automáticamente
+- `generate-claude-md.py`: genera `.claude/architecture.rules` al crear CLAUDE.md si no existe
+- Schema JSON Draft-07: `core/schemas/project.schema.json` para validar `project.yaml` v2
+- Validador: `scripts/forge-validate-project-yaml.py` con flag `--json`, exit 1 en errores
+- Migrador: `scripts/forge-migrate-project-yaml.py` de v1 → v2, soporta `--dry-run` y `--backup`
+- Referencia completa: `docs/project-yaml-v2-reference.md` con tablas por sección
+
+#### Knowledge Layer (Capa 2)
+- Slash command `/plan` (3 modos): crear spec, listar specs, revisar con Planner-Critic
+- Slash command `/work`: lee spec aprobada, propone team según mode, spawna teammates en paralelo
+- Slash command `/review` (F1-B03): multi-agente en standard/enterprise; veredicto APPROVED/CHANGES_REQUESTED/BLOCKED; escribe `.claude/review-status.json` para `/ship`
+- Slash command `/ship`: pipeline 10 pasos, polling max 1/min a Vercel, smoke tests, logs en tiempo real
+
+#### Guardrail Layer (Capa 3)
+- `core/hooks/hooks-registry.yaml`: declarativo por mode (universal/standard/enterprise) y stack
+- `core/hooks/pre-bash-check.py`: bloquea comandos destructivos basado en incidente 2026-04-28
+- `core/hooks/session-start.sh`: verificaciones determinísticas al inicio de sesión (tools, branch, env)
+- `forge-init.py`: lee `hooks-registry.yaml` para instalar hooks según mode del proyecto
+- Nuevas entradas en hooks-registry.yaml para stacks `nextjs-admin` (prisma-safety) y `laravel` (composer-check)
+
+#### Delegation Layer (Capa 4)
+- 7 agentes Tier 1 (`core/agents/`) actualizados con sección `## Forge v2` (spec-first, hooks awareness, scope rules)
+- 7 perfiles Tier 2 actualizados a Forge v2: `hono-drizzle`, `nextjs-admin`, `laravel`, `fastapi`, `astro`, `expo`, `wordpress`
+- `README.md` creado para cada perfil con agentes, cuándo usar, hooks específicos del stack, activación en `project.yaml`
+
+#### Distribution Layer (Capa 5)
+- `manifest.json`: inventario completo de agentes, perfiles, skills, comandos, hooks y schemas
+- `docs/team-install.md`: guía de onboarding de 5 minutos para nuevos desarrolladores
+- `scripts/team-install.sh`: script de instalación automática del equipo
+
+---
+
+## [0.3.0] — 2026-05-17
+
+### Agregado — Forge v2 Fase 0 (session lifecycle + hooks)
+- Slash commands de ciclo de sesión: `/session-start` (3 escenarios, detección automática de branch) y `/session-close` (pipeline de 8 pasos: commit, changeset, GitHub Projects, daily-note, RELEASE-NOTES, rebase + PR)
+- Hook `pre-edit-check.py` (PreToolUse): branch guard en main, detección de debug statements multi-stack (TS/PHP/Python/Ruby), detección de credenciales hardcodeadas
+- Hook `post-turn-check.sh` (Stop): typecheck automático sobre archivos modificados, auto-detección de package manager, soporte `scripts.check` en project.yaml
+- `forge-init.py`: instala hooks en `.claude/hooks/` del proyecto (función `install_hooks()`)
+- `forge-init.py`: `session-start.md` y `session-close.md` se instalan siempre (sin requerir skill activa)
+- `settings.json` ahora incluye configuración de hooks (`PreToolUse`, `Stop`) además de `permissions.allow`
+- Documentación del plan v2: `docs/plan/forge-v2-plan.md`, `docs/plan/forge-v2-implementation.md`
+- Bitácora de fricción: `docs/feedback/friction-log.md` con template y formato estándar
+- Guía de migración: `docs/migration/v1-to-v1.5.md`
+
+### Convenciones
+- Versión "Forge v1.5" del plan de arquitectura = `0.3.0` en semver
+
+---
+
+## [0.2.2] — 2026-05-05
+
+### Agregado
+- Picker TUI de dos paneles en audit: lista navegable (izquierda) + detalle del ítem (derecha)
+- `forge-init.py`: genera CLAUDE.md automáticamente desde el adapter de claude-code
+- `forge-init.py`: inyecta `scope:` en el frontmatter de cada agente desde `agent_paths` en project.yaml
+- `forge-init.py`: genera `.claude/settings.json` con `permissions.allow` según el stack del proyecto
+- Slash commands nuevos: `/new-feature`, `/deploy-check`, `/review` instalados automáticamente por forge-init
+- CLI: opción "Regenerar CLAUDE.md — sin reinstalar agentes" en el submenú de init
+- Extensión VS Code: comando `forge: Regenerate CLAUDE.md` con icono en el panel lateral
+- `generate-claude-md.py`: tabla "Agentes y su scope" en el CLAUDE.md generado
+- `generate-claude-md.py`: soporte a `--force` para bypass del prompt interactivo
+- `project.yaml.tpl`: sección `agent_paths` con keys api, frontend, admin, mobile, scanner
+- Extensión VS Code: `showOpportunitiesPicker()` multi-select QuickPick con `canPickMany: true`
+- Extensión VS Code: context states `forge.installed` / `forge.active` vía `setContext`
+- Extensión VS Code: `AuditOpportunity` interface para parseo estructurado del JSON de audit
+
+### Cambiado
+- Picker de oportunidades: reemplaza lista estática + prompt de texto por TUI de dos paneles
+- CLI `menu_init()`: descripciones actualizadas mencionando settings.json y slash commands
+- `ForgeActionsProvider`: incluye "Regenerate CLAUDE.md" en el panel de acciones
+- Fallback a `_simple_opp_picker` en Windows, terminal <60 cols o modo no-TTY/CI
+
+---
+
+## [0.2.1] — 2026-05-04
+
+### Agregado
+- Profile `laravel`: agentes `api-engineer`, `fullstack-engineer`, `migration-specialist` con ruta completa L6→L13
+- Profile `wordpress`: agentes `wp-engineer`, `divi-engineer`, `elementor-engineer` (FSE, Divi 5, Elementor Pro)
+- `scripts/forge-add-opportunities.py`: aplica profiles/skills seleccionados a `project.yaml` vía CLI o VS Code
+- Filtrado inteligente de oportunidades en audit por stack declarado (`_PROFILE_RELEVANCE`)
+- Picker interactivo numerado en terminal para seleccionar y aplicar oportunidades
+- Catálogos `_SKILL_INFO` y `_PROFILE_INFO` con descripción y trigger por item
+- Agentes especialistas: `forge-init-specialist`, `forge-audit-specialist`, `forge-catalog-specialist`
+- VS Code: `showOpportunitiesPicker()` con QuickPick multi-select
+- VS Code: vistas `forgeActionsView`, `forgeProjectView`, `forgeAgentsView` con `viewsWelcome`
+- VS Code: campo `publisher: "socialwebcl"` en `package.json`
+- GitHub Actions: workflow `tests.yml` con matrix Python 3.9/3.11/3.12
+- Campo `last_verified` en agentes de terceros (Divi, Elementor) con check de expiración en audit
+- Sección de extensión VS Code en README y `docs/guide.md`
+
+### Corregido
+- Windows: `ModuleNotFoundError: No module named 'termios'` reemplazado por mensaje orientativo con exit limpio
+- URL del submodule en README: `socialweb-cl` → `socialwebcl` (sin guión)
+- Instrucciones de `git submodule update --init --recursive` para colaboradores nuevos
+- Campo `summary` ausente en salida JSON de `forge-audit.py` (generaba falsa seguridad en CI)
+- Flags `--forge` y `--only` declarados en docs pero no implementados en `forge-audit.py`
+- 4 profiles sin documentar en `agent-standard.md` (django, go-gin, sveltekit, vuenuxt)
+- `codex.md` con convención no verificada en spec de Codex CLI → eliminado, adapter simplificado
+- Referencias a `aitmpl.com` en código activo → removidas
+- Wizard: 4 brechas de UX para usuario nuevo (mensajes de error, terminología)
+- `pbcopy`/`open` macOS-only → reemplazado por alternativas multiplataforma
+- Extensión VS Code: sin documentación ni instrucciones de instalación → documentada con VSIX
+
+### Cambiado
+- Audit terminal: agentes OK colapsados en una línea por tier (reduce scroll)
+- Oportunidades en audit: cards con descripción, agentes/trigger y selección numerada integrada
+- Extensión VS Code: 624 → 1071 líneas (opportunity picker, estados gestionados)
+- `forge-audit.py`: 557 → 855 líneas (filtrado, catálogos, UI)
+- Tests: 358 → 464 casos (contratos JSON, platform compat, VS Code extension, profiles nuevos)
+- Extensión VS Code: `0.1.2` → `0.2.1`
+
+---
+
+## [0.2.0] — 2026-05-03
+
+### Agregado
+- Profiles: `django`, `go-gin`, `sveltekit`, `vuenuxt`, `astro`
+- Skills: `browser-test`, `wiki-ingest`, `wiki-query`, `wiki-lint`
+- Adapter Codex CLI
+- Extensión VS Code (inicial, sin publicar)
+- Wizard interactivo TUI con 10 preguntas guiadas
+- `forge-audit.py` con salida `--json` e integración CI
+- Catálogo curado offline (20 MCP servers, 13 profiles, 5 frameworks)
+
+---
+
+## Convenciones de versioning
+
+- **MAJOR** (`1.0.0`): breaking changes en `project.yaml`, estructura de agentes, o adapters
+- **MINOR** (`0.X.0`): profiles nuevos, skills nuevos, features de CLI o extensión
+- **PATCH** (`0.2.X`): bugfixes, documentación, mejoras de UX sin cambios de estructura

package/LICENSE

@@ -0,0 +1,191 @@
+                                 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 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, as submitted to the 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 Legal Entity on behalf of
+      whom a Contribution has been received by the 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 the 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 any Contributor
+      Contribution 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, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, 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 license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the
+      Work, subject to the terms and conditions of 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 reproducing 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 exemplary 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 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 offer only
+      conditions consistent with the terms of this License, in a
+      manner that is 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 in question.
+
+   Copyright 2026 Cristian Correa
+
+   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.

package/README.md

@@ -0,0 +1,156 @@
+# forge
+
+[![tests](https://github.com/cristiancorreau/forge/actions/workflows/tests.yml/badge.svg)](https://github.com/cristiancorreau/forge/actions/workflows/tests.yml)
+[![version](https://img.shields.io/badge/version-0.5.0-blue)](CHANGELOG.md)
+[![license](https://img.shields.io/badge/license-Apache%202.0-green)](LICENSE)
+
+Framework de desarrollo agéntico para equipos de software. Un `project.yaml` genera la configuración correcta de agentes, skills y reglas para cualquier runtime de IA.
+
+> Los agentes sin harness derivan. Forge es el harness: reglas persistentes, memoria del proyecto, y delegación estructurada desde el primer commit.
+
+---
+
+## Por qué Forge
+
+- **Los agentes olvidan.** Sin memoria y reglas persistentes, cada sesión empieza desde cero. Forge mantiene el contexto entre sesiones.
+- **El contexto se pierde entre archivos.** Un CLAUDE.md plano no sabe qué agente ejecuta qué tarea. Forge separa responsabilidades con agentes especializados por tier.
+- **Cada runtime tiene su formato.** Claude Code, OpenCode, Kiro y Codex CLI esperan archivos distintos. Forge los genera todos desde una sola fuente de verdad.
+- **La calidad baja con el tiempo.** Sin auditoría, los agentes se desactualizan silenciosamente. Forge detecta gaps y ofrece correcciones.
+
+---
+
+## Diferencias con otras herramientas
+
+| Herramienta | Qué hace | Alcance | Runtimes | Hooks | Equipos |
+|-------------|----------|---------|----------|-------|---------|
+| **Forge** | Framework completo: agentes, skills, reglas, auditoría | Proyecto + team | Claude Code, OpenCode, Kiro, Codex CLI | Sí (pre-commit) | Sí (tiers) |
+| `cc-sdd` | Plantillas SDD para Claude Code | Proyecto individual | Claude Code | No | No |
+| `Bridle` | Guardrails para prompts | Prompt-level | Agnóstico | No | No |
+| `wshobson/agents` | Colección de agent files | Proyecto individual | Claude Code | No | No |
+| CLAUDE.md manual | Instrucciones en texto plano | Sesión | Claude Code | No | No |
+
+**Lo que Forge NO es:** no es un modelo de IA, no es un servicio en la nube, no es una plataforma de deployment, no ejecuta agentes por sí solo. Es una capa de configuración y estructura que vive en tu repositorio.
+
+---
+
+## Quick start (5 minutos)
+
+**Requisitos:** Python 3.9+, git, Claude Code (u otro runtime soportado).
+
+```bash
+# 1. Agregar forge al proyecto como submodule
+git submodule add https://github.com/cristiancorreau/forge .agentic
+pip3 install -r .agentic/requirements.txt
+```
+
+```bash
+# 2. Copiar y completar project.yaml
+cp .agentic/templates/project.yaml.tpl project.yaml
+```
+
+Editar `project.yaml` con los datos del proyecto:
+
+```yaml
+project:
+  name: "Mi SaaS"
+  mode: "standard"     # startup | standard | enterprise
+
+stack:
+  backend: "hono"
+  frontend: "nextjs"
+
+agents:
+  active: [orchestrator, test-engineer, docs-writer]
+  profiles: [hono-drizzle, nextjs-admin]
+
+skills:
+  active: [new-feature, security-audit, db-migrate]
+```
+
+```bash
+# 3. Inicializar agentes
+python3 .agentic/scripts/forge-init.py --tool claude-code
+```
+
+```bash
+# 4. Abrir Claude Code y ejecutar
+/session-start
+```
+
+Después del paso 4 verás: agentes instalados en `.claude/agents/`, un `CLAUDE.md` generado con el roster del proyecto, y slash commands disponibles en Claude Code.
+
+---
+
+## Arquitectura — cinco capas
+
+| Capa | Qué hace |
+|------|----------|
+| **Memory** | `project.yaml` como fuente de verdad; wiki de proyecto persistente entre sesiones |
+| **Knowledge** | Agentes especializados (Tier 1/2/3) con scope declarado y reglas no-negociables |
+| **Guardrail** | Compliance by design, hook de pre-commit, auditoría con `forge-audit.py` |
+| **Delegation** | Orquestador que descompone tareas y delega a agentes especializados |
+| **Distribution** | Un solo `project.yaml` genera configs para todos los runtimes soportados |
+
+Documentación completa: [`docs/guide.md`](docs/guide.md)
+
+---
+
+## Runtimes soportados
+
+| Runtime | Soporte | Cómo instalar |
+|---------|---------|---------------|
+| **Claude Code** | Completo (agentes, CLAUDE.md, settings, slash commands) | `--tool claude-code` |
+| **OpenCode** | Serial (AGENTS.md) | `--tool opencode` |
+| **Codex CLI** | Serial (AGENTS.md enriquecido) | `--tool codex` |
+| **Kiro** | Serial (steering files) | `--tool kiro` |
+| **Todos** | Genera los cuatro | `--tool all` |
+
+"Soporte completo" significa integración con hooks, settings.json y slash commands. "Serial" significa generación del archivo de instrucciones sin integración profunda con el runtime.
+
+---
+
+## Perfiles de stack disponibles
+
+15 perfiles listos para usar, declarados en `agents.profiles` del `project.yaml`:
+
+`hono-drizzle` · `nextjs-admin` · `astro` · `expo` · `playwright-crawler`
+`fastapi` · `express` · `rails` · `nestjs` · `django`
+`vuenuxt` · `go-gin` · `sveltekit` · `laravel` · `wordpress`
+
+Cada profile instala uno o más agentes especializados en ese stack. Ver [`profiles/`](profiles/) para el detalle de cada uno.
+
+Para stacks no cubiertos:
+
+```bash
+python3 .agentic/scripts/forge-scaffold-profile.py --name <stack> --engineer <agente>
+```
+
+---
+
+## Contribuir
+
+**Fork + PR.** Para cambios grandes, abre un issue primero.
+
+**Agregar un profile:**
+
+```bash
+python3 .agentic/scripts/forge-scaffold-profile.py --name <stack> --engineer <agente>
+```
+
+El agente debe seguir el estándar en [`docs/agent-standard.md`](docs/agent-standard.md). Agregar el nombre al `CATALOG` en `scripts/aitmpl-search.py` y a los parametrize en `tests/test_profiles.py`.
+
+**Agregar un skill:** Crear `core/skills/<nombre>/SKILL.md` con la estructura estándar. Ver skills existentes como referencia.
+
+**Reportar fricción:** Abre un issue con el formato: _qué intentabas hacer → qué pasó → qué esperabas_. Los friction logs son bienvenidos como issues o PRs directamente en `docs/`.
+
+**Tests antes de cada PR:**
+
+```bash
+python3 -m pytest tests/ -q   # debe pasar al 100%
+```
+
+---
+
+## Licencia
+
+Apache 2.0 — [Cristian Correa](https://github.com/cristiancorreau), 2026.

package/assets/adapters/claude-code/commands/deploy-check.md

@@ -0,0 +1,12 @@
+# deploy-check
+
+Verifica que el proyecto esté listo para deploy y ejecuta los checks previos al push.
+
+Entorno target: $ARGUMENTS (ej: staging, production — vacío para checks generales).
+
+1. Ejecutar lint y tests completos.
+2. Verificar que no hay cambios no commiteados.
+3. Revisar variables de entorno: ¿están todas documentadas en .env.example?
+4. Buscar console.log / print de depuración en los cambios recientes.
+5. Confirmar branch y proveedor de deploy desde project.yaml.
+6. Si el target es production, confirmar que el entorno de staging fue validado primero.

package/assets/adapters/claude-code/commands/new-feature.md

@@ -0,0 +1,11 @@
+# new-feature
+
+Inicia la implementación de una nueva feature siguiendo SDD (Spec-Driven Development).
+
+Argumentos: $ARGUMENTS — nombre de la feature o ruta a la spec existente.
+
+1. Si no existe spec para "$ARGUMENTS" en docs/specs/, crearla primero antes de escribir código.
+2. Leer la spec antes de proponer cualquier implementación.
+3. Proponer el plan de implementación y esperar aprobación explícita.
+4. Implementar con tests junto a la implementación, no al final.
+5. Al terminar, actualizar la spec con las decisiones tomadas durante la implementación.