feature-spec
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.
- Installs
- 427
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pproenca/dot-skills --skill feature-spec- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads feature-spec automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
FAQ
What does the feature-spec skill do?
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.
How do I install feature-spec?
Run npx skills add https://github.com/pproenca/dot-skills --skill feature-spec in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/feature-spec/ (personal) or .claude/skills/feature-spec/ (project).
Which AI agents can use feature-spec?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is feature-spec safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains feature-spec?
It is published by pproenca in pproenca/dot-skills. It has 427 recorded installs.
More from pproenca/dot-skills
zod
pproenca/dot-skills
Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).
vitest
pproenca/dot-skills
Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
react-hook-form
pproenca/dot-skills
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, the subscribe() API, and the Watch / FormStateSubscribe / FieldArray render-prop components. Covers RHF 7.82 additions including resetDefaultValues() and the disabled field-array option. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).
emilkowal-animations
pproenca/dot-skills
Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.
nuqs
pproenca/dot-skills
nuqs (type-safe URL query state) best practices for Next.js and other React frameworks. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, limitUrlUpdates, Standard Schema, NuqsAdapter, or Next.js routing with state.
clean-architecture
pproenca/dot-skills
Clean Architecture principles and best practices from Robert C. Martin's book. This skill should be used when designing software systems, reviewing code structure, or refactoring applications to achieve better separation of concerns. Triggers on tasks involving layers, boundaries, dependency direction, entities, use cases, or system architecture.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.