Stats
Actions
Tags
From skills-for-humanity
Identifies recurring cycles (hype, adoption, economic) and maps current position to predict next phase. Useful for strategic analysis and pattern detection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-temporal-cycle-detectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every situation that feels unprecedented is usually an instance of a recurring cycle. Knowing your position in the cycle tells you what phase is coming, what actions are appropriate now versus premature, and which signals indicate divergence from the typical pattern — the most important signal of all. Acting as if a situation is unique when it is not forfeits the pattern's predictive value.
Every situation that feels unprecedented is usually an instance of a recurring cycle. Knowing your position in the cycle tells you what phase is coming, what actions are appropriate now versus premature, and which signals indicate divergence from the typical pattern — the most important signal of all. Acting as if a situation is unique when it is not forfeits the pattern's predictive value.
Step 1: Describe Current State and Trajectory State what is happening now and how the situation has moved over the past period. Include: rate of change, sentiment, who is entering or exiting, resource flows, expectations.
Framing check: Confirm the specific situation before continuing. State what you've identified — the actual phenomenon or domain being analyzed and its key observable parameters — in one sentence, then use AskUserQuestion:
Step 2: Match to a Candidate Cycle Compare against the most common cycles:
Step 3: Map Current Position Place the situation on the curve. Be specific about which phase and where within the phase (early, mid, late).
Step 4: Identify Phase Signs List the characteristic indicators of this phase. Which are present? Which are absent? Absent expected signs are as informative as present ones.
Step 5: State the Typical Next Phase What normally follows this phase? What are the leading indicators that the transition has begun?
Step 6: Note Divergences Where does this situation differ from the typical cycle? These divergences — not the pattern itself — are the most important signals. They indicate either a different cycle applies or this instance will unfold differently.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Cycle Match: [cycle name] — [why it fits]
Current Position: [phase name] — [early / mid / late within phase]
Phase Signs
| Expected Sign for This Phase | Present? |
|---|---|
Typical Next Phase: [name + leading indicators of transition]
Divergences: [where this instance differs from the typical pattern + what that implies]
Implications: [what actions are appropriate now vs. premature vs. overdue]
If no cycle fits well, that is itself a finding — either the situation is genuinely novel or it requires a composite of two cycles. Name the mismatch explicitly rather than forcing a fit.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-historical-cycle-detection — Look for historical evidence that confirms the cycles/s4h-temporal-timing-analysis — Time actions to the detected cycles/s4h-strategy-timing — Align strategy with the cycle timingnpx claudepluginhub human-avatar/skills-for-humanityIdentifies which recurring cycle a situation belongs to and where you are in it. Triggered by questions like 'what cycle is this' or 'is this a bubble'.
Analyzes software component evolution stages (Genesis to Commodity) and Wardley climatic patterns for planning, design, and best practices guidance.
Uses feedback loop analysis to diagnose why a system grows uncontrollably, oscillates, or resists change. Identifies dominant loops and delays.