| 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 boundariesscope-document-assumptions - Document all assumptions explicitlyscope-work-breakdown - Break scope into measurable work itemsscope-define-mvp - Define MVP before full feature setscope-stakeholder-signoff - Get stakeholder signoff on scope
2. Requirements Clarity (CRITICAL)
req-specific-measurable - Write specific, measurable requirementsreq-user-stories - Structure requirements as user storiesreq-avoid-solution-language - Avoid solution-specific languagereq-functional-nonfunctional - Separate functional and non-functionalreq-consistent-terminology - Use consistent terminologyreq-traceability - Maintain requirements traceability
3. Prioritization Frameworks (HIGH)
prio-moscow-method - Use MoSCoW prioritization methodprio-rice-scoring - Apply RICE scoring for objectivityprio-value-vs-effort - Map value vs effort explicitlyprio-dependencies-first - Identify and order dependenciesprio-kano-model - Apply Kano model for feature classification
4. Acceptance Criteria (HIGH)
accept-given-when-then - Use Given-When-Then formataccept-testable-criteria - Write testable acceptance criteriaaccept-edge-cases - Include edge cases in acceptanceaccept-definition-of-done - Define clear definition of doneaccept-avoid-over-specification - Avoid over-specification
5. Stakeholder Alignment (MEDIUM-HIGH)
stake-identify-stakeholders - Identify all stakeholders earlystake-early-feedback - Gather feedback early and oftenstake-conflict-resolution - Resolve conflicts explicitlystake-communication-plan - Establish communication cadencestake-success-metrics - Align on success metrics
6. Technical Specification (MEDIUM)
tech-system-context - Document system context and dependenciestech-api-contracts - Define API contracts before implementationtech-data-model - Specify data models and schema changestech-error-handling - Plan error handling and recoverytech-performance-requirements - Specify performance requirementstech-security-considerations - Document security considerations
7. Change Management (MEDIUM)
change-formal-process - Use formal change request processchange-impact-assessment - Assess full impact before approvalchange-version-tracking - Version all specification documentschange-scope-freeze - Implement scope freeze periodschange-defer-log - Maintain deferred items log
8. Documentation Standards (LOW)
doc-single-source - Maintain single source of truthdoc-consistent-templates - Use consistent document templatesdoc-decision-records - Document key decisions with contextdoc-accessible-format - Keep documentation accessibledoc-glossary-terms - Define project terminology
