requirements-specification
De la autor
Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.
Instalare
npx skills add nicepkg/ai-workflow --skill requirements-specification -a claude-code
Se instalează în .claude/skills/requirements-specification/ · 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
- Include scripturi pe care nu le-am verificatScăzut
De ce 72
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.
- project-specificationathola/claude-night-marketTransforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.Planificare★ 343
- specification-writinga5c-ai/babysitterWrite feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.Redactare★ 1.9K
- feature-specw95/awesome-claude-corporate-skillsWrite detailed feature specifications with functional requirements, edge cases, data models, API contracts, and UX flows. Create comprehensive technical specifications that enable clear implementation.Planificare★ 285
- specification-generationa5c-ai/babysitterConvert requirements into structured technical specifications with architecture decisionsPlanificare★ 1.9K
- spechashgraph-online/awesome-codex-pluginsSpec phase. Converts user requirements into a numbered Requirements + Acceptance Criteria document saved as SPEC-{timestamp}.md. Prompts /team suggestion when 3+ requirements are detected.Planificare★ 1.4K
- 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.2K
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