claude skills

CLAUDE.md

@@ -1,3 +1,10 @@
+# OpenWolf
+
+@.wolf/OPENWOLF.md
+
+This project uses OpenWolf for context management. Read and follow .wolf/OPENWOLF.md every session. Check .wolf/cerebrum.md before generating code. Check .wolf/anatomy.md before reading files.
+
+
 # XCE Cluster Management System
 
 ## Overview
@@ -133,31 +140,38 @@ Kiro-style Spec-Driven Development on an agentic SDLC
 
 ### Active Specifications
 - Check `.kiro/specs/` for active specifications
-- Use `/kiro:spec-status [feature-name]` to check progress
+- Use `/kiro-spec-status [feature-name]` to check progress
 
 ## Development Guidelines
 - Think in English, generate responses in English. All Markdown content written to project files (e.g., requirements.md, design.md, tasks.md, research.md, validation reports) MUST be written in the target language configured for this specification (see spec.json.language).
 
 ## Minimal Workflow
-- Phase 0 (optional): `/kiro:steering`, `/kiro:steering-custom`
+- Phase 0 (optional): `/kiro-steering`, `/kiro-steering-custom`
 - Phase 1 (Specification):
-  - `/kiro:spec-init "description"`
-  - `/kiro:spec-requirements {feature}`
-  - `/kiro:validate-gap {feature}` (optional: for existing codebase)
-  - `/kiro:spec-design {feature} [-y]`
-  - `/kiro:validate-design {feature}` (optional: design review)
-  - `/kiro:spec-tasks {feature} [-y]`
-- Phase 2 (Implementation): `/kiro:spec-impl {feature} [tasks]`
-  - `/kiro:validate-impl {feature}` (optional: after implementation)
-- Progress check: `/kiro:spec-status {feature}` (use anytime)
+  - `/kiro-spec-init "description"` — initialize spec scaffold
+  - `/kiro-spec-quick "description"` — fast single-pass spec (requirements + design + tasks, no approval gates)
+  - `/kiro-spec-batch` — generate specs for all features in a roadmap in parallel
+  - `/kiro-spec-requirements {feature}`
+  - `/kiro-validate-gap {feature}` (optional: for existing codebase)
+  - `/kiro-spec-design {feature} [-y]`
+  - `/kiro-validate-design {feature}` (optional: design review)
+  - `/kiro-spec-tasks {feature} [-y]`
+- Phase 2 (Implementation): `/kiro-spec-impl {feature} [tasks]`
+  - `/kiro-validate-impl {feature}` (optional: after implementation)
+  - `/kiro-verify-completion {feature}` — validate all acceptance criteria are met
+- Debugging: `/kiro-debug {feature}` — systematic debugging with spec context
+- Code review: `/kiro-review` — review implementation against spec requirements
+- Progress check: `/kiro-spec-status {feature}` (use anytime)
 
 ## Development Rules
 - 3-phase approval workflow: Requirements → Design → Tasks → Implementation
 - Human review required each phase; use `-y` only for intentional fast-track
-- Keep steering current and verify alignment with `/kiro:spec-status`
+- Use `/kiro-spec-quick` for small, well-understood features; full workflow for anything touching HA/persistence/RBAC
+- Keep steering current and verify alignment with `/kiro-spec-status`
 - Follow the user's instructions precisely, and within that scope act autonomously: gather the necessary context and complete the requested work end-to-end in this run, asking questions only when essential information is missing or the instructions are critically ambiguous.
 
 ## Steering Configuration
 - Load entire `.kiro/steering/` as project memory
-- Default files: `product.md`, `tech.md`, `structure.md`
-- Custom files are supported (managed via `/kiro:steering-custom`)
+- Core files: `product.md`, `tech.md`, `structure.md`
+- XCE custom files: `testing.md`, `error-handling.md`, `security.md`
+- Add new custom files via `/kiro-steering-custom`