grad-phenomenology
Apply phenomenological methods including bracketing (epoche), lived experience inquiry, and Interpretive Phenomenological Analysis (IPA) to uncover the essence of human experience. Use this skill when the user needs to study how people experience a phenomenon from the first-person perspective, apply Husserlian descriptive or Heideggerian interpretive phenomenology, conduct IPA with idiographic focus, or when they ask 'what is the lived experience of X', 'how do I bracket my assumptions', or 'how do I do IPA'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/grad-phenomenology”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/grad-phenomenologymetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
74 words · 514 chars — "Apply phenomenological methods including bracketing (epoche), lived experience i…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 74 words.
Documentation present and substantive
Documentation present (SKILL.md, 816 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Overview
Phenomenology is a qualitative methodology that seeks to describe and understand the essence of lived experience as perceived by those who experience it. Rooted in Husserl's philosophy, the researcher suspends (brackets) preconceptions to let the phenomenon reveal itself. Two major traditions exist: descriptive phenomenology (Husserl, Moustakas) focuses on essential structures, while interpretive phenomenology (Heidegger, van Manen) and IPA (Smith) emphasize hermeneutic interpretation of meaning-making.
When to Use
- Understanding the essential structure of a lived experience (e.g., grief, learning, chronic illness)
- Exploring "what is it like to experience X?" from first-person perspectives
- When existing theories do not capture the experiential dimension of a phenomenon
- When idiographic depth (individual meaning-making) is valued over population-level patterns
When NOT to Use
- When the research question is about behavior, systems, or processes rather than experience
- When the phenomenon has not been experienced by the participants firsthand
- When causal explanation or prediction is required
- When the researcher cannot bracket their assumptions (e.g., strong advocacy stance)
Assumptions
IRON LAW: Phenomenology studies LIVED EXPERIENCE as described by those
who live it — the researcher's theoretical preconceptions must be
bracketed (epoche). If you impose your framework on participants'
experience, you are doing thematic analysis, NOT phenomenology.
Key assumptions:
- Consciousness is always consciousness OF something (intentionality)
- Lived experience has an essential structure that can be described
- The researcher must suspend the natural attitude through epoche (bracketing)
- Meaning is constituted through the relationship between person and phenomenon
Methodology
Step 1: Identify the Phenomenon and Bracket Preconceptions
Define the phenomenon precisely. Conduct epoche — write down all presuppositions, theories, and expectations about the phenomenon, then consciously set them aside. In IPA, acknowledge that bracketing is partial and iterative.
Step 2: Collect Experiential Descriptions
Conduct in-depth interviews with individuals who have lived the experience. Use open questions: "Tell me about your experience of X." Aim for rich, detailed, first-person descriptions. Sample size: descriptive phenomenology 5-25; IPA typically 3-6 for idiographic depth.
Step 3: Analyze for Meaning Structures
Descriptive (Moustakas/Colaizzi): Extract significant statements, formulate meanings, cluster into themes, produce textural and structural descriptions, synthesize the essence.
IPA (Smith): Read and re-read each transcript. Note initial observations. Develop emergent themes per case. Search for connections across themes. Move to next case. Identify patterns across cases while preserving idiographic detail.
Step 4: Describe the Essence
Write a composite description of the phenomenon's essential structure — the invariant features without which the experience would not be what it is. In IPA, present a narrative that weaves individual voices with interpretive commentary.
Output Format
## Phenomenological Analysis: [Experience]
### Phenomenon
- Definition: [the experience studied]
- Participants: [N, selection criteria]
- Approach: [descriptive / interpretive / IPA]
### Bracketing Statement
- Researcher preconceptions: [listed and suspended]
### Essential Themes
| Theme | Textural Description (What) | Structural Description (How) |
|-------|---------------------------|----------------------------|
| [theme] | [what was experienced] | [how it was experienced] |
### Essence Statement
> [A composite description capturing the invariant structure of the experience — what makes this experience THIS experience and not something else]
### Individual Voices (IPA)
| Participant | Unique Contribution | Illustrative Quote |
|-------------|--------------------|--------------------|
| [pseudonym] | [what this case adds] | [direct quote] |
### Implications
1. [What this reveals about the phenomenon]
2. [How the essence challenges or enriches existing understanding]
Gotchas
- Epoche does NOT mean the researcher has no perspective — it means they consciously reflect on and suspend it
- Do NOT conflate phenomenology with thematic analysis — phenomenology seeks essences, not just themes
- IPA involves a "double hermeneutic": the researcher interprets the participant's interpretation of their experience
- Descriptive and interpretive phenomenology have different philosophical foundations — do not mix them carelessly
- Small sample sizes are intentional — depth trumps breadth in phenomenological research
- The essence is not a summary of common themes; it is the invariant structure that defines the experience
References
- Moustakas, C. (1994). Phenomenological Research Methods. Sage.
- Smith, J. A., Flowers, P., & Larkin, M. (2022). Interpretive Phenomenological Analysis: Theory, Method and Research (2nd ed.). Sage.
- van Manen, M. (2016). Researching Lived Experience: Human Science for an Action Sensitive Pedagogy (2nd ed.). Routledge.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/grad-phenomenology