Apply Grounded Theory (Glaser and Strauss) to build theory inductively from qualitative data through open, axial, and selective coding. Use this skill when the user needs to develop new theory from data rather than test existing hypotheses, conduct theoretical sampling and constant comparison, determine when theoretical saturation is reached, or when they ask 'what theory explains this phenomenon', 'how do I code qualitative data systematically', or 'when do I stop collecting data'.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-grounded-theory
Grounded Theory is a systematic methodology for constructing theory that is grounded in qualitative data. Through iterative cycles of data collection, coding, and comparison, the researcher develops concepts and categories that ultimately form an explanatory theory. The method was originally developed by Glaser and Strauss (1967) and later diverged into Glaserian (emergent) and Straussian (structured) variants.
IRON LAW: In grounded theory, theory EMERGES from data — imposing a
pre-existing framework violates the methodology's core principle. If
you begin with a hypothesis and seek confirmation, you are NOT doing
grounded theory.
Key assumptions:
Break data into discrete incidents, events, or ideas. Assign initial codes (labels) to each segment. Use in-vivo codes (participants' own words) where possible. Generate as many codes as the data warrant — do not filter prematurely.
Group open codes into higher-order categories. Identify relationships between categories using the coding paradigm: conditions, actions/interactions, and consequences. Build subcategories that specify when, where, why, and how a category manifests.
Identify the core category — the central phenomenon around which all other categories integrate. Systematically relate all categories to the core category. Write a storyline that narrates the theory.
Refine the theory through constant comparison. Validate against the data. Produce a substantive theory with defined concepts, propositions, and boundary conditions. Report the audit trail of coding decisions.
## Grounded Theory Analysis: [Context]
### Core Category
- Central phenomenon: [the core category label]
- Definition: [what it means in this context]
### Category Structure
| Category | Properties | Dimensions | Relationship to Core |
|----------|-----------|------------|---------------------|
| [name] | [key properties] | [range/variation] | [how it relates] |
### Coding Paradigm
- **Causal conditions**: [what leads to the phenomenon]
- **Context**: [specific conditions shaping action]
- **Intervening conditions**: [broader structural conditions]
- **Action/Interaction strategies**: [how actors respond]
- **Consequences**: [outcomes of action/interaction]
### Theoretical Propositions
1. [Proposition linking categories]
2. [Proposition linking categories]
### Saturation Evidence
- Categories saturated: [list]
- Data sources: [count and type]
- Point of saturation: [when no new properties emerged]
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun.
You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.
Take asgard-ai-platform/grad-grounded-theory from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.