Claude Skills by boisenoise

Universal context reviewer: delegates arbitrary context (plans, decisions, documents, architecture proposals) to external agents (Codex + Gemini) for independent review with debate protocol. Context always passed via files.

Probes CLI agents (Codex, Gemini) and writes environment_state.json. Use when setting up a project or after installing/removing CLI agents.

Multi-agent context review: delegates plans, decisions, documents, architecture proposals to external agents (Codex + Gemini) for independent review with debate protocol. Works in Plan Mode.

Installs agents, configures MCP servers, aligns marketplace plugins, creates and audits instructions. Use after setup or when agents/MCP/plugins need alignment.

Installs or updates Codex CLI and Claude Code. Use when CLI agents need installation or update.

Use when installing MCP packages and configuring Claude-side MCP registration, hooks, permissions, IDE extension mode, and migrations.

Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.

Use when removing Claude-side hex-line integration surfaces such as MCP registration, permissions, hooks, and output style.

Use when bootstrapping or managing VPS agent environments: fresh install, add project, hex-relay redeploy, diagnostics, or fleet plan/apply.

Use when installing, verifying, or updating the shared VPS host runtime for Claude Code, Codex, MCP, and marketplace plugins.

Use when creating or verifying one project runtime on a prepared VPS, including god-session, provider credentials, and local dispatcher setup.

Use when deploying, redeploying, verifying, migrating, or syncing users for the hex-relay Telegram/API control plane on a VPS.

Use when inspecting health, drift, logs, auth, ports, systemd, tmux, or safe repair needs for one VPS project environment.

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.

Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.

Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.

Creates core project docs (requirements, architecture, tech stack, patterns catalog). Use for any project regardless of type.

Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.

Creates design_guidelines.md with WCAG 2.1 compliance and design system docs. Use when project has a frontend.

Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.

Creates reference docs (ADRs, guides, manuals) for nontrivial tech stack choices. Use when project needs justified architecture decision records.

Creates task management docs (kanban board, workflow rules) with Linear integration. Use when setting up task tracking for a project.

Creates test documentation (testing-strategy.md, tests/README.md) with Risk-Based Testing philosophy. Use when setting up test strategy for a project.

Builds interactive HTML presentation from project docs with Mermaid diagrams. Use when sharing project overview with stakeholders.

Extracts procedural content from project docs into slash commands. Use when docs contain deploy, test, or troubleshoot procedures.

Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.

Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.

Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.

Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.

Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.

Creates Story documents with 9-section structure and INVEST validation in Linear. Use when Epic has an IDEAL plan ready for Story generation.

Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.

RICE-scores Stories with market research and generates prioritization table. Use when Stories need business priority ranking for sprint planning.

Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.

Creates implementation, refactoring, and test tasks from templates. Use when an approved task plan needs tasks created in Linear and kanban.

Compares ideal plan vs existing tasks and applies KEEP/UPDATE/OBSOLETE/CREATE changes. Use when Story tasks need re-sync with updated requirements.

Use when validating Stories, plans, or tasks through the evaluation platform with mandatory research, parallel evidence lanes, sequential merge, and bounded refinement. Modes: story | plan_review.

Validates Stories/Tasks: GO/NO-GO verdict, Readiness Score (1-10), Penalty Points (Before/After), Anti-Hallucination. Auto-fixes fixable violations, FLAGs unfixable. Delegates to ln-002 for docs.

Runs parallel external agent reviews (Codex + Gemini) on Story/Tasks. Process-as-arrive, critical verification with debate. Returns filtered suggestions.

Use when an evaluation coordinator needs normalized findings from target artifacts and research evidence.

Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.

Use when accepted findings require bounded repair changes and a structured repair summary.

Use when an evaluation run must merge research, findings, documentation, and repair outputs into one verified result.

Use when an evaluation run requires bounded iterative refinement with trace and cleanup evidence.

Executes Story tasks in priority order (To Review, To Rework, Todo). Use when Story has planned tasks ready for implementation.

Executes implementation tasks through Todo, In Progress, To Review. Use when task needs coding with KISS/YAGNI. Not for test tasks.

Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework.

Fixes tasks in To Rework by applying reviewer feedback, then returns to To Review. Use when task was rejected during review.

Executes test tasks (label 'tests') through Todo to To Review with risk-based limits. Use for test task execution. Not for implementation tasks.