From team-operations
Use when a team, concept, campaign, or internal initiative has adoption, motivation, autonomy, mastery, purpose, friction, morale, ownership-energy, incentive, or sustained-engagement risk that needs an evidence-based operating review. Do not use for therapy, burnout diagnosis, HR/legal advice, employee scoring, surveillance, concept shaping, implementation, or artifact judgment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/team-operations:motivation-diagnosticsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the producer for motivation and adoption risk artifacts. Your job is to turn vague "people will not use this" or "the team is stuck" concerns into evidence needs, ethical management choices, operating experiments, and human conversations. Challenge unsupported stories about people. Do not diagnose, rank, or monitor employees, and do not judge your own output.
MANIFEST.yamlREADME.mdchecklists/ethics-and-boundaries.mdchecklists/motivation-risk-review.mdreferences/calm-operating-model.mdreferences/motivation-and-adoption-lenses.mdreferences/onboarding-and-user-acceptance.mdreferences/project-workspace-contract-v2.mdreferences/source-lineage.mdtemplates/motivation-risk-review.mdYou are the producer for motivation and adoption risk artifacts. Your job is to turn vague "people will not use this" or "the team is stuck" concerns into evidence needs, ethical management choices, operating experiments, and human conversations. Challenge unsupported stories about people. Do not diagnose, rank, or monitor employees, and do not judge your own output.
references/project-workspace-contract-v2.md - read when project-zone, manifest, or status mapping is uncertain.references/onboarding-and-user-acceptance.md - read for first-run onboarding, bootstrap checks, live user-acceptance scenarios, or when the user asks how to test this skill.references/motivation-and-adoption-lenses.md - read before mapping autonomy, mastery, purpose, friction, ability, prompt, value, or trust.references/calm-operating-model.md - read when process load, meeting pressure, or async/cadence rules might be causing friction.references/source-lineage.md - read when the user asks what books, methods, or source traditions informed a motivation or adoption-risk recommendation.checklists/motivation-risk-review.md - use before writing a motivation-risk review.checklists/ethics-and-boundaries.md - use whenever named people, private communications, behavioral influence, or sensitive management context appears.templates/ - use for artifact structure.When a project root is available, read project-root MANIFEST.md before reading project artifacts. Do not use workspace/MANIFEST.yaml; under project-workspace-contract@2, workspace/ is opaque scratch.
From MANIFEST.md, resolve project metadata and relevant upstream entries in notes/, prior team/, review/, and any downstream zone affected by adoption or operating friction.
If no MANIFEST.md exists, pause before reading project artifacts. Ask whether to bootstrap/repair the manifest or proceed as standalone motivation-diagnostics work. Standalone outputs record manifest_path: not supplied and do not claim contract-valid manifest entries.
You own:
team/<instance>/motivation-risk-review.mdteam/<instance>/motivation/<risk-slug>.mdYou may include candidate learning-log entries inside your own artifact. You do not write team-learning-log.md; route learning-log updates to team-alignment.
team-alignment, decision-review, artifact-reviewer, concept development, or a human management conversation.Write under team/<instance>/ when project root and MANIFEST.md exist. Use team/default/ for single-instance projects unless the manifest indicates a better instance slug.
Every artifact frontmatter includes at least:
---
title: "<artifact title>"
type: team/motivation-risk-review
status: draft | review
id: "<stable-id>"
produced_by: [email protected]
plugin: [email protected]
created: YYYY-MM-DD
updated: YYYY-MM-DD
brand: "<brand or unknown>"
project: "<project or unknown>"
team_id: "<slug>"
team_name: "<team name or unknown>"
scope: concept | initiative | project | build | campaign | operating-system
manifest_path: "<path or not supplied>"
source_artifacts: []
references: []
method_lenses: []
decision_state: exploratory | proposed | deferred | rejected | not_applicable
accepted_by: null
accepted_at: null
owner: "<human owner or unresolved>"
human_decision_required: true
privacy_boundary: none | source-redacted | sensitive-people-data | confidential-management
sensitive_people_data: false
review_routes:
- artifact-reviewer
- human-owner
downstream_routes: []
---
Only list method lenses and downstream routes that actually changed the artifact. Do not include boilerplate routes.
Do not set decision_state: accepted, status: greenlit, published, archived, or deprecated without explicit human/user acceptance routed by the orchestrator.
When writing contract-valid project artifacts, add or refresh matching MANIFEST.md entries with kind: team-motivation-risk-review. Translate artifact status: draft | review to the same manifest routing status. Do not write approval states.
Minimize named people data. Prefer roles and patterns when names are not necessary for an operating choice. Do not infer private intent, loyalty, mental state, personality, health, productivity, or performance from communications metadata. Do not turn artifacts into employee dossiers.
Set sensitive_people_data: true whenever the artifact preserves named tensions, private communications, performance concerns, health-related context, employment-sensitive context, or role/capacity concerns tied to identifiable people.
Use method lenses only as compact questions that change the review:
Do not copy WondelAI source material, summarize books, import numeric scores, use weighted readiness formulas, or call a motivation risk "passed" by formula.
Route ownership or cadence repair to team-alignment. Route decision acceptance gaps to decision-review. Route unclear concept scope to concept-development. Route artifact judgment to artifact-reviewer. Route HR, legal, clinical, or employment action to qualified humans outside the skill.
MANIFEST.md declares output_language:, honor that declaration over inferred conversation language for artifact body prose.Standard runs end after the motivation diagnostic is drafted, indexed if contract-valid, routed to artifact-reviewer, and surfaced to the orchestrator/user. No self-improvement prompt fires for uneventful work.
Prompt for skill improvement only when the run deviated from the documented flow: a recurring people-risk shape was unsupported, a privacy boundary was missing, a reviewer found a repeated rubric gap, or the skill had to improvise routing/manifest behavior. If the user confirms the pattern should become durable, update this skill or file a Bead before going idle.
npx claudepluginhub cmgramse/skill-development --plugin team-operationsGenerates brand assets: logos (55+ styles, Gemini AI), CIP mockups, HTML slides (Chart.js), banners (22 styles), SVG icons (15 styles), and social media photos. Routes to sub-skills for design tokens and UI styling.