Menu
Use when the core category has emerged and you need to delimit the theory by coding selectively around the core.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when writing academic prose for qualitative research — findings, methods, discussion sections with appropriate voice and conventions.
Use when conducting participatory action research (PAR) involving collaborative inquiry, cycles of action and reflection.
Use when formatting academic work in APA 7th edition style — citations, references, headings, tables, and manuscript structure.
Use when designing or conducting case study research following Yin's multiple case study methodology or Stake's approach.
Use when developing and densifying categories with properties, dimensions, conditions, and consequences.
Use when formatting academic work in Chicago/Turabian style — notes-bibliography or author-date systems.
| name | selective-coding |
| description | Use when the core category has emerged and you need to delimit the theory by coding selectively around the core. |
Selective coding begins when a core category has emerged and earned its place as the center of the developing theory. You shift from coding everything to coding only what develops the story that integrates the core category with major related categories (conditions, strategies, consequences, etc.).
Use this skill when your open coding and constant comparison suggest a central pattern, and you need to delimit scope while increasing theoretical density and integration.
It is:
It is not:
Glaser describes the core as the category that:
Ask:
If a candidate fails these tests, keep comparing—do not promote a core by fiat.
In many Glaserian studies, the core is a process: something participants do or work through over time (e.g., status passage, becoming, managing uncertainty).
Indicators you may be dealing with a BSP core:
Not every core must be a BSP, but if your data are strongly processual, gerund formulations often help.
Delimiting means you intentionally stop trying to code all possible interesting topics. Instead, you ask of each new incident:
“What does this contribute to the core and its integrated relationships?”
Document delimiting decisions in memos to preserve transparency.
Run a two-track week:
Selective coding clarifies what must be integrated. Theoretical coding (coding families) clarifies how categories relate (e.g., conditional, causal, strategy).
Sequence (typical in classic GT):
Avoid bolting on theoretical codes before substantive relationships are comparatively earned.
Provisional core category:
One-sentence core claim (hypothesis):
Main concern (if identifiable):
Primary related categories (list):
Negative cases queued for comparison:
What would falsify this core claim in upcoming data?
Source ID / location:
Why this excerpt matters to the core:
New properties/dimensions discovered (if any):
Revised relationship statements (if any):
Next sampling impulse (theoretical sampling note):
Revisit fit, work, relevance, modifiability:
open-coding, constant-comparison, memo-writingtheoretical-coding, theoretical-sampling, theoretical-saturationsubstantive-theory (write-up structure)