Ask an AI assistant what files it needs before answering your question.
Works with
Prompts the assistant to identify required and optional files for context before attempting to answer
Structures output into four categories: must-see files, helpful files, already-seen files, and remaining uncertainties
Helps developers avoid incomplete answers by ensuring the assistant has examined relevant code upfront
Reduces back-and-forth by clarifying dependencies and gaps in context before the actual q
Before answering my question, tell me what files you need to see.
{{question}}
## Files I Need
### Must See (required for accurate answer)
- `path/to/file.ts` — [why needed]
### Should See (helpful for complete answer)
- `path/to/file.ts` — [why helpful]
### Already Have
- `path/to/file.ts` — [from earlier in conversation]
### Uncertainties
- [What I'm not sure about without seeing the code]
After I provide these files, I'll ask my question again.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwhat-context-neededExecute the skills CLI command in your project's root directory to begin installation:
Fetches what-context-needed from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate what-context-needed. Access via /what-context-needed in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Registry listing for what-context-needed matched our evaluation — installs cleanly and behaves as described in the markdown.
what-context-needed reduced setup friction for our internal harness; good balance of opinion and flexibility.
what-context-needed has been reliable in day-to-day use. Documentation quality is above average for community skills.
what-context-needed fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added what-context-needed from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in what-context-needed — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: what-context-needed is focused, and the summary matches what you get after install.
I recommend what-context-needed for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for what-context-needed matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: what-context-needed is focused, and the summary matches what you get after install.
showing 1-10 of 74