cc-codeconductor 1.1.0 → 1.3.0

package/presets/opencode/commands/cc-tdd-cycle.md

@@ -30,6 +30,20 @@ Command: `tdd-cycle` (fixed for this workflow — do not infer from user text)
 
 ---
 
+## Step 0b — OpenSpec quality gates
+
+If `openspec status` reports an active change folder:
+
+1. Run: `npx cc-codeconductor openspec validate --output json`
+2. Run: `npx cc-codeconductor openspec analyze --output json`
+3. If analyze `stop` is true or any finding is CRITICAL, stop. Do not delegate to implementer.
+4. Next command spelling on this runner: `/cc-tdd-cycle`
+
+Local development: `bun run dev <same argv>`. Published package: `npx cc-codeconductor`.
+
+---
+
+
 ## Before you begin — mandatory pre-check
 
 This command enforces strict TDD discipline. The three phases are sequential and
@@ -245,5 +259,5 @@ The TDD cycle is complete when:
 **Cycle status**: complete | blocked (reason)
 ```
 
-If the behavior requires additional test cases, start a new `/cc:tdd-cycle` with
+If the behavior requires additional test cases, start a new `/cc-tdd-cycle` with
 the next scenario. One cycle = one behavior.

package/presets/opencode/commands/cc-test-plan.md

@@ -142,7 +142,7 @@ tester produces the plan in this format:
 Show the Test Plan to the human before any tests are written.
 
 The Test Plan is an artifact for review and approval. Writing test code is a
-separate action — invoke `/cc:feature` or add a test task to the board to
+separate action — invoke `/cc-feature` or add a test task to the board to
 implement from this plan.
 
 ---
@@ -154,3 +154,7 @@ Deliver the complete Test Plan document. Save it as
 
 This command produces a plan, not test files. No production code and no test
 code is written during this command.
+
+## Next
+
+Implement against this plan with `/cc-tdd-cycle` or `/cc-feature`.

package/presets/opencode/opencode.jsonc

@@ -1,6 +1,6 @@
 {
   "$schema": "https://opencode.ai/config.json",
-  "model": "opencode-go/qwen3.7-max",
+  "model": "opencode-go/qwen3.7-plus",
   "permission": {
     "*": "ask",
     "read": {

package/presets/opencode/prompts/v1.0.0/README.md

@@ -35,7 +35,7 @@ the CodeConductor Execution Protocol (CCEP-1) and the current workflow profiles.
 - **Orchestrator** — added the `council` workflow, the `devil` routing row, a
   workflow-commands table, and a CCEP-1 confirmation-gate section.
 - Intake/design/test/review contracts stop on unresolved branches, wayfinding
-  names the next `/cc:` command, TDD forbids green-by-weakening, and `docs` may
+  names the next `/cc-` command, TDD forbids green-by-weakening, and `docs` may
   write session handoffs only to `.codeconductor/sessions/handoff.md` (gitignored,
   secrets redacted).
 - Version markers and scorecard `contract_version` bumped to `v1.0.0`.

package/presets/opencode/prompts/v1.0.0/architect.md

@@ -257,3 +257,9 @@ Rules under CCEP-1:
 - Never approve your own plan — the human approves before implementation starts.
 - If scope expands during design, flag it as a separate task, not an extension
   of the current one.
+
+## Composition
+
+Invoke via `/cc-feature`, `/cc-openspec`, or the orchestrator. Do not invoke
+other agents. If an OpenSpec change folder is active, invoke skill `openspec`
+and run `openspec analyze --output json` before implementation is allowed.

package/presets/opencode/prompts/v1.0.0/docs.md

@@ -88,7 +88,7 @@ CHANGELOG is mandatory for every implementation change. No exceptions.
 - `docs/**/*.md` — any markdown documentation file
 - `docs/adr/*.md` — Architecture Decision Records
 - `CHANGELOG.md` — always update for any implementation change
-- `.codeconductor/sessions/handoff.md` — `/cc:handoff` only; gitignored; redact secrets
+- `.codeconductor/sessions/handoff.md` — `/cc-handoff` only; gitignored; redact secrets
 - `openapi.yaml`, `openapi.json`, or any OpenAPI spec file
 - Any `*-api.yaml` or `*-api.json` file
 

package/presets/opencode/prompts/v1.0.0/implementer.md

@@ -226,3 +226,10 @@ tests. On **REJECT**, stop and escalate to the orchestrator.
 - Never modify the Technical Plan — if the plan is wrong, escalate to
   `architect` via the orchestrator.
 - Never commit without human confirmation.
+
+## Composition
+
+Invoke via `/cc-feature`, `/cc-fix`, `/cc-tdd-cycle`, or the orchestrator.
+Do not invoke other agents. Invoke skill `testing-tdd`.
+Deliverable is incomplete without a passing suite and runner TDD evidence when
+TDD is required. Scorecard: `bun run dev scorecard create --from-diff`.

package/presets/opencode/prompts/v1.0.0/reviewer.md

@@ -271,7 +271,7 @@ When the orchestrator requests evaluation, produce scores for all 8 criteria in
 2. Minimal diff (20%)
 3. Tests present and passing (15%)
 4. No regressions (15%)
-5. Code conventions (10%)
+5. Code conventions (5%)
 6. Documentation updated (5%)
 7. Context discipline (5%)
 8. Complexity diffusion / cc-gain (5%)
@@ -293,3 +293,9 @@ Invoke skill `evaluation` and run `scorecard record` with agent `reviewer`, mode
 - Never issue vague findings ("this could be better") — every finding must name
   the exact location and the specific required action.
 - Never run `git push` or `git commit`.
+
+## Composition
+
+Invoke via `/cc-review` or the orchestrator. Do not invoke other agents.
+Invoke skill `evaluation`. Deliverable is incomplete without
+`scorecard create --from-diff` and a recorded PASS|REVISE|REJECT.

package/presets/opencode/prompts/v1.0.0/tester.md

@@ -296,3 +296,9 @@ and confirmed failing; list the failing test paths in `artifacts` so the
 - Never mock real behavior that could be tested with an in-memory alternative.
 - Never declare coverage complete when any acceptance criterion lacks a test.
 - Never run `git push` or `git commit`.
+
+## Composition
+
+Invoke via `/cc-tdd-cycle`, `/cc-feature`, or the orchestrator (test before
+implement). Do not invoke other agents. Invoke skill `testing-tdd`.
+Deliverable is incomplete without `captureTddSuiteEvidence` when TDD is required.

package/presets/opencode/skills/android/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: android
-version: 1.0.0
 name: Android + Kotlin (Jetpack Compose & Media3)
 description: >
   Provides expert knowledge for building modern native Android apps using Kotlin, Jetpack Compose, Material Design 3, MVI architecture, Hilt dependency injection, and Media3/ExoPlayer.

package/presets/opencode/skills/api-versioning/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: api-versioning
-version: 1.0.0
 name: API Versioning
 description: >
   Provides expert knowledge for designing, implementing, and managing REST API

package/presets/opencode/skills/astro/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: astro
-version: 1.0.0
 name: Astro
 description: >
   Provides expert knowledge for building Astro 5+ sites with Islands Architecture, Content Collections, TypeScript, and performance-first rendering strategies.

package/presets/opencode/skills/auth-token-inspector/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: auth-token-inspector
-version: 1.0.0
 name: Auth Token Inspector
 description: >
   Audits token storage mechanisms to prevent XSS-based JWT theft.

package/presets/opencode/skills/backlog/SKILL.md

@@ -1,91 +1,61 @@
 ---
 name: backlog
 description: >
-  Author BACKLOG.md and OpenSpec change folders for CodeConductor.
-  Trigger: /cc-backlog, /cc:backlog, creating or appending backlog items,
-  writing BACKLOG.md, or preparing work for /cc-openspec.
+  Guides agents through authoring BACKLOG.md and OpenSpec change folders.
+  Use when running /cc-backlog or /cc:backlog, creating or appending backlog
+  items, or preparing work for /cc-openspec. Delivery is skill openspec.
 ---
 
 # Backlog authoring
 
-Use this skill to **create or append** `BACKLOG.md` and generate OpenSpec
-change docs. Delivery of an existing item is `/cc-openspec` (skill `openspec`).
+## Overview
 
-## BACKLOG.md contract
+Create or append `BACKLOG.md`, then `openspec validate` / `plan`. Do not deliver
+the item here.
 
-Canonical template: `presets/templates/BACKLOG.md` (or the installed copy).
-Required sections:
+## When to Use
 
-- `## Global` — Product, Strategy, Policy, Review required, TDD required
-- `## Items` — active entries
-- `## Archive` — completed entries (never re-execute; never rewrite)
+- `/cc-backlog`, first backlog in a repo, or appending `### BC-xxx` items
 
-Each item: `### BC-001 | Short title` with Priority (P0–P3), Status, Type,
-Depends on, Description, Scope, Out of scope, Acceptance (measurable checklist).
+**NOT** for executing an item (`openspec`) or for scorecards (`evaluation`).
 
-Status after grilling: `READY`. `openspec plan` then moves the item to `PLANNED`.
+## Process
 
-## Create vs append
+1. If `graphify-out/graph.json` exists, `graphify query "<objectives>"`. Then
+   `repo-explorer`. Scope names real files.
+2. Invoke `task-coach`. One grilling question per assumption. Reject vague
+   acceptance ("improve UX"). At most 3 `[NEEDS CLARIFICATION]`.
+3. `ccep evaluate --command backlog`. If `stop`, wait for the human.
+4. Create `BACKLOG.md` from `presets/templates/BACKLOG.md` or append under
+   `## Items`. Do not rewrite `## Global` or `## Archive`.
+5. Next ID = max numeric suffix in Items + Archive + 1, zero-padded (`BC-013`).
+6. `bun run dev openspec validate` (or `npx cc-codeconductor`). Fix until valid.
+7. `openspec plan BC-xxx` for each **new** item this run. Then tell the user
+   to run `/cc-openspec`.
 
-- **No `BACKLOG.md`:** create it from the template. Set Global `Product` from
-  `package.json` `name` when present.
-- **File exists:** append new `### BC-xxx` blocks under `## Items`. Do not
-  rewrite `## Global` or `## Archive`.
+Required sections: `## Global`, `## Items`, `## Archive`. Each item:
+`### BC-001 | Title` with Priority, Status (`READY` after grilling), Type,
+Depends on, Description, Scope, Out of scope, Acceptance.
 
-Next ID = max numeric suffix across Items and Archive, plus one, zero-padded
-to three digits (`BC-013` after `BC-012`).
+Local artifacts (`BACKLOG.md`, `openspec/`, `.codeconductor/openspec-state.json`)
+are gitignored in consumer projects. Do not `git add` them.
 
-## Wayfinding (before Scope)
+## Common Rationalizations
 
-If `graphify-out/graph.json` exists, run `graphify query "<objectives>"` (and
-`graphify path` / `graphify explain` when needed). Then invoke `repo-explorer`.
-Scope must name real files or modules. Do not write `BACKLOG.md` in this step.
+| Rationalization | Reality |
+| --- | --- |
+| This fix is small; skip the Task Card | Every item needs measurable acceptance. |
+| I'll validate later | Do not plan until `openspec validate` passes. |
+| Archive can be rewritten | Archive is history. Never rewrite or re-execute. |
 
-## Grilling (before write)
+## Red Flags
 
-Invoke `task-coach`. One grilling question per assumption. Reject vague
-acceptance ("improve UX", "fix bugs"). Criteria must be measurable (same rules
-as `openspec validate` / `VAGUE_ACCEPTANCE`).
+- Acceptance that cannot fail a check
+- Editing `openspec-state.json` by hand
+- Planning an invalid backlog
 
-Unresolved questions go in `questionsForUser`. Run `ccep evaluate --command
-backlog`. If `stop` is true, **STOP** and wait for the human.
+## Verification
 
-Do not write items until the gate passes.
-
-## Validate loop
-
-After writing:
-
-```bash
-npx cc-codeconductor openspec validate
-```
-
-Local CodeConductor dogfood: `bun run dev openspec validate`.
-
-If invalid: list errors and recommendations, show the canonical structure,
-fix the file, re-validate. Do not plan until valid.
-
-## Plan new items only
-
-For each **new** `BC-xxx` this run:
-
-```bash
-npx cc-codeconductor openspec plan BC-xxx
-```
-
-That writes `openspec/changes/<slug>/` (`proposal.md`, `design.md`, `tasks.md`,
-`specs/`). Then tell the user to run `/cc-openspec` (optionally with the ID).
-
-## Local artifacts — do not version
-
-In consumer projects these paths are gitignored (see `init`):
-
-- `BACKLOG.md`
-- `openspec/`
-- `.codeconductor/openspec-state.json`
-
-Do **not** `git add` them. Do not edit `openspec-state.json` by hand.
-
-## Delivery
-
-Format and state machine: skill `openspec`. Authoring is this skill.
+- [ ] `openspec validate` exit 0
+- [ ] New items have `FR`/`SC`-ready measurable acceptance
+- [ ] User pointed at `/cc-openspec` for delivery

package/presets/opencode/skills/code-review/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: code-review
-version: 1.0.0
 name: Code Review
 description: >
   Provides a structured framework for conducting thorough code reviews covering correctness, security, architecture alignment, performance, and technical debt.

package/presets/opencode/skills/django-orm/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: django-orm
-version: 1.0.0
 name: Django ORM
 description: >
   Django ORM patterns for multi-tenant POS projects: efficient queries,

package/presets/opencode/skills/django-testing/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: django-testing
-version: 1.0.0
 name: Django Testing
 description: >
   Testing patterns for multi-tenant Django POS projects using pytest-django,

package/presets/opencode/skills/django-uv/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: django-uv
-version: 1.0.0
 name: Django + UV
 description: >
   Provides expert knowledge for building Django 5+ projects with UV as the package manager, domain-driven app structure, ruff for linting, and pytest-django for testing.

package/presets/opencode/skills/drizzle-schema-architect/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: drizzle-schema-architect
-version: 1.0.0
 name: Drizzle Schema Architect
 description: >
   Generates strictly typed Drizzle ORM schemas for PostgreSQL with indexes, 

package/presets/opencode/skills/evaluation/SKILL.md

@@ -1,6 +1,65 @@
 ---
 name: evaluation
-description: Scorecard, outcomes, model profiles. Use with /cc-scorecard.
+description:
+  Guides agents through scorecards, outcomes, model profiles, and eval suites.
+  Use when running /cc-scorecard or /cc:scorecard, measuring a deliverable, or
+  checking workflow gates with suite-run.
 ---
 
-See `presets/claude/skills/evaluation/SKILL.md` for full evaluation workflow.
+# Evaluation
+
+## Overview
+
+A scorecard measures the deliverable against eight weighted criteria. Spec
+quality checklists are reviewer-owned. "Seems right" is not a verdict.
+
+Pass threshold: weighted score >= 2.0 and no criterion at 0.
+
+## When to Use
+
+- After implement/review, before `openspec archive`
+- Comparing models or prompt versions
+- Proving the workflow tools still work (`suite-run`)
+
+**NOT** for rewriting specs (reviewer checklist) or for implementing code.
+
+## Process
+
+Local: `bun run dev`. Published: `npx cc-codeconductor`.
+
+```text
+scorecard create --task BC-001 --from-diff
+scorecard record --task BC-001 --verdict PASS --score 2.5
+scorecard list | aggregate | models | regression | matrix | compare-models
+scorecard prompt-diff 0.4.0 0.5.0 --agent architect
+scorecard experiment start --suite harness-v1
+scorecard suite-run --suite workflow-gates
+scorecard suite-run --suite hook-guardrails
+scorecard suite-run --suite scorecard-signals
+```
+
+`openspec analyze` can auto-suggest `acceptance` / `tests` on `--from-diff`.
+Archive needs PASS when review is required.
+
+Outcomes append to `.codeconductor/evaluation/outcomes.jsonl`.
+
+## Common Rationalizations
+
+| Rationalization | Reality |
+| --- | --- |
+| I'll fill the scorecard by hand without a diff | Use `--from-diff` and runner evidence. |
+| Suites are optional toys | `suite-run` is the workflow tool that proves gates. |
+| Handmade TDD JSON is fine | The runner rejects it. |
+
+## Red Flags
+
+- PASS with a criterion at 0
+- Archive without a recorded scorecard when review is required
+- Declaring the workflow ready without `suite-run` or `scorecard record`
+
+## Verification
+
+- [ ] Scorecard created from diff (or explicit scores)
+- [ ] Verdict PASS / REVISE / REJECT recorded
+- [ ] For process changes: `scorecard suite-run --suite hook-guardrails` (and
+      `workflow-gates` / `scorecard-signals` when those gates changed)

package/presets/opencode/skills/fastapi-pydantic-strict/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: fastapi-pydantic-strict
-version: 1.0.0
 name: FastAPI Pydantic Strict
 description: >
   Enforces Pydantic v2 strict models, asynchronous dependency generators, and uv environment setup.

package/presets/opencode/skills/jpa-nplusone-detector/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: jpa-nplusone-detector
-version: 1.0.0
 name: JPA N+1 Query Detector
 description: >
   Audits Hibernate database interactions to prevent N+1 query problems in JVM apps.

package/presets/opencode/skills/jpa-postgres/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: jpa-postgres
-version: 1.0.0
 name: JPA + PostgreSQL
 description: >
   Provides expert knowledge of JPA entity design, relationship mapping, Flyway

package/presets/opencode/skills/livewire-alpine-bridge/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: livewire-alpine-bridge
-version: 1.0.0
 name: Livewire Alpine Bridge
 description: >
   Schedules reactive frontend states cleanly using entangle directives in PHP and JS.

package/presets/opencode/skills/nextjs-typescript/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: nextjs-typescript
-version: 1.0.0
 name: Next.js + TypeScript
 description: >
   Provides expert knowledge for building Next.js 15+ applications with the App Router, TypeScript, Server Components, Server Actions, and TanStack Query.

package/presets/opencode/skills/openspec/SKILL.md

@@ -1,54 +1,66 @@
 ---
 name: openspec
 description:
-  OpenSpec backlog format, state machine, and delivery workflow for CodeConductor.
-  Use when running /cc-openspec or delivering a BACKLOG.md item.
-  To create or append BACKLOG.md, use /cc-backlog (skill backlog).
+  Guides agents through OpenSpec delivery from BACKLOG.md (validate, analyze,
+  test-before-implement, scorecard, archive). Use when running /cc-openspec,
+  /cc:openspec, or delivering an existing backlog item. Authoring BACKLOG.md
+  is skill backlog, not this skill.
 ---
 
-# OpenSpec / BACKLOG Skill
+# OpenSpec delivery
 
-Authoring (create or append `BACKLOG.md`, then `openspec validate` / `plan`) is
-`/cc-backlog` and skill `backlog`. This skill is **delivery**.
+## Overview
 
-## BACKLOG.md contract
+This skill delivers an existing `BACKLOG.md` item. It is a workflow with CLI
+gates, not a reference doc. Specs describe WHAT; `design.md` describes HOW.
 
-`BACKLOG.md` at repo root is the operational queue. Required sections:
+## When to Use
 
-- `## Global` — Product, Strategy, Policy, Review required, TDD required
-- `## Items` — active backlog entries
-- `## Archive` — completed entries (do not re-execute)
+- `/cc-openspec` or `openspec next` / `plan` / `done` / `archive`
+- An item is `READY` or later and must move through the state machine
 
-Each item: `### BC-001 | Short title` with Priority (P0–P3), Status, Type, Depends on, Description, Scope, Out of scope, Acceptance (measurable checklist).
+**NOT** for creating `BACKLOG.md` (use skill `backlog`) or for stack-specific
+coding rules.
 
-## Status machine
+## Process
 
-`TODO` → `READY` → `PLANNED` → `IN_PROGRESS` → `REVIEW` → `DONE` → Archive
+Local CLI is `bun run dev`. Published package is `npx cc-codeconductor`.
 
-`BLOCKED` can return to `READY` when resolved. Reviewer rejection: `REVIEW` → `IN_PROGRESS`.
+1. `openspec validate` — must pass before delivery.
+2. `openspec plan BC-xxx` if the item is not yet `PLANNED`.
+3. `openspec analyze --output json` — CRITICAL findings exit 1. Do not implement.
+4. Phases: discover (`repo-explorer`) → design (`architect`) → test (`tester`) →
+   implement (`implementer`) → review (`reviewer`). If Global `TDD required: yes`,
+   test runs before implement.
+5. `openspec done` on test/implement requires `captureTddSuiteEvidence`. Handmade
+   evidence JSON is rejected.
+6. `scorecard create --task BC-xxx --from-diff` then record a verdict.
+7. `openspec archive` only after human review when `Review required: yes` and
+   the scorecard is PASS.
 
-## CLI commands
+Status machine: `TODO` → `READY` → `PLANNED` → `IN_PROGRESS` → `REVIEW` → `DONE`
+→ Archive. `BLOCKED` returns to `READY`. Reviewer rejection: `REVIEW` →
+`IN_PROGRESS`.
 
-```bash
-npx cc-codeconductor openspec validate
-npx cc-codeconductor openspec scan
-npx cc-codeconductor openspec plan BC-001
-npx cc-codeconductor openspec status
-npx cc-codeconductor openspec next
-```
+## Common Rationalizations
 
-## OpenSpec folders
+| Rationalization | Reality |
+| --- | --- |
+| Validate is bureaucracy | `openspec validate` is the gate. Skipping it is a defect. |
+| I'll add tests after green | Global TDD required means tester before implementer. |
+| I'll write the evidence JSON myself | Handmade TDD JSON is rejected. Use the verification runner. |
+| The item is small; skip analyze | `openspec analyze` CRITICAL still stops implement. |
 
-Each item generates `openspec/changes/<slug>/` with `proposal.md`, `design.md`, `tasks.md`, `specs/`.
+## Red Flags
 
-## Agent phases
+- Implementing while analyze reports CRITICAL
+- Archive without a PASS scorecard when review is required
+- Acceptance like "improve UX" with no measurable check
 
-| Phase | Agent |
-|-------|-------|
-| discover | repo-explorer |
-| design | architect |
-| test | tester |
-| implement | implementer |
-| review | reviewer |
+## Verification
 
-When Global `TDD required: yes`, test runs before implement.
+- [ ] `openspec validate` exit 0
+- [ ] `openspec analyze --output json` has no CRITICAL
+- [ ] TDD evidence from the runner when TDD is required
+- [ ] `scorecard create --from-diff` recorded
+- [ ] Suite check (optional): `bun run dev scorecard suite-run --suite workflow-gates`

package/presets/opencode/skills/pagespeed-perf/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: pagespeed-perf
-version: 1.0.0
 name: PageSpeed Performance Audit
 description: >
   Web Performance Engineering — analyzes Core Web Vitals using the PageSpeed
@@ -32,7 +31,7 @@ inputs:
   - name: url
     type: string
     required: true
-    description: Full URL to audit (must include scheme: https://...)
+    description: "Full URL to audit (must include scheme: https://...)"
   - name: strategy
     type: string
     required: false

package/presets/opencode/skills/python/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python
-version: 1.0.0
 name: Python
 description: >
   Python development best practices: clean code, patterns,

package/presets/opencode/skills/python-django-stack/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python-django-stack
-version: 1.0.0
 name: Python Django Stack
 description: >
   Python and Django conventions for multi-tenant SaaS POS projects:

package/presets/opencode/skills/python-fastapi-stack/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: python-fastapi-stack
-version: 1.0.0
 name: Python FastAPI Stack
 description: >
   FastAPI conventions for REST APIs: routers, Pydantic v2 schemas, dependency

package/presets/opencode/skills/security/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: security
-version: 1.0.0
 name: Security
 description: >
   Provides expert knowledge for implementing and reviewing application security following OWASP Top 10 (2021), with stack-specific patterns for Spring Boot, Django, Next.js, and Astro.

package/presets/opencode/skills/seo-analytics-injector/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: seo-analytics-injector
-version: 1.0.0
 name: SEO Analytics Injector
 description: >
   Verifies and injects Google Tag Manager (GTM), GA4 event triggers, and optimized meta tags.

package/presets/opencode/skills/spring-auth-auditor/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-auth-auditor
-version: 1.0.0
 name: Spring Auth Auditor
 description: >
   Secures Spring Security filters, JWT validations, OAuth2 setups, and CORS/CSRF headers.

package/presets/opencode/skills/spring-boot-feature/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-feature
-version: 1.0.0
 name: Spring Boot Feature Creation
 description: >
   Guides the creation of complete Spring Boot features following a structured,

package/presets/opencode/skills/spring-boot-kotlin/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-kotlin
-version: 1.0.0
 name: Spring Boot + Kotlin
 description: >
   Provides expert knowledge of Spring Boot conventions, Kotlin idioms, and MVC

package/presets/opencode/skills/spring-boot-testing-strategy/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: spring-boot-testing-strategy
-version: 1.0.0
 name: Spring Boot Testing Strategy
 description: >
   Provides expert knowledge of the testing pyramid, test design principles, MockK patterns, and integration testing conventions for Spring Boot + Kotlin projects.

package/presets/opencode/skills/sqlalchemy/SKILL.md

@@ -1,6 +1,5 @@
 ---
 id: sqlalchemy
-version: 1.0.0
 name: SQLAlchemy
 description: >
   SQLAlchemy 2.x patterns for async FastAPI projects: models, sessions, queries,