ostacky 0.6.3 → 0.7.0

package/manifest.json

@@ -1,29 +1,29 @@
 {
-  "version": "0.6.3",
+  "version": "0.7.0",
   "repo": "JaimeHoracio/Ostacky",
-  "tag": "v0.6.3",
+  "tag": "v0.7.0",
   "agents": [
     {
       "name": "ostacky",
       "file": "assets/agents/ostacky.md",
-      "description": "Orquestador con recuperación automática (nunca se congela), ruteo por nivel de impacto, controller MCP con SDK oficial, edición segura con fallback inline, y delegación en OpenSpec + Superpowers",
-      "version": "0.6.3",
-      "sha256": "9cd6f45339b897fe002775a3a54f570e47dedd1784fa474d6cd5113594d1bd85"
+      "description": "Orquestador con recuperación automática (nunca se congela), ruteo por nivel de impacto, controller MCP con SDK oficial, edición segura con fallback inline, y delegación en OpenSpec + Superpowers. v0.7.0: prune de skills obsoletas, lastHandoff, getAvailableTransitions, consecutiveFailures real, mem_session_summary automático al cierre.",
+      "version": "0.7.0",
+      "sha256": "f833e69b6eaa3dfe24de9addf6455b3da55f829b51cba3c7c90c65c69cda34c2"
     }
   ],
   "commands": [
     {
       "name": "install-stack",
       "file": "assets/commands/install-stack.md",
-      "description": "Instala el stack tecnológico del proyecto (CodeGraph, skills, OpenSpec, Engram, Context7, controller MCP con SDK oficial)",
-      "version": "0.6.3",
-      "sha256": "6002a342c3570a33c6f5d4bccf767d0c343b06c4a612cfaa8f744ffedd0de34d"
+      "description": "Instala el stack tecnológico del proyecto (CodeGraph, skills, OpenSpec, Engram, Context7, controller MCP con SDK oficial). v0.7.0: Paso 1.5 controller expandido con verificación post-instalación y troubleshooting.",
+      "version": "0.7.0",
+      "sha256": "c957627dfafabfdb9da2717546b996d1d8856f08a6e4c48caf72c562363b566b"
     },
     {
       "name": "opsx-sync",
       "file": "assets/commands/opsx-sync.md",
       "description": "Sincroniza delta specs del change activo sin inicializar CodeGraph si ya existe índice",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "fe0158478f2ca63b315037a85fc1632b77868532e319af6c7384285441767d64"
     }
   ],
@@ -31,15 +31,15 @@
     {
       "name": "ostacky-controller",
       "file": "assets/mcp/ostacky-controller/",
-      "description": "Máquina de estados persistida con @modelcontextprotocol/server SDK. 20 tools: start_request → discovery → route → execution → sync → done + validate_edit + complete_task + ping + proceed_to_route + abandon integrado",
-      "version": "0.6.3",
-      "sha256": "144fb38a88f81a7657131bf416e59bf668c9eca5fd92a607ea94e32a41e1a36d"
+      "description": "Máquina de estados persistida con @modelcontextprotocol/server SDK. v0.7.0: 22 tools (incluye set_handoff, get_handoff, clear_handoff, get_available_transitions funcional). Bugfixes: consecutiveFailures real, lastHandoff state, defaultChoice persistido. Robustez: degraded mode automático tras 3 fallos, persistence condicional para Nivel 0, prune de skills obsoletas.",
+      "version": "0.7.0",
+      "sha256": "0ec6fa0fc2900c78b884258168309653dea4b77ded3596bb56866f689ec2404c"
     },
     {
       "name": "openspec",
       "file": "assets/mcp/openspec/",
       "description": "MCP server local para OpenSpec - proposal, apply, archive, sync de cambios",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "fa4be28bfc1e75db8f1a037e2580f04a60066c80e8e5934e90e1041020d04609"
     }
   ],
