feature-spec
/feature-spec
Podaje wytyczne do specyfikacji i planowania funkcji dla inżynierów: pisanie PRD, definiowanie wymagań, zarządzanie zakresem, priorytetyzacja i obsługa zmian.
- Autor
- pproenca ↗
- Repozytorium
- dot-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 15.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 48
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 15.08.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Podaje wytyczne do specyfikacji i planowania funkcji dla inżynierów: pisanie PRD, definiowanie wymagań, zarządzanie zakresem, priorytetyzacja i obsługa zmian.
Oryginalny opis (EN)
Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management.
Jak działa
- When to Apply
- Rule Categories by Priority
- Quick Reference
Podgląd SKILL.md
--- name: feature-spec description: Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management. --- # Software Engineering Feature Specification and Planning Best Practices Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success. ## When to Apply Reference these guidelines when: - Writing PRDs or feature specifications - Defining requirements or user stories - Managing scope and preventing scope creep - Prioritizing features and backlog items - Handling change requests - Aligning stakeholders on project goals ## Rule Categories by Priority | Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Scope Definition | CRITICAL | `scope-` | | 2 | Requirements Clarity | CRITICAL | `req-` | | 3 | Prioritization Frameworks | HIGH | `prio-` | | 4 | Acceptance Criteria | HIGH | `accept-` | | 5 | Stakeholder Alignment | MEDIUM-HIGH | `stake-` | | 6 | Technical Specification | MEDIUM | `tech-` | | 7 | Change Management | MEDIUM | `change-` | | 8 | Documentation Standards | LOW | `doc-` | ## Quick Reference ### 1. Scope Definition (CRITICAL) - `scope-define-boundaries` - Define explicit scope boundaries - `scope-document-assumptions` - Document all assumptions explicitly - `scope-work-breakdown` - Break scope into measurable work items - `scope-define-mvp` - Define MVP before full feature set - `scope-stakeholder-signoff` - Get stakeholder signoff on scope ### 2. Requirements Clarity (CRITICAL) - `req-specific-measurable` - Write specific, measurable requirements - `req-user-stories` - Structure requirements as user stories - `req-avoid-solution-language` - Avoid solution-specific language - `req-functional-nonfunctional` - Separate functional and non-functional - `req-consistent-terminology` - Use consistent terminology - `req-traceability` - Maintain requirements traceability ### 3. Prioritization Frameworks (HIGH) - `prio-moscow-method` - Use MoSCoW prioritization method - `prio-rice-scoring` - Apply RICE scoring for objectivity - `prio-value-vs-effort` - Map value vs effort explicitly - `prio-dependencies-first` - Identify and order dependencies - `prio-kano-model` - Apply Kano model for feature classification ### 4. Acceptance Criteria (HIGH) - `accept-given-when-then` - Use Given-When-Then format - `accept-testable-criteria` - Write testable acceptance criteria - `accept-edge-cases` - Include edge cases in acceptance - `accept-definition-of-done` - Define clear definition of done - `accept-avoid-over-specification` - Avoid over-specification ### 5. Stakeholder Alignment (MEDIUM-HIGH) - `stake-identify-stakeholders` - Identify all stakeholders early - `stake-early-feedback` - Gather feedback early and often - `stake-conflict-resolution` - Resolve conflicts explicitly - `stake-communication-plan` - Establish communication cadence - `stake-success-metrics` - Align on success metrics ### 6. Technical Specification (MEDIUM) - `tech-system-context` - Document system context and dependencies - `tech-api-contracts` - Define API contracts before implementation - `tech-data-model` - Specify data models and schema changes - `tech-error-handling` - Plan error handling and recovery - `tech-performance-requirements` - Specify performance requirements - `tech-security-considerations` - Document security considerations ### 7. Change Management (MEDIUM) - `change-formal-process` - Use formal change request process - `change-impact-assessment` - Assess full impact before approval - `change-version-tracking` - Version all specification documents - `change-scope-freeze` - Implement scope freeze periods - `change-defer-log` - Maintain deferred items log ### 8. Documentation Standards (LOW) - `doc-single-source` - Maintain single source of truth - `doc-consistent-templates` - Use consistent document templates - `doc-decision-records` - Document key decisions with context - `doc-accessible-format` - Keep documentation accessible - `doc-glossary-terms` - Define project terminology
Pliki w paczce (48)
- AGENTS.md 9 KB
- README.md 4 KB
- SKILL.md 4 KB
- metadata.json 1 KB
- assets/templates/_template.md 1 KB
- references/_sections.md 2 KB
- references/accept-avoid-over-specification.md 2 KB
- references/accept-definition-of-done.md 2 KB
- references/accept-edge-cases.md 2 KB
- references/accept-given-when-then.md 2 KB
- references/accept-testable-criteria.md 2 KB
- references/change-defer-log.md 5 KB
- references/change-formal-process.md 5 KB
- references/change-impact-assessment.md 4 KB
- references/change-scope-freeze.md 5 KB
- references/change-version-tracking.md 4 KB
- references/doc-accessible-format.md 4 KB
- references/doc-consistent-templates.md 4 KB
- references/doc-decision-records.md 4 KB
- references/doc-glossary-terms.md 5 KB
- references/doc-single-source.md 4 KB
- references/prio-dependencies-first.md 2 KB
- references/prio-kano-model.md 3 KB
- references/prio-moscow-method.md 2 KB
- references/prio-rice-scoring.md 2 KB
- references/prio-value-vs-effort.md 3 KB
- references/req-avoid-solution-language.md 2 KB
- references/req-consistent-terminology.md 2 KB
- references/req-functional-nonfunctional.md 2 KB
- references/req-specific-measurable.md 2 KB
- references/req-traceability.md 2 KB
- references/req-user-stories.md 2 KB
- references/scope-define-boundaries.md 2 KB
- references/scope-define-mvp.md 2 KB
- references/scope-document-assumptions.md 2 KB
- references/scope-stakeholder-signoff.md 2 KB
- references/scope-work-breakdown.md 2 KB
- references/stake-communication-plan.md 2 KB
- references/stake-conflict-resolution.md 2 KB
- references/stake-early-feedback.md 2 KB
- references/stake-identify-stakeholders.md 2 KB
- references/stake-success-metrics.md 2 KB
- references/tech-api-contracts.md 4 KB
- references/tech-data-model.md 6 KB
- references/tech-error-handling.md 5 KB
- references/tech-performance-requirements.md 4 KB
- references/tech-security-considerations.md 5 KB
- references/tech-system-context.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · pproenca/dot-skills | 90 | MIT |
| yxz1025/picoddy | 100 | MIT |
| yasunori0418/skills | 100 | MIT |
| lingegrace/claude-research-skills | 100 | MIT |
| Wafhi3n/dev-workflow-core | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki d467b0aa33eb (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100writing-feature-prds
Pisze PRD i specyfikację wymagań przed implementacją nowej funkcji, gdy użytkownik mówi o nowej funkcji albo prosi o PRD. - 84prd
Prowadzi przez pisanie PRD lub specyfikacji w czterech fazach: odkrycie, specyfikacja, plan i zadania. - 100prd
Prowadzi pisanie PRD jako kontraktu dla specyfikacji przekazywanych zespołom wdrożeniowym: zakres, granice i kryteria akceptacji, także z inwentarza funkcji do PRD per funkcja. - 90product-spec
Pisze PRD lub specyfikację funkcji na podstawie opisu pomysłu: historyjki, wymagania i zakres, gotowe do przekazania zespołowi. - 90product-requirements-document
Pisze przejrzysty dokument wymagań produktowych z problemem, zakresem, wymaganiami, miarami sukcesu, ryzykami i otwartymi pytaniami, na przykład PRD czy specyfikację dla inżynierów. - 100product-management
Wspiera zarządzanie produktem od pomysłu do premiery: zbieranie wymagań, user stories, priorytetyzację, strategię, PRD, definiowanie MVP i analizę konkurencji.