issue_requirements
Skill21 starsChanged 3 months agoMITView on GitHub
Refocus discussion on open requirements and feature questions
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-workspaceword for word, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 1
- MarcusJellinghaus/mcp-workspace★ 49100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- commit_pushSkill
- discussSkill
- implementation_approveSkill
- implementation_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement_directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- issue_createSkill
- issue_updateSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- rebaseSkill
The file
We split this skill 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
- Distinctive: line 16
Questionable decisions: If any existing decision seems risky or worth revisiting given what you've seen in the code, briefly note why.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.
Files
Issue Requirements
Refocus the conversation on open requirements after /issue_analyse has explored the issue and codebase.
Instructions
Review the conversation so far and produce a structured summary:
- Decided items: List what was already decided (from the issue's
## Decisionssection and the current conversation). Do not re-ask these. - Questionable decisions: If any existing decision seems risky or worth revisiting given what you've seen in the code, briefly note why. Don't block on it — just flag it.
- Open requirements / feature questions: List only the remaining open questions that affect requirements or user-facing behavior. Implementation details are yours to decide — do not ask about them.
- Constraints & rationale identified: List any non-obvious constraints or gotchas discovered during analysis (the "why" behind decisions, things downstream steps need to know).
Suggested next step: /discuss — to walk through the open questions one by one.
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
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.