@@ -47,114 +47,107 @@
     {
       "name": "brainstorming",
       "file": "assets/skills/brainstorming/SKILL.md",
-      "description": "Skill unificado de pensamiento con dos modos: creative-design (producción de diseño → transición a writing-plans o openspec-propose) y open-exploration (exploración libre)",
-      "version": "0.6.3",
-      "sha256": "602116fb37e5bc879d1a28815a5928c7bcd9563713907ea278669c1cd81fcde1"
+      "description": "Skill unificado de pensamiento con dos modos: creative-design (producción de diseño → transición a implementación directa o openspec-propose) y open-exploration (exploración libre)",
+      "version": "0.7.0",
+      "sha256": "333810ca63450e8ab795e8c5a58e645101e788d79210ca8ac36e10d11be39585"
     },
     {
       "name": "execution-mode-evaluation",
       "file": "assets/skills/execution-mode-evaluation/SKILL.md",
       "description": "Skill de análisis de modo de ejecución — output reconciliado con controller snapshot contract (recommendation field)",
-      "version": "0.6.3",
-      "sha256": "2e21e69011a0d3cfc2abc4a42b93a616fa9dc7e416955d1f757f6d8e5b35f00b"
-    },
-    {
-      "name": "writing-plans",
-      "file": "assets/skills/writing-plans/SKILL.md",
-      "description": "Skill de planificación de implementación (Superpowers) — execution handoff removido, Ostacky decide modo de ejecución",
-      "version": "0.6.3",
-      "sha256": "9b14903231df96f54da08158c117801b18bba8f5a2e5a0c069854d059e99f294"
+      "version": "0.7.0",
+      "sha256": "edf6fca0af52cce83f8fd08e7db9b3d79cc130b53fca505e90d3fbaf4909338b"
     },
     {
       "name": "tdd",
       "file": "assets/skills/tdd/SKILL.md",
       "description": "Skill de test-driven development (Superpowers)",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "aa412298980b7826165c211145c1b8e9135f68f36247bb3cb96d0a0eae274486"
     },
     {
       "name": "subagent-driven-development",
       "file": "assets/skills/subagent-driven-development/SKILL.md",
       "description": "Skill de ejecución con subagentes (Superpowers) — ejecuta solo después de confirmación del coordinador Ostacky",
-      "version": "0.6.3",
-      "sha256": "6128a6cac60eadc11541ba2d37c3e395c6da3a0167767fbb9b7203b1a2a33ebc"
+      "version": "0.7.0",
+      "sha256": "1a42d714a9a13faf05f0bf7b580e8d837c2e77a5633839542ccce603023419e8"
     },
     {
       "name": "dispatching-parallel-agents",
       "file": "assets/skills/dispatching-parallel-agents/SKILL.md",
       "description": "Skill de dispatch paralelo de agentes (Superpowers)",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "3c8a66d51ae2e719e877d02c3dac32bd804722c3bb9227c258ecae78252a20ab"
     },
     {
       "name": "review",
       "file": "assets/skills/review/SKILL.md",
       "description": "Skill de revisión de código (Superpowers)",
-      "version": "0.6.3",
-      "sha256": "78914222c29306e479d24b09449e1b5a54b5a0482bd5e3e24faace792946a40a"
+      "version": "0.7.0",
+      "sha256": "b19650ed4d1d4d9857a4dd5b7e08e91328a1a1fc9c45bcc2fb600fa9d0213279"
     },
     {
       "name": "receiving-code-review",
       "file": "assets/skills/receiving-code-review/SKILL.md",
       "description": "Skill de recibir y procesar feedback de code review",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "d761e884e71d8d3476ac734d287cae403a4024506a7d12e7361a448217c0a831"
     },
     {
       "name": "openspec-propose",
       "file": "assets/skills/openspec-propose/SKILL.md",
       "description": "Skill de generación de proposal (OpenSpec)",
-      "version": "0.6.3",
-      "sha256": "a184a9e99c06860e1742a100336b1662b329c5d6b319301449ed0fa01545e1ac"
+      "version": "0.7.0",
+      "sha256": "bb59100b9fd3c9f9a1ec6509fa975ec55bf7fc737df4fe73bb3e9bbc217b83f7"
     },
     {
       "name": "openspec-apply-change",
       "file": "assets/skills/openspec-apply-change/SKILL.md",
       "description": "Skill de aplicación de change (OpenSpec)",
-      "version": "0.6.3",
-      "sha256": "b12d80deb4f54f1ceb4792897dbd29fda9b15a71ddd98c30fb6501b085d8eee6"
+      "version": "0.7.0",
+      "sha256": "dfc823bf89fc7505e91ab6dee9c1f004be38a410bd3d88fb67b211b1b6cbb1d0"
     },
     {
       "name": "openspec-archive-change",
       "file": "assets/skills/openspec-archive-change/SKILL.md",
       "description": "Skill de archivo de change (OpenSpec)",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "16e4b561de7747283663fed602e506abf502452c49a8d4b86d7a5539c40f0195"
     },
     {
       "name": "openspec-explore",
       "file": "assets/skills/openspec-explore/SKILL.md",
       "description": "Modo explore para OpenSpec — thinking partner para explorar ideas, investigar problemas y clarificar requisitos antes/durante un cambio",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "37ae4aaf17ea71a395bab6dc4d9d61b9a49d7910f6692535ae8553244c46880b"
     },
     {
       "name": "using-git-worktrees",
       "file": "assets/skills/using-git-worktrees/SKILL.md",
       "description": "Skill de uso de git worktrees para aislamiento de trabajo",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "11afa9123828fc5caa22137aff907cd99c751e99027fbd4c020751110a949281"
     },
     {
       "name": "using-superpowers",
       "file": "assets/skills/using-superpowers/SKILL.md",
       "description": "Skill de orquestación de Superpowers skills",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "7e54536f96d2a379185a10bfc1e970850caa2561b6d8aca7080f0defea0381a4"
     },
     {
       "name": "writing-skills",
       "file": "assets/skills/writing-skills/SKILL.md",
       "description": "Skill de creación y edición de skills",
-      "version": "0.6.3",
+      "version": "0.7.0",
       "sha256": "3d76b906cee518a2b809febb70db95697a35b9f368986bb504b4120c3bfb437a"
     },
     {
       "name": "graceful-degradation",
       "file": "assets/skills/graceful-degradation/SKILL.md",
       "description": "Skill de degradación graceful cuando múltiples tools están indisponibles",
-      "version": "0.6.3",
-      "sha256": "91c52da5c72a866c5df388fc4d4a3dc317bc55be0040081cc7ae04d3c167a026"
+      "version": "0.7.0",
+      "sha256": "e5090e475729f21871bb25bce738000f3616955ed3edb3ba926dd740d3298948"
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "ostacky",
-    "version": "0.6.3",
+    "version": "0.7.0",
     "description": "Instalador interactivo de agentes y comandos para OpenCode",
     "type": "module",
     "bin": {

package/assets/skills/writing-plans/SKILL.md

@@ -1,149 +0,0 @@
----
-name: writing-plans
-description: Use when you have a spec or requirements for a multi-step task, before touching code
----
-
-# Writing Plans
-
-**IMPORTANT:** Engram is an **MCP server**, not a skill. Tools `mem_save`, `mem_search`, `mem_context` are MCP tools. Do NOT use `skill("engram")` — it doesn't exist.
-
-## Overview
-
-Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
-
-Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
-
-**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."
-
-**Context:** If working in an isolated worktree, it should have been created via the `using-git-worktrees` skill at execution time.
-
-**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
-- (User preferences for plan location override this default)
-
-## Pre-Plan: Check Engram for Past Decisions
-
-Before writing the plan, **consult Engram** to avoid repeating past mistakes:
-
-1. `mem_search` with keywords from the feature name and affected modules
-2. Look for:
-   - Previous plans for similar features (avoid duplicating approaches)
-   - Architecture decisions that affect implementation (design patterns, library choices)
-   - Known gotchas or edge cases discovered in similar work
-3. If relevant findings exist, incorporate them into the plan's context section
-
-## Scope Check
-
-If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming (creative-design mode). If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
-
-## File Structure
-
-Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
-
-- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.
-- You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.
-- Files that change together should live together. Split by responsibility, not by technical layer.
-- In existing codebases, follow established patterns. If the codebase uses large files, don't unilaterally restructure - but if a file you're modifying has grown unwieldy, including a split in the plan is reasonable.
-
-This structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.
-
-## Bite-Sized Task Granularity
-
-**Each step is one action (2-5 minutes):**
-- "Write the failing test" - step
-- "Run it to make sure it fails" - step
-- "Implement the minimal code to make the test pass" - step
-- "Run the tests and make sure they pass" - step
-- "Commit" - step
-
-## Plan Document Header
-
-**Every plan MUST start with this header:**
-
-```markdown
-# [Feature Name] Implementation Plan
-
-> **For agentic workers:** Tasks use checkbox (`- [ ]`) syntax for tracking. Execution mode is determined by the coordinator after plan completion.
-
-**Goal:** [One sentence describing what this builds]
-
-**Architecture:** [2-3 sentences about approach]
-
-**Tech Stack:** [Key technologies/libraries]
-
----
-```
-
-## Task Structure
-
-````markdown
-### Task N: [Component Name]
-
-**Files:**
-- Create: `exact/path/to/file.py`
-- Modify: `exact/path/to/existing.py:123-145`
-- Test: `tests/exact/path/to/test.py`
-
-- [ ] **Step 1: Write the failing test**
-
-```python
-def test_specific_behavior():
-    result = function(input)
-    assert result == expected
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `pytest tests/path/test.py::test_name -v`
-Expected: FAIL with "function not defined"
-
-- [ ] **Step 3: Write minimal implementation**
-
-```python
-def function(input):
-    return expected
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `pytest tests/path/test.py::test_name -v`
-Expected: PASS
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add tests/path/test.py src/path/file.py
-git commit -m "feat: add specific feature"
-```
-````
-
-## No Placeholders
-
-Every step must contain the actual content an engineer needs. These are **plan failures** — never write them:
-- "TBD", "TODO", "implement later", "fill in details"
-- "Add appropriate error handling" / "add validation" / "handle edge cases"
-- "Write tests for the above" (without actual test code)
-- "Similar to Task N" (repeat the code — the engineer may be reading tasks out of order)
-- Steps that describe what to do without showing how (code blocks required for code steps)
-- References to types, functions, or methods not defined in any task
-
-## Remember
-- Exact file paths always
-- Complete code in every step — if a step changes code, show the code
-- Exact commands with expected output
-- DRY, YAGNI, TDD, frequent commits
-
-## Self-Review
-
-After writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.
-
-**1. Spec coverage:** Skim each section/requirement in the spec. Can you point to a task that implements it? List any gaps.
-
-**2. Placeholder scan:** Search your plan for red flags — any of the patterns from the "No Placeholders" section above. Fix them.
-
-**3. Type consistency:** Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called `clearLayers()` in Task 3 but `clearFullLayers()` in Task 7 is a bug.
-
-If you find issues, fix them inline. No need to re-review — just fix and move on. If you find a spec requirement with no task, add the task.
-
-## Execution
-
-Ostacky (the coordinator) handles execution-mode analysis and user confirmation after the plan is ready. This skill only writes the plan — it does NOT offer the user an execution mode choice. If an execution-mode prompt appears, defer to the coordinator.