orgsci-theory-development
Use when building or sharpening the theory for an Organization Science manuscript — articulating the organizational mechanism, bridging micro-macro levels, and deciding between a priori deductive theorizing and inductive grounded theory building. Develops the theory; it does not frame the contribution statement (orgsci-contribution-framing) or run the analysis (orgsci-data-analysis).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-theory-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Theory Development (orgsci-theory-development) ## When to trigger - Your hypotheses or propositions are descriptive ("A relates to B") with no organizational mechanism - You have rich inductive data and need to build, not test, theory - A reviewer says "what is the theoretical engine?" or "the levels are conflated" - You need to bridge micro behavior and macro structure explicitly ## Two legitimate modes — pick deliberately Organization Science is **theory-driven** but methodologically eclectic, so theory can be built two ways and the journal respects both: - **Deductive / a priori.** State the organizational construct relationships, derive the mechanism from organization theory, and articulate testable propositions or hypotheses before the data. Make the mediating mechanism and the boundary conditions explicit. - **Inductive / grounded.** When the contribution is a new process or construct, build theory up from data. Aim for an abstracted process model or a grounded set of propositions — not a description. The journal's signature openness to qualitative and inductive work means this is a first-class path, not a fallback. ## Build the mechanism, not just the relationship - **Name
- When to trigger
- Two legitimate modes — pick deliberately
- Build the mechanism, not just the relationship
- Anti-patterns
- Theory pass for Organization Science
- Output format
What does the orgsci-theory-development skill do?
Use when building or sharpening the theory for an Organization Science manuscript — articulating the organizational mechanism, bridging micro-macro levels, and deciding between a priori deductive theorizing and inductive grounded theory building. Develops the theory; it does not frame the contribution statement (orgsci-contribution-framing) or run the analysis (orgsci-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-theory-development --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.