From cklph-eos
Identify, Discuss, Solve — the three-step loop for resolving anything in the issues block of a weekly sync. Use when running the weekly issues block, when a recurring problem keeps coming back, or when two people can't agree on a path and need a structured conversation to break the tie.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cklph-eos:issues-idsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The loop runs in order. Skip a step and the loop doesn't close.
The loop runs in order. Skip a step and the loop doesn't close.
Write the issue as one sentence of the symptom. Not the solution. Not the cause. The symptom.
If you start at the solution, the discussion argues the solution. If you start at the symptom, the discussion finds the right solution. Most failed issues blocks were misidentified at step one.
Every solve ends in one of these:
If the same issue shows up in five weekly syncs, the prior solve was wrong. Don't keep discussing the symptom. Admit the solve missed; address the root.
A recurring issue is signal that step 1 was wrong (you identified the symptom of a deeper symptom) or step 3 was weak (no real owner, no deadline, no follow-through).
Weekly sync issues block. Recurring problem. Two people who can't agree on a path. "We keep talking about this."
Pairs with weekly-sync (the meeting this loop lives inside) and decide from cklph-os (when a solve requires a one-way-door decision).
npx claudepluginhub chykalophia/cklph-marketplace --plugin cklph-eosProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.