agentleFS
Felpix-StudiosFelpix-Studios/social-science-research/skills/new-project/SKILL.md

new-project

Skill8 starsChanged 4 months agoMITView on GitHub

Start a new research project. Structured interview formalizes the idea; generates research questions with identification strategies and a project spec. Use when developing or documenting a new research idea, not searching literature or data.

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use checkpoint, prd and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • genomewalkerSkill

    checkpoint

    Save a checkpoint of task status, decisions, active files, and next steps

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • +1 more from getsentry

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask questions one or two at a time.

    line 24
  2. Distinctive:

    If after 3 exchanges the user keeps giving vague answers, move to Phase 2 anyway and flag the open questions.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

New Research Project

Formalize a research idea into a concrete project specification with testable hypotheses and empirical strategies.

Input: $ARGUMENTS — a topic, phenomenon, dataset, or "start fresh" for open-ended exploration.

This skill runs in three phases. Phase 1 is conversational — ask one or two questions at a time and wait for responses. Phases 2 and 3 run automatically after the interview.

For complex or ambiguous project-scoping requests, read ${CLAUDE_PLUGIN_ROOT}/skills/new-project/references/plan-first-workflow.md before Phase 1.

Phase 1: Research Interview

Goal: Draw out the researcher's thinking and establish a clear research question.

Ask questions one or two at a time. Build on each answer before moving to the next phase. Do NOT use AskUserQuestion — ask directly in your response. A good interview runs 4–6 exchanges.

Question Bank (select and adapt based on context)

The Puzzle (start here):

  • "What phenomenon or puzzle are you trying to understand?"
  • "What do you observe in the data / world that doesn't fit the standard explanation?"

Why It Matters:

  • "Why does this matter? Who should care about the answer?"
  • "Is there a policy lever here, or is this more about understanding a mechanism?"

Theoretical Motivation:

  • "What's your intuition for why X happens — what's the mechanism?"
  • "What would standard theory predict? Do you expect to find something different, and why?"

Data and Setting:

  • "Do you have data in mind, or are you open on the data source?"
  • "Is there a specific context, time period, country, or institutional setting you're focused on?"

Identification:

  • "Is there a natural experiment, policy change, or discontinuity you could exploit?"
  • "What's the biggest threat to a causal interpretation — what would a skeptic say?"

Expected Results + Contribution:

  • "What would you expect to find? What would genuinely surprise you?"
  • "What existing papers are closest to this? What gap does yours fill?"

When to Stop Interviewing

Move to Phase 2 when you have:

  • A clear research question (one sentence)
  • At least one plausible identification strategy
  • Some sense of what data exists or is needed
  • The motivation / contribution

If after 3 exchanges the user keeps giving vague answers, move to Phase 2 anyway and flag the open questions.

Phase 2: Research Ideation

Goal: Generate 3–5 structured research questions covering the full range from descriptive to causal.

Announce the transition: "Great — I have enough to generate a structured set of research questions. Let me build that out now."

Then generate 3–5 research questions ordered by type:

TypeWhat It Asks
DescriptiveWhat are the patterns? How has X evolved?
CorrelationalWhat factors are associated with X, controlling for Z?
CausalWhat is the causal effect of X on Y?
MechanismThrough what channel does X affect Y?
PolicyWould intervention X improve outcome Y?

For each RQ, develop:

  • Hypothesis — testable prediction with expected direction/magnitude
  • Identification Strategy:
    • Method (DiD, RDD, IV, synthetic control, etc.)
    • Treatment (what varies, when, where)
    • Control group (comparison units)
    • Key assumption (parallel trends, exclusion restriction, etc.)
    • Main robustness checks (pre-trends test, placebo, etc.)
  • Data requirements — what variables, time period, geography, unit of observation
  • Key pitfalls — 2 main threats to identification + mitigations
  • Related work — 2-3 papers using similar approaches (name only, no fabrication)

Rank the questions by feasibility × contribution:

RQFeasibilityContributionPriority
1HighHigh★★★
2HighMedium★★
............

Phase 3: Save Project Spec

Produce the unified project spec document and save it.

Save to: quality_reports/project_spec_[sanitized_topic].md

# Research Project: [Working Title]

**Date:** [YYYY-MM-DD]
**Researcher:** [from CLAUDE.md if available]


## Research Question

[Single clear sentence]

## Motivation

[2–3 paragraphs: why this matters, theoretical context, policy relevance, what the answer would change]

## Research Questions

### RQ1: [Question] — Priority: ★★★ (Feasibility: High / Contribution: High)

**Type:** Causal

**Hypothesis:** [Testable prediction with expected sign]

**Identification Strategy:**
- **Method:** [e.g., Staggered DiD with Sun–Abraham estimator]
- **Treatment:** [What varies and when]
- **Control group:** [Comparison units]
- **Key assumption:** [e.g., Parallel pre-trends conditional on controls]
- **Robustness:** [Pre-trends test, placebo outcomes, alternative control groups]

**Data Requirements:**
- [Dataset or data type needed]
- [Key variables: treatment proxy, outcome, controls]
- [Time period and geography]

**Key Pitfalls:**
1. [Threat + mitigation]
2. [Threat + mitigation]

**Related Work:** [Author (Year)], [Author (Year)]


[Repeat for RQ2–RQ5]


## Priority Empirical Strategy

[1 paragraph recommending the single highest-priority RQ and why, with the specific identification approach]

## Open Questions

[Issues raised in the interview that need further thought before committing to a strategy]


## Suggested Next Steps

1. **`/lit-review [topic]`** — Search the literature for related work and citation chains
2. **`/data-finder [topic]`** — Find and assess datasets for the priority RQ
3. Once data is secured: **`/data-analysis`** to begin analysis

After Saving

Tell the user:

  • The spec is saved to quality_reports/project_spec_[topic].md
  • Recommended next step: /lit-review [topic] to build the literature foundation
  • Then: /data-finder [topic] to identify and assess data sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.