en un clic
sdd-nestjs-svelte-boilerplate
sdd-nestjs-svelte-boilerplate contient 9 skills collectées depuis raphaelsasso, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Generates a Product Requirements Document (PRD) from a feature prompt. Use when planning a new feature, starting a project, or when asked to create a PRD. Don't use for technical specifications, task breakdowns, or implementation.
Breaks down a PRD and Tech Spec into an ordered list of implementable tasks. Use when PRD and Tech Spec are ready and the next step is planning the implementation sequence. Don't use for creating PRDs, writing specs, or implementing code.
Generates a Technical Specification from an existing PRD. Use when a PRD is ready and the next step is to define architecture, APIs, data models, and implementation strategy. Don't use for requirements gathering, task breakdown, or implementation.
Fixes all bugs listed in a bugs.md file with root-cause analysis and regression tests. Use after QA has identified bugs that need fixing. Don't use for new features, code review, or QA testing.
Performs Quality Assurance on implemented features including E2E testing, accessibility checks, and requirements verification. Use after implementation and code review are done. Don't use for code review, implementation, or bug fixing.
Performs a structured code review of implemented features against the PRD and Tech Spec. Use after tasks are implemented and code needs quality validation. Don't use for QA testing, bug fixing, or implementation.
Implements a single task from the task list, including code, tests, and checks. Use when tasks have been created and the next step is writing code. Don't use for creating PRDs, specs, task lists, or code review.
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
Reviews a completed task for code quality, spec adherence, and test coverage. Use after a task has been implemented via run-task. Don't use for full code review, QA, or implementation.