ac-framework 1.1.0 → 1.2.0

package/LICENSE

@@ -0,0 +1,14 @@
+The MIT License (MIT)
+
+Copyright (c) 2024 OpenSpec Contributors
+Copyright © 2026 AF-Framework Contributors
+
+This project includes modifications and extensions
+based on the OpenSpec framework.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+

package/README.md

@@ -1,24 +1,275 @@
-# AC-framework
-Agentic coding framework, including skills, workflow and more
-
-This framework use OpenSpec as base: MIT License
-
-Copyright (c) 2024 OpenSpec Contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+# AC-Framework 🚀
+
+<p align="center">
+  <img src="https://img.shields.io/badge/OpenSpec-Based-blue?style=for-the-badge&logo=data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMjAiIGhlaWdodD0iMjAiIHZpZXdCb3g9IjAgMCAyMCAyMCIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj48cGF0aCBkPSJNMTAgMkM1LjU4IDIgMiA1LjU4IDIgMTBzMy41OCA4IDggOCA4LTMuNTggOC04LTMuNTgtOC04LTh6bTMuNSA5LjVhMS41IDEuNSAwIDAxLTIgMEwxMCAxMGwxLjUtMS41YTEuNSAxLjUgMCAwMTIgMEwxNCAxMGwtMS41IDEuNXoiIGZpbGw9IndoaXRlIi8+PC9zdmc+" />
+  <img src="https://img.shields.io/badge/Node.js-18+-green?style=for-the-badge&logo=node.js" />
+  <img src="https://img.shields.io/badge/License-MIT-yellow?style=for-the-badge" />
+  <img src="https://img.shields.io/badge/23+-Assistants-purple?style=for-the-badge" />
+</p>
+
+<p align="center">
+  <strong>🤖 Agentic Coding Framework</strong><br>
+  <em>Framework basado en OpenSpec con sistema de Skills mejorado y Skill Routing inteligente para IA</em>
+</p>
+
+---
+
+## 📖 ¿Qué es AC-Framework?
+
+**AC-Framework** (Agentic Coding Framework) es un framework de desarrollo avanzado basado en **OpenSpec** que implementa la metodología **Spec-Driven Development** con mejoras significativas para el contexto y enrutamiento de IA.
+
+### 🎯 Filosofía OpenSpec
+
+AC-Framework adopta y potencia los principios fundamentales de OpenSpec:
+
+- **📋 Todo cambio es un artefacto** - Cada modificación se documenta antes de implementarse
+- **🔄 Desarrollo basado en especificaciones** - El "qué" (specs), "cómo" (design) y "por qué" (proposal) están separados
+- **✅ Trazabilidad total** - Historial completo de decisiones y cambios
+- **🎯 Contexto preservado** - La IA siempre tiene el contexto correcto para cada tarea
+
+
+---
+
+## 🚀 Características Principales
+
+### 🎭 10 Skills Especializadas
+
+Cada skill está diseñada para un propósito específico del ciclo de desarrollo:
+
+| Comando | Skill | Descripción |
+|---------|-------|-------------|
+| `/opsx:onboard` | **Onboarding** | Tutorial guiado para nuevos usuarios |
+| `/opsx:new` | **New Change** | Crear cambio completo con proposal, specs, design y tasks |
+| `/opsx:continue` | **Continue Change** | Retomar un cambio existente |
+| `/opsx:ff` | **Fast Forward** | Crear todos los artefactos rápidamente |
+| `/opsx:apply` | **Apply Change** | Implementar tareas del cambio actual |
+| `/opsx:verify` | **Verify Change** | Verificar completitud y calidad |
+| `/opsx:archive` | **Archive Change** | Archivar cambio completado |
+| `/opsx:bulk-archive` | **Bulk Archive** | Archivar múltiples cambios |
+| `/opsx:sync` | **Sync Specs** | Sincronizar specs delta a principales |
+| `/opsx:explore` | **Explore** | Modo exploración (pensar antes de actuar) |
+
+### 🧠 Sistema de Skill Routing
+
+El **Skill Routing** es una innovación clave de AC-Framework que proporciona:
+
+- **🎯 Contexto Contextualizado**: Cada skill recibe solo el contexto relevante para su función
+- **🔄 Enrutamiento Automático**: La IA sabe qué skill usar según el estado del proyecto
+- **📊 Preservación de Estado**: El contexto se mantiene coherente entre skills
+- **⚡ Optimización**: Menor consumo de tokens al enviar solo contexto necesario
+
+### 🌐 Multi-Asistente Sincronizado
+
+**23+ Asistentes de IA soportados** con el mismo conjunto de skills:
+
+#### IDEs y Editores
+- 📝 **Cursor** - IDE con IA integrada
+- 🌊 **Windsurf** - Editor AI-first
+- 🎯 **Trae** - IDE con asistente IA
+- 💎 **Gemini** - Google AI Studio
+
+#### Herramientas CLI
+- 🎩 **Claude Code** - CLI de Anthropic
+- 🤖 **Codex** - OpenAI Codex CLI
+- 👤 **CodeBuddy** - Asistente CLI
+
+#### Extensiones VS Code
+- 🔌 **Continue.dev** - Extensión de código abierto
+- 🦅 **Cline** - Asistente de codificación
+- 🦘 **Roo Code** - Fork de Cline
+- 🐙 **GitHub Copilot** - Asistente de GitHub
+
+#### Cloud y Otros
+- ☁️ **Amazon Q** - AWS AI Assistant
+- 🐉 **Qwen** - Alibaba Cloud
+- ⚡ **Augment** - Augment Code
+- 🔧 **OpenCode** - Framework de código abierto
+- Y **13 asistentes más...**
+
+---
+
+## 📦 Instalación
+
+### Instalación Global
+
+```bash
+# Instalar el CLI de AC-Framework
+npm install -g ac-framework
+
+# Inicializar en tu proyecto
+acfm init
+```
+
+### Instalación Local
+
+```bash
+# Instalar como dependencia de desarrollo
+npm install --save-dev ac-framework
+
+# Ejecutar el inicializador
+npx acfm init
+```
+
+### Uso del CLI
+
+```bash
+acfm [opciones] [comando]
+
+Comandos:
+  init [options]  Inicializar AC-Framework en el proyecto
+  help [command]  Mostrar ayuda de un comando
+
+Opciones:
+  -V, --version   Mostrar versión
+  -h, --help      Mostrar ayuda
+```
+
+---
+
+## 🏗️ Estructura de Proyecto OpenSpec
+
+Cuando inicializas AC-Framework, se crea la siguiente estructura:
+
+```
+openspec/
+├── config.yaml                    # Configuración global
+├── changes/                       # Cambios activos
+│   ├── {nombre-cambio}/
+│   │   ├── proposal.md           # 📝 Por QUÉ hacer el cambio
+│   │   ├── design.md             # 🎨 CÓMO se implementará
+│   │   ├── tasks.md              # ✅ Lista de tareas
+│   │   └── specs/
+│   │       └── {capability}/
+│   │           └── spec.md       # 📋 QUÉ cambia
+│   └── archive/                   # 📦 Cambios completados
+│       └── YYYY-MM-DD-{nombre}/
+└── specs/                         # Especificaciones principales
+    └── {capability}/
+        └── spec.md
+```
+
+### Artefactos de un Cambio
+
+Cada cambio OpenSpec incluye 4 artefactos fundamentales:
+
+1. **📄 proposal.md** - Justificación y contexto del cambio
+2. **🎨 design.md** - Arquitectura y enfoque de implementación
+3. **✅ tasks.md** - Checklist de tareas ejecutables
+4. **📋 specs/** - Especificaciones técnicas detalladas
+
+---
+
+## 🔄 Flujo de Trabajo
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    🧭 EXPLORAR (/opsx:explore)              │
+│           Investigar, entender, planificar                  │
+└─────────────────────────────────────────────────────────────┘
+                              │
+                              ▼
+┌─────────────────────────────────────────────────────────────┐
+│              🆕 NUEVO (/opsx:new) o (/opsx:ff)              │
+│  • proposal.md    ← Justificación                          │
+│  • specs/         ← Requisitos                             │
+│  • design.md      ← Arquitectura                           │
+│  • tasks.md       ← Plan de trabajo                        │
+└─────────────────────────────────────────────────────────────┘
+                              │
+                              ▼
+┌─────────────────────────────────────────────────────────────┐
+│                   🔨 APLICAR (/opsx:apply)                  │
+│           Implementar y marcar tareas completadas           │
+└─────────────────────────────────────────────────────────────┘
+                              │
+                              ▼
+┌─────────────────────────────────────────────────────────────┐
+│                  ✔️ VERIFICAR (/opsx:verify)                │
+│          Revisar calidad y completitud                      │
+└─────────────────────────────────────────────────────────────┘
+                              │
+                              ▼ (opcional)
+┌─────────────────────────────────────────────────────────────┐
+│                   🔄 SINCRONIZAR (/opsx:sync)               │
+│          Actualizar documentación principal                 │
+└─────────────────────────────────────────────────────────────┘
+                              │
+                              ▼
+┌─────────────────────────────────────────────────────────────┐
+│                  📦 ARCHIVAR (/opsx:archive)                │
+│         Mover a archivo con fecha                           │
+└─────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## 🛠️ Uso Rápido
+
+### 1. Inicializar Proyecto
+
+```bash
+acfm init
+```
+
+Selecciona los asistentes que usarás (puedes elegir múltiples):
+
+```
+? ¿Qué módulos deseas instalar? (Selecciona con espacio)
+ ❯◉ Cursor IDE
+  ◯ Claude Code
+  ◯ Continue.dev
+  ◉ GitHub Copilot
+  ◯ ...
+```
+
+### 2. Crear un Cambio
+
+```
+/opsx:new feature-user-authentication
+```
+
+Esto crea:
+- `openspec/changes/feature-user-authentication/proposal.md`
+- `openspec/changes/feature-user-authentication/design.md`
+- `openspec/changes/feature-user-authentication/tasks.md`
+- `openspec/changes/feature-user-authentication/specs/auth/spec.md`
+
+### 3. Implementar
+
+```
+/opsx:apply
+```
+
+La IA implementará las tareas del archivo `tasks.md`, marcándolas como completadas.
+
+### 4. Verificar y Archivar
+
+```
+/opsx:verify
+/opsx:archive
+```
+
+---
+
+```bash
+# Las skills están en:
+framework/.{asistente}/skills/openspec-{nombre}/SKILL.md
+
+# Ejemplo:
+framework/.cursor/skills/openspec-new-change/SKILL.md
+framework/.claude/skills/openspec-new-change/SKILL.md
+framework/.opencode/skills/openspec-new-change/SKILL.md
+```
+
+---
+
+## 📝 Licencia
+
+MIT © AC-Framework Team
+
+---
+
+<p align="center">
+  <strong>🚀 Desarrollo asistido por IA, estandarizado y potenciado</strong><br>
+  <em>Trabaja con cualquier asistente, mantén el mismo flujo de trabajo</em>
+</p>

package/framework/.agent/skills/skill-writer/SKILL.md

@@ -0,0 +1,385 @@
+---
+name: skill-writer
+description: Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.
+---
+
+# Skill Writer
+
+This Skill helps you create well-structured Agent Skills for Claude Code that follow best practices and validation requirements.
+
+## When to use this Skill
+
+Use this Skill when:
+- Creating a new Agent Skill
+- Writing or updating SKILL.md files
+- Designing skill structure and frontmatter
+- Troubleshooting skill discovery issues
+- Converting existing prompts or workflows into Skills
+
+## Instructions
+
+### Step 1: Determine Skill scope
+
+First, understand what the Skill should do:
+
+1. **Ask clarifying questions**:
+   - What specific capability should this Skill provide?
+   - When should Claude use this Skill?
+   - What tools or resources does it need?
+   - Is this for personal use or team sharing?
+
+2. **Keep it focused**: One Skill = one capability
+   - Good: "PDF form filling", "Excel data analysis"
+   - Too broad: "Document processing", "Data tools"
+
+### Step 2: Choose Skill location
+
+Determine where to create the Skill:
+
+**Personal Skills** (`~/.claude/skills/`):
+- Individual workflows and preferences
+- Experimental Skills
+- Personal productivity tools
+
+**Project Skills** (`.claude/skills/`):
+- Team workflows and conventions
+- Project-specific expertise
+- Shared utilities (committed to git)
+
+### Step 3: Create Skill structure
+
+Create the directory and files:
+
+```bash
+# Personal
+mkdir -p ~/.claude/skills/skill-name
+
+# Project
+mkdir -p .claude/skills/skill-name
+```
+
+For multi-file Skills:
+```
+skill-name/
+├── SKILL.md (required)
+├── reference.md (optional)
+├── examples.md (optional)
+├── scripts/
+│   └── helper.py (optional)
+└── templates/
+    └── template.txt (optional)
+```
+
+### Step 4: Write SKILL.md frontmatter
+
+Create YAML frontmatter with required fields:
+
+```yaml
+---
+name: skill-name
+description: Brief description of what this does and when to use it
+---
+```
+
+**Field requirements**:
+
+- **name**:
+  - Lowercase letters, numbers, hyphens only
+  - Max 64 characters
+  - Must match directory name
+  - Good: `pdf-processor`, `git-commit-helper`
+  - Bad: `PDF_Processor`, `Git Commits!`
+
+- **description**:
+  - Max 1024 characters
+  - Include BOTH what it does AND when to use it
+  - Use specific trigger words users would say
+  - Mention file types, operations, and context
+
+**Optional frontmatter fields**:
+
+- **allowed-tools**: Restrict tool access (comma-separated list)
+  ```yaml
+  allowed-tools: Read, Grep, Glob
+  ```
+  Use for:
+  - Read-only Skills
+  - Security-sensitive workflows
+  - Limited-scope operations
+
+### Step 5: Write effective descriptions
+
+The description is critical for Claude to discover your Skill.
+
+**Formula**: `[What it does] + [When to use it] + [Key triggers]`
+
+**Examples**:
+
+✅ **Good**:
+```yaml
+description: Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.
+```
+
+✅ **Good**:
+```yaml
+description: Analyze Excel spreadsheets, create pivot tables, and generate charts. Use when working with Excel files, spreadsheets, or analyzing tabular data in .xlsx format.
+```
+
+❌ **Too vague**:
+```yaml
+description: Helps with documents
+description: For data analysis
+```
+
+**Tips**:
+- Include specific file extensions (.pdf, .xlsx, .json)
+- Mention common user phrases ("analyze", "extract", "generate")
+- List concrete operations (not generic verbs)
+- Add context clues ("Use when...", "For...")
+
+### Step 6: Structure the Skill content
+
+Use clear Markdown sections:
+
+```markdown
+# Skill Name
+
+Brief overview of what this Skill does.
+
+## Quick start
+
+Provide a simple example to get started immediately.
+
+## Instructions
+
+Step-by-step guidance for Claude:
+1. First step with clear action
+2. Second step with expected outcome
+3. Handle edge cases
+
+## Examples
+
+Show concrete usage examples with code or commands.
+
+## Best practices
+
+- Key conventions to follow
+- Common pitfalls to avoid
+- When to use vs. not use
+
+## Requirements
+
+List any dependencies or prerequisites:
+```bash
+pip install package-name
+```
+
+## Advanced usage
+
+For complex scenarios, see [reference.md](reference.md).
+```
+
+### Step 7: Add supporting files (optional)
+
+Create additional files for progressive disclosure:
+
+**reference.md**: Detailed API docs, advanced options
+**examples.md**: Extended examples and use cases
+**scripts/**: Helper scripts and utilities
+**templates/**: File templates or boilerplate
+
+Reference them from SKILL.md:
+```markdown
+For advanced usage, see [reference.md](reference.md).
+
+Run the helper script:
+\`\`\`bash
+python scripts/helper.py input.txt
+\`\`\`
+```
+
+### Step 8: Validate the Skill
+
+Check these requirements:
+
+✅ **File structure**:
+- [ ] SKILL.md exists in correct location
+- [ ] Directory name matches frontmatter `name`
+
+✅ **YAML frontmatter**:
+- [ ] Opening `---` on line 1
+- [ ] Closing `---` before content
+- [ ] Valid YAML (no tabs, correct indentation)
+- [ ] `name` follows naming rules
+- [ ] `description` is specific and < 1024 chars
+
+✅ **Content quality**:
+- [ ] Clear instructions for Claude
+- [ ] Concrete examples provided
+- [ ] Edge cases handled
+- [ ] Dependencies listed (if any)
+
+✅ **Testing**:
+- [ ] Description matches user questions
+- [ ] Skill activates on relevant queries
+- [ ] Instructions are clear and actionable
+
+### Step 9: Test the Skill
+
+1. **Restart Claude Code** (if running) to load the Skill
+
+2. **Ask relevant questions** that match the description:
+   ```
+   Can you help me extract text from this PDF?
+   ```
+
+3. **Verify activation**: Claude should use the Skill automatically
+
+4. **Check behavior**: Confirm Claude follows the instructions correctly
+
+### Step 10: Debug if needed
+
+If Claude doesn't use the Skill:
+
+1. **Make description more specific**:
+   - Add trigger words
+   - Include file types
+   - Mention common user phrases
+
+2. **Check file location**:
+   ```bash
+   ls ~/.claude/skills/skill-name/SKILL.md
+   ls .claude/skills/skill-name/SKILL.md
+   ```
+
+3. **Validate YAML**:
+   ```bash
+   cat SKILL.md | head -n 10
+   ```
+
+4. **Run debug mode**:
+   ```bash
+   claude --debug
+   ```
+
+## Common patterns
+
+### Read-only Skill
+
+```yaml
+---
+name: code-reader
+description: Read and analyze code without making changes. Use for code review, understanding codebases, or documentation.
+allowed-tools: Read, Grep, Glob
+---
+```
+
+### Script-based Skill
+
+```yaml
+---
+name: data-processor
+description: Process CSV and JSON data files with Python scripts. Use when analyzing data files or transforming datasets.
+---
+
+# Data Processor
+
+## Instructions
+
+1. Use the processing script:
+\`\`\`bash
+python scripts/process.py input.csv --output results.json
+\`\`\`
+
+2. Validate output with:
+\`\`\`bash
+python scripts/validate.py results.json
+\`\`\`
+```
+
+### Multi-file Skill with progressive disclosure
+
+```yaml
+---
+name: api-designer
+description: Design REST APIs following best practices. Use when creating API endpoints, designing routes, or planning API architecture.
+---
+
+# API Designer
+
+Quick start: See [examples.md](examples.md)
+
+Detailed reference: See [reference.md](reference.md)
+
+## Instructions
+
+1. Gather requirements
+2. Design endpoints (see examples.md)
+3. Document with OpenAPI spec
+4. Review against best practices (see reference.md)
+```
+
+## Best practices for Skill authors
+
+1. **One Skill, one purpose**: Don't create mega-Skills
+2. **Specific descriptions**: Include trigger words users will say
+3. **Clear instructions**: Write for Claude, not humans
+4. **Concrete examples**: Show real code, not pseudocode
+5. **List dependencies**: Mention required packages in description
+6. **Test with teammates**: Verify activation and clarity
+7. **Version your Skills**: Document changes in content
+8. **Use progressive disclosure**: Put advanced details in separate files
+
+## Validation checklist
+
+Before finalizing a Skill, verify:
+
+- [ ] Name is lowercase, hyphens only, max 64 chars
+- [ ] Description is specific and < 1024 chars
+- [ ] Description includes "what" and "when"
+- [ ] YAML frontmatter is valid
+- [ ] Instructions are step-by-step
+- [ ] Examples are concrete and realistic
+- [ ] Dependencies are documented
+- [ ] File paths use forward slashes
+- [ ] Skill activates on relevant queries
+- [ ] Claude follows instructions correctly
+
+## Troubleshooting
+
+**Skill doesn't activate**:
+- Make description more specific with trigger words
+- Include file types and operations in description
+- Add "Use when..." clause with user phrases
+
+**Multiple Skills conflict**:
+- Make descriptions more distinct
+- Use different trigger words
+- Narrow the scope of each Skill
+
+**Skill has errors**:
+- Check YAML syntax (no tabs, proper indentation)
+- Verify file paths (use forward slashes)
+- Ensure scripts have execute permissions
+- List all dependencies
+
+## Examples
+
+See the documentation for complete examples:
+- Simple single-file Skill (commit-helper)
+- Skill with tool permissions (code-reviewer)
+- Multi-file Skill (pdf-processing)
+
+## Output format
+
+When creating a Skill, I will:
+
+1. Ask clarifying questions about scope and requirements
+2. Suggest a Skill name and location
+3. Create the SKILL.md file with proper frontmatter
+4. Include clear instructions and examples
+5. Add supporting files if needed
+6. Provide testing instructions
+7. Validate against all requirements
+
+The result will be a complete, working Skill that follows all best practices and validation rules.