Ask an AI assistant what files it needs before answering your question.
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
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
Submit your Claude Code skill and start earning
epx add github/awesome-copilot --skill what-context-neededCompatible with
Supported agents
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
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:
epx add github/awesome-copilot --skill what-context-neededFetches 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:
.cursor/skills/what-context-needed
Restart Cursor to activate what-context-needed. Access via /what-context-neededin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
premium-frontend-ui
github/awesome-copilot · Frontend · same repo
java-springboot
github/awesome-copilot · Backend · same repo
framer-motion
pproenca/dot-skills · Productivity · same category
find-skills
kimyx0207/findskill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
network-engineer
404kidwiz/claude-supercode-skills · Productivity · same category
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