skill-name

النجوم٠

التفرعات٠

آخر تحديث٢٥ أبريل ٢٠٢٦ في ١٩:٥٨

Use when the user says /SKILL_NAME, "<trigger phrase>", or <situation that warrants this skill>. One sentence per trigger class — name WHEN to invoke, not WHAT the skill does. Do NOT use when <anti-trigger — situation where another skill or no skill fits better>. Avoid trigger overlap with existing skills (audit `skills/*/SKILL.md` per #73).

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

chriscantu

chriscantu/claude-config

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو الإدارةمهن الأعمال والعمليات المالية·SOC 13-1111

متخصصو التدريب والتطويرSOC 13-1151

مستكشف الملفات

3 ملفات

SKILL.md

readonly

name	SKILL_NAME
description	Use when the user says /SKILL_NAME, "<trigger phrase>", or <situation that warrants this skill>. One sentence per trigger class — name WHEN to invoke, not WHAT the skill does. Do NOT use when <anti-trigger — situation where another skill or no skill fits better>. Avoid trigger overlap with existing skills (audit `skills/*/SKILL.md` per #73).
status	experimental
version	0.1.0

One-paragraph statement of what this skill does and why it exists.

Announce at start: "I'm using the SKILL_NAME skill to ."

When to Use

<Trigger 1 — concrete user phrasing or situation>
<Trigger 2>

When NOT to Use

<Anti-trigger — situation where another skill or no skill fits better>

Procedure

→ verify:
→ verify:

Backtracking

If fails, return to and . Do not advance with a known-wrong shape.

References

Read on demand, not upfront:

المزيد من هذا المستودع

نفس المستودع

org-design

chriscantu/claude-config

Use when the user says /org-design <org>, "analyze the org I inherited", "inherited org analysis", "span of control / SPOF / on-call distribution review", or wants a descriptive read of the org structure they just walked into during a senior eng leader ramp. The analyze mode reads a manual org/structure.md + stakeholder memory graph into a 7-section analysis under ~/repos/onboard-<org>/decisions/. The scenario mode projects a reorg (split-team, add-headcount, merge-teams, change-reporting, reduce-headcount), validates it structurally, and gates on explicit user review before writing. reduce-headcount adds a machine layoff-acknowledgment gate (machine-enforced deliberateness; the human confirmation behind the flag is prose-bound, not machine-verified). Do NOT use for codebase architecture (use /architecture-overview).

2026-07-300

risk-register

chriscantu/claude-config

Use when the user says /risk-register, "add a risk", "review risks", "escalate R-N", "ack R-N", "resolve R-N", or "show my risk register" during a 90-day ramp or any initiative. Tracks org-level technical risks in any initiative workspace. Six actions: add, review, ack, escalate, resolve, list.

2026-07-300

strategy-doc

chriscantu/claude-config

Use when the user says /strategy-doc <org>, "draft my 90-day plan", "review the 90-day plan", or "challenge the 90-day plan" during a senior eng leader ramp. Phase 1 supports the 90-day-plan mode only — collates /swot + /stakeholder-map + /architecture-overview + free-form notes/*.md into a 7-section markdown artifact under ~/repos/onboard-<org>/decisions/. Cross-org RFC mode is Phase 2 (separate spec).

2026-07-300

glossary

chriscantu/claude-config

Use when the user explicitly invokes /glossary, asks to canonicalize a domain term in ./CONTEXT.md, or wants to record agreed-upon project-specific terminology so future sessions and downstream artifacts (ADRs, SDRs, systems-analysis output) stay consistent. Also invoked by define-the-problem and systems-analysis at end-of-skill via the caller-hook contract to offer canonicalization for terms resolved during planning. Write-only format-owner for per-project ./CONTEXT.md. Lazy-create on first term resolution; never auto-write — user approval gates every entry. Do NOT use for: casual term mentions in conversation, code-level naming questions, architectural primitives (Module, Interface, Adapter, Seam — those belong in LANGUAGE.md owned by architecture-overview), general programming concepts, or decisions about why a term was chosen (those belong in docs/superpowers/decisions/ or an ADR).

2026-07-230

ring-review-tiered

chriscantu/claude-config

Use when the user says /ring-review-tiered, "ring review these PRs", "antagonistic ring on this batch", "review PR #N with the ring", or asks to run adversarial / critic review across one or more pull requests. Calibrates critic count to per-PR risk tier — trivial PRs skip the ring, surgical PRs get one cross-dimension critic, medium PRs get two dimension-targeted critics, large/boundary/security PRs get the full 5-critic ring plus arbiter. Use even when the user names a uniform critic count — surface the tier and let them override. Do NOT use for solo single-PR review where the user explicitly asks for the full ring; that's `pr-review-toolkit:review-pr`.

2026-07-230

swot

chriscantu/claude-config

Use when the user says /swot, "landscape analysis", "SWOT analysis", "strengths and weaknesses", or wants to capture, review, or challenge organizational observations.

2026-07-230

name	SKILL_NAME
description	Use when the user says /SKILL_NAME, "<trigger phrase>", or <situation that warrants this skill>. One sentence per trigger class — name WHEN to invoke, not WHAT the skill does. Do NOT use when <anti-trigger — situation where another skill or no skill fits better>. Avoid trigger overlap with existing skills (audit `skills/*/SKILL.md` per #73).
status	experimental
version	0.1.0

One-paragraph statement of what this skill does and why it exists.

Announce at start: "I'm using the SKILL_NAME skill to ."

When to Use

<Trigger 1 — concrete user phrasing or situation>
<Trigger 2>

When NOT to Use

<Anti-trigger — situation where another skill or no skill fits better>

Procedure

→ verify:
→ verify:

Backtracking

If fails, return to and . Do not advance with a known-wrong shape.

References

Read on demand, not upfront: