requirement-analysis
De la autor
Model 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、代码提炼目标/范围/角色/规则/异常/依赖。不用于：直接写用例、策略、流水线。
Instalare
npx skills add fishzjp/qa-skills --skill requirement-analysis -a claude-code
Se instalează în .claude/skills/requirement-analysis/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 82
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- requirementdoccker/cc-use-exp结构化需求分析工作流，适用于显式 requirement doc 与 interrogate 场景；不负责技术设计、bug 修复或正式代码审查。Planificare★ 1.1K
- product-requirementscbrock84/headcountWrites down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried. Use this to write a specification, review one that is causing rework, or work out why a delivered feature technically matched the request and still was not what anyone wanted.Planificare★ 2.1K
- requirements-discoveryNickCrew/Claude-CortexStakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.Planificare★ 61
- business-modelsandbaseai/sandbase-skillsCreate or review business model deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for business model planning or analysis.Planificare★ 203
- requirement-convergenceshinpr/claude-code-workflowsSeparates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from decision-relevant repository evidence. Use when a requirement enters a workflow, before design begins.Planificare★ 704
- 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.Planificare★ 40.4K
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te