From role-based-analyzer
Use when the user wants to analyze and document the current structure of a business field's workflow inside a company, as a precondition for process improvement. Conducts a structured interview covering Roles (Holacracy-style), Artifacts, and Meetings, then writes a single structured markdown report. Invoke with /role-based-analyzer. Use only for static structural analysis — does not cover dynamic relationships across dimensions, timing, or edge cases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/role-based-analyzer:role-based-analyzerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Invoke this skill when the user wants to understand and document the current structure of a business field within a company (e.g., "finance department", "HR onboarding process", "sales operations") before planning improvements.
Invoke this skill when the user wants to understand and document the current structure of a business field within a company (e.g., "finance department", "HR onboarding process", "sales operations") before planning improvements.
If an out-of-scope question arises during the interview, acknowledge it and note it can be explored in a separate session. Do not attempt to answer it within this skill.
-ing form. Each accountability is an ongoing action (e.g., "Reviewing budget submissions", "Maintaining the master schedule"). If the user describes one in another form, paraphrase it correctly and confirm.Meeting::Role must derive from a primary Role. A Meeting::Role is a meeting-specific manifestation of a primary Role. If a new role appears only in a meeting context, first capture it as a primary Role in Phase A, then reference it in Phase C.(not specified).Begin with a brief orientation:
"I'll guide you through a structured interview to capture the current structure of this business field across three dimensions: Roles, Artifacts, and Meetings. We'll go through them in order. You can say 'done' at any point when you've listed all entries for a dimension. Ready to start with Roles?"
Ask for the business field name first if not provided.
For each Role, ask these questions in sequence:
-ing form."
-ing form; rephrase gently if not, and confirm.After completing a Role, ask: "Is there another Role? Or are you done with Roles?"
When the user finishes Roles, ask: "Are there any roles that appear only inside specific meetings — not in the general workflow? We'll capture those as Meeting::Role entries in the Meetings phase."
Transition with: "Now let's capture the Artifacts — deliverables or submitted items involved in this business field, regardless of format."
For each Artifact, ask:
Artifact::part)After completing an Artifact, ask: "Is there another Artifact? Or are you done with Artifacts?"
Transition with: "Finally, let's capture the Meetings — structured gatherings that are part of this business field's workflow."
For each Meeting, ask:
Meeting::agenda-item entries)Meeting::Role entries; each must reference a primary Role from Phase A)
Meeting::Role, ask: "Which primary Role from our Phase A list does this correspond to?"After completing a Meeting, ask: "Is there another Meeting? Or are you done with Meetings?"
Once all three phases are complete, confirm with the user:
"I have all the information. Where should I save the report? (Default:
./<field-name>-analysis.md)"
Then write a single markdown file with this structure:
# <Business Field Name> — Structural Analysis
## Roles
### <Role Name>
- **Purpose:** <one-sentence ideal state>
- **Domain:**
- <exclusive area or asset>
- ...
- **Accountabilities:**
- <...ing ...>
- ...
---
## Artifacts
### <Artifact Name>
- **Format:** <digital / physical / either>
- **Description:** <brief description>
- **Parts:**
- <part name and brief description>
- ...
---
## Meetings
### <Meeting Name>
- **Requirement documents:**
- <document or data required for preparation>
- ...
- **Participants:** <criteria for who should attend>
- **Agenda items:**
- <step description>
- ...
- **Output documents:**
- <deliverable produced>
- ...
- **Meeting::Role:**
- `<Meeting-Role Name>` ← derived from `<Primary Role Name>`
- ...
Omit any optional sub-section (Parts, Meeting::Role) entirely if no entries were captured for it — do not leave empty bullets.
After writing the file, output a brief summary:
"Report saved to
<path>. Captured: N roles, M artifacts, K meetings. Please review and let me know if anything needs correction."
Do not add analysis, recommendations, or observations — this skill captures structure only.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub callas1900/-role-based-analyzer --plugin role-based-analyzer