with one click
omoikane-cli
omoikane-cli contains 17 collected skills from d2a8k3u, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
CTO responsible for technical strategy, prioritization, tech-debt posture, and final calls on cross-cutting trade-offs.
Product Analyst responsible for turning briefs into concrete, checkable acceptance criteria and user stories.
QA Reviewer responsible for verifying acceptance criteria, code review, and functional and regression checks.
AI Engineer responsible for LLM integrations, RAG pipelines, prompt design, and evaluation of model-driven features.
Analyst responsible for debugging, log analysis, observability, and root-cause investigation.
Architect responsible for system structure, API contracts, tech-stack decisions, and architectural trade-offs.
Backend Engineer responsible for server-side logic, APIs, data access, and integrations.
Database Specialist responsible for data modeling, query optimization, migrations, and database reliability.
UI/UX Designer responsible for visual design, interaction patterns, and a coherent futuristic-yet-clean design system.
DevOps / Platform Engineer responsible for CI/CD, infrastructure, deployment, monitoring, and developer experience.
Frontend Engineer responsible for UI/UX implementation, component architecture, and client-side performance.
Implementer responsible for writing the code, the tests, and the small, atomic commits that build the system.
Ingests a specialist's final report after a supervisor-dispatched delegation, records the outcome in the Project Book, and surfaces blocked-on-approval signals. Leaf role — never dispatched by CTO routing, always dispatched explicitly by the orchestrator-protocol session after a specialist returns.
ML Engineer responsible for model training, fine-tuning, evaluation pipelines, and ML-system productionization.
Security Engineer responsible for application security, threat modeling, secure coding practices, and compliance.
Technical Writer responsible for documentation, developer guides, API documentation, and knowledge management.
Protocol the top-level orchestrator follows to drive a project from brief to verified completion via the Project Book and the specialist team.