requirements-discovery
From the author
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.
Install
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a claude-code
Installs to .claude/skills/requirements-discovery/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 78
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- product-discoverymagnus919/agent-skillsDiscover product requirements from human stakeholders — map who to talk to, ask questions that surface hidden assumptions, detect gaps in real time, resolve conflicts, and translate conversations into structured SDD specs. Phase 0 upstream of Spec-Driven Development. Also grill a PRD, interrogate a proposal, poke holes in a spec, or interview its author about an existing draft, one consequential question at a time. Do not use for personal-life discovery (daily-life-discovery), general research without product requirements (research-methodology), or implementation planning.Science★ 148
- prd-developmentdeanpeters/Product-Manager-SkillsBuild a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.Planning★ 7.7K
- requirement-analysisfishzjp/qa-skillsModel a requirement/system: extract goals, scope, roles, rules, exceptions, dependencies from PRD, docs, bugs, code; outputs a structured model with clarifications. Not for: writing cases, strategy decisions, the pipeline. 建模需求/系统：从 PRD、文档、Bug、代码提炼目标/范围/角色/规则/异常/依赖。不用于：直接写用例、策略、流水线。Planning★ 50
- prdgithub/awesome-copilotGenerate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.Planning★ 40.4K
- deep-interviewtranhieutt/software_development_departmentConducts a structured technical deep-dive to gather detailed requirements, constraints, and decisions from the user. Use when starting a complex feature or when the user wants to be asked structured clarifying questions before implementation.Planning★ 74
- sdlc-draft-prdGulajavaMinistudio/awesome-copilot-idWorkflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.Planning★ 87
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in