Agent Skills: requirements-discovery
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.
ID: nickcrew/claude-ctx-plugin/requirements-discovery
4114
Install this agent skill to your local
Skill Files
The files that make up requirements-discovery.
More agent skills
- oracleOracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
- data-analyst데이터 분석 전문가. pandas, numpy, 시각화, 통계 분석 지원.
- 1k-perf-optimizerDiagnose and optimize OneKey iOS startup and Wallet Home performance using timing metrics, call counts, profiling, and regression baselines.
- abridge-sdk-patternsImplement a narrow customer-owned adapter around an approved Abridge tenant interface without claiming a public SDK. Use when coding against vendor-issued integration specifications. Trigger with \"build the Abridge adapter\".
- agent-experienceAudit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'.
- tdd-workflowUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.