agentleFS
KonHKonH/GlobalStrategy/.cursor/rules/issue-clarification-questions.mdc

GlobalStrategy / rules

Cursor rule3 starsChanged 2 months agoMITView on GitHub

Format for clarification questions posted in GitHub issue/PR handoff comments

The file

We split this issue-clarification-questions.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    When asking the owner for decisions on a GitHub issue or PR, put the questions in the handoff comment itself.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “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
issue-clarification-questions.mdc
---
description: Format for clarification questions posted in GitHub issue/PR handoff comments
alwaysApply: true
---

# Clarification Questions in Issue / PR Comments

When asking the owner for decisions on a GitHub issue or PR, put the questions in the handoff comment itself.

## Required format

1. **Always write the questions in the comment** — do not only point at a spec Ambiguities section or say “open clarifications remain.”
2. **Number them `0`–`9` (then `10+`)** so the owner can answer with `N: answer`.
3. **Show the full question text** for each item, with enough context to decide without opening another file. Assumed defaults may follow in parentheses.

## Anti-patterns

- Abbreviated titles only (“influence definition”, “FIFO vs merge”)
- “See spec Ambiguities” without repeating the questions
- Unnumbered bullets the owner cannot cite

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.