← all publishers

DeL-TaiseiOzaki

@del-taiseiozaki source repo

15 published skills

  1. ▌
    Design Tracker · del-taiseiozaki
    Record a project design decision into .claude/docs/DESIGN.md through the shared typed writer. Use when the user says "record this", "add to design", "document this", "記録して", or asks what has been decided so far — and when a design decision has just been made and should not be lost.
    1 install
  2. ▌
    Update Lib Docs · del-taiseiozaki bundle
    Update library documentation in .claude/docs/libraries/ with latest information from web search.
    1 install
  3. ▌
    Troubleshoot · del-taiseiozaki bundle
    Diagnose and plan fixes for errors/bugs with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for deep code reasoning, hypothesis evaluation, and fix validation. Phase 1: Error reproduction & context gathering (Opus subagent 1M context + Codex initial analysis + Claude user interaction). Phase 2: Parallel diagnosis (Agent Teams: Root Cause Analyst [Codex-driven] + Impact Investigator [Opus + Codex risk analysis]). Phase 3: Fix plan synthesis, Codex validation & user approval. Fix implementation is handled separately by /team-execute.
    1 install
  4. ▌
    Checkpointing · del-taiseiozaki bundle
    Save session activity, rebuild rolling PROGRESS.md, and compact stale working blocks in .claude/STATE.md.
    1 install
  5. ▌
    Context Loader · del-taiseiozaki bundle
    ALWAYS activate this skill at the start of every task. Load shared rules from .claude/rules/ and project design context before executing any task.
    1 install
  6. ▌
    Codex System · del-taiseiozaki bundle
    Codex CLI handles planning, design, and complex code implementation. Use for: architecture design, implementation planning, complex algorithms, debugging (root cause analysis), trade-off evaluation, code review. External research is NOT Codex's job — use general-purpose-opus instead. Explicit triggers: "plan", "design", "architecture", "think deeper", "analyze", "debug", "complex", "optimize".
    1 install
  7. ▌
    Research Lib · del-taiseiozaki
    Research a library and create comprehensive documentation in .claude/docs/libraries/.
    1 install
  8. ▌
    Team Execute · del-taiseiozaki bundle
    Two-phase Agent Teams execution — replaces the old /team-implement and /team-review skills. Phase 1 IMPLEMENT (formerly /team-implement): parallel implementation with teammates per module/layer, file-ownership separation, and a shared task list with dependencies. Run after /feature plan approval. Phase 2 REVIEW (formerly /team-review): specialized reviewers (security, quality, test coverage) review the changes from different perspectives in parallel. Pass --review-only to skip Phase 1 and review existing changes (after manual or Codex implementation).
    1 install
  9. ▌
    Catchup · del-taiseiozaki bundle
    Comprehensive onboarding for new or returning contributors. Scans repository artifacts (git history, .claude/STATE.md, project rules, skill catalog, DESIGN.md, research & library notes, checkpoints, agent-team logs) and synthesizes a GUIDE.md at the repository root summarizing what has been worked on, why, and how to resume work.
    1 install
  10. ▌
    Feature · del-taiseiozaki bundle
    Unified feature planning & implementation skill — replaces the old /add-feature and /start-feature skills (both trigger phrases still apply here). MODE=existing (formerly /add-feature): add a feature to an established codebase with Codex-first collaboration — Codex is consulted in every phase for scope analysis, architecture design, implementation planning, and validation. MODE=greenfield (formerly /start-feature): start a large or new feature that requires external research — Agent Teams (Researcher + Architect) do parallel research & design. Both modes share Phase 3 complexity routing (SIMPLE: Codex direct, MODERATE: Codex + /team-execute --review-only, COMPLEX: /team-execute).
    1 install
  11. ▌
    Simplify · del-taiseiozaki bundle
    Simplify and refactor code while preserving functionality and library constraints.
    1 install
  12. ▌
    Tdd · del-taiseiozaki
    Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
    1 install
  13. ▌
    Init · del-taiseiozaki bundle
    Analyze project structure, populate .claude/docs/DESIGN.md, and write the thin Repository Identity section in .claude/STATE.md.
    1 install
  14. ▌
    Plan · del-taiseiozaki
    Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
    1 install
  15. ▌
    Spike · del-taiseiozaki bundle
    Time-boxed technical investigation/feasibility study with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for question framing, feasibility analysis, and final evaluation. Phase 1: Frame the investigation question & constraints (Claude user interaction + Codex question decomposition). Phase 2: Parallel investigation (Agent Teams: Researcher [Opus external research] + Feasibility Analyst [Codex deep analysis] + optional prototype). Phase 3: Codex synthesis into go/no-go recommendation & research report. Produces a DECISION DOCUMENT, NOT an implementation plan. Use /feature after a GO decision.
    1 install