omcc-workflow

Coordinate code and document tasks through structured OMCC roles and phases.

1|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Lynricsy/Oh-My-ClaudeCode --skill omcc-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omcc-workflow
Source: https://github.com/Lynricsy/Oh-My-ClaudeCode/tree/main/skills/omcc-workflow
Command: npx skills add https://github.com/Lynricsy/Oh-My-ClaudeCode --skill omcc-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMCC coordinates multi-person software tasks by clearly defining roles and a structured workflow to reduce miscommunication and handoff delays.

Core Features & Use Cases

  • Role-based collaboration (Coder, Reviewer, Advisor, Frontend, Librarian, Looker) for end-to-end development and documentation workflows.
  • Task decomposition, staged execution, and formal reviews to ensure quality and traceability across code changes and documentation edits.
  • Use cases include implementing features, fixing bugs, refactoring, and performing code reviews in software projects.

Quick Start

Prompt a clearly defined task and context to the Coder, then follow the OMCC workflow through sequential coding, reviewing, and advising steps.

Frequently Asked Questions about omcc-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multi-role code and document tasks to reduce handoff delays?

Multi-role code tasks are coordinated using a structured OMCC workflow with defined roles like coder, reviewer, and advisor, enforcing phased execution and clear acceptance criteria to reduce handoff delays.

What is the best way to structure feature implementation and code reviews across a software project?

Structuring feature implementation and code reviews involves applying a disciplined workflow with task decomposition, sequential role-based execution, and formal quality gates to ensure traceable progress across software projects.

How does role-based collaboration work for refactoring and bug fixing workflows?

Role-based collaboration for refactoring and bug fixing works by assigning specific roles such as coder, reviewer, and advisor to execute staged tasks, ensuring changes pass formal reviews and defined quality gates.

Can I use this workflow for both code changes and documentation edits?

Yes, you can use this workflow for both code changes and documentation edits, as it coordinates end-to-end tasks using task prompting, phased execution, and traceable inputs and outputs.

Do I need to define task prompts and acceptance criteria before starting software collaboration?

Yes, you need to define clear task prompts and acceptance criteria before starting, because the workflow enforces disciplined task decomposition and formal reviews to guarantee traceable progress and quality.

Why should I use a structured workflow for software engineering tasks instead of ad-hoc collaboration?

A structured workflow is necessary to reduce miscommunication and handoff delays by clearly defining roles, enforcing phased execution, and applying formal reviews to ensure traceable progress across code and document tasks.