skills.rest
kevhsunami
kevhsunamiCOMMUNITY
Explore all skills by this author →
GitHub

ceos-ids

Identify and resolve CEOS workflow issues using the EOS IDS process.

Updated Apr 12, 2026
Search Tags:#workflow#ids#root-cause-analysis#issue-management#eos#to-dos#l10
One-click install
npx skills add https://github.com/kevhsunami/EOS --skill ceos-ids-kevhsunami
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ceos-ids
Source: https://github.com/kevhsunami/EOS/tree/main/skills/ceos-ids
Command: npx skills add https://github.com/kevhsunami/EOS --skill ceos-ids-kevhsunami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The EOS IDS process provides a disciplined, repeatable method for identifying, discussing, and solving issues by uncovering root causes, capturing diverse perspectives, and generating concrete To-Dos with owners and due dates.

Core Features & Use Cases

  • Root-cause analysis via the 5 Whys to identify underlying problems
  • Structured discussion during L10 meetings and open sessions to align perspectives
  • Actionable resolution with assigned owners, due dates, and validation of outputs
  • Use Case: When a team faces an ongoing bottleneck, surface the issue, discuss root causes, and assign To-Dos to resolve it

Quick Start

Run the IDS workflow to identify an issue, discuss perspectives, and implement To-Dos with owners and deadlines.

Frequently Asked Questions about ceos-ids

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

FAQPage Schema
How do I run root-cause analysis for issue management during L10 meetings?▼

Root-cause analysis during L10 meetings is executed using the IDS process to identify underlying problems via the 5 Whys, discuss perspectives, and generate concrete To-Dos with assigned owners and due dates.

What is the EOS IDS process for structured issue resolution?▼

The EOS IDS process is a disciplined, repeatable method for identifying, discussing, and solving issues by uncovering root causes, capturing diverse perspectives, and generating concrete To-Dos with assigned owners and due dates.

Do I need a specific repository structure to use the EOS IDS workflow?▼

Yes, the EOS IDS workflow requires access to the CEOS repository structure, specifically the .ceos root marker and templates/issue.md to read and write issue data across open and solved directories.

How do I assign owners and due dates when resolving team bottlenecks?▼

You assign owners and due dates by creating actionable To-Dos as the final step of the IDS workflow, ensuring every identified root cause has a concrete resolution plan with validated outputs.

Can I track resolved issues separately from open issues in the CEOS workflow?▼

Yes, you can track resolved issues separately by writing and reading issue data across the data/issues/open and data/issues/solved directories within the CEOS repository structure.

Related Skills

Explore More Product & Management Skills→
kevhsunamikevhsunami

ceos-l10

Manage Level 10 meetings with a seven-section agenda and CEOS data.

Community
Advanced
danieljformandanieljforman

ceos-ids

Identify root causes and assign owner To-Dos with due dates.

Community
Advanced
bradfeldbradfeld
143

ceos-ids

Manage the Identify, Discuss, Solve process for business issues within the EOS framework.

Community
Advanced
AstravueOrgAstravueOrg
12

triaging-overdue-work

Identify overdue tasks, determine root causes, and propose triage actions for approval.

Official
Intermediate