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.
Install
npx skills add pproenca/dot-skills --skill feature-specgit clone --depth 1 https://github.com/pproenca/dot-skills.git /tmp/dot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/dot-skills/skills/.experimental/feature-spec ~/.claude/skills/feature-specPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Details
- Skill name
feature-spec- Repository
- pproenca/dot-skills
- Path
skills/.experimental/feature-spec/SKILL.md- License
- MIT
- Repo updated
- 15 August 2026
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 the Feature Spec skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pproenca/dot-skills --skill feature-spec. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Feature Spec popular?
It lives in pproenca/dot-skills, which has 228 GitHub stars and 19 forks.
Related skills
12 Factor App
228pproenca/dot-skills
The Twelve-Factor App methodology for building scalable, maintainable cloud-native applications. Use when designing backend services, APIs, microservices, or any software-as-a-service application. Triggers on deployment patterns, configuration management, process architecture, logging, and infrastructure decisions.
37signals Rails
228pproenca/dot-skills
37signals Rails coding principles and conventions from DHH, Jorge Manrubia, and the Fizzy/Basecamp/HEY codebase. This skill should be used when writing, reviewing, or refactoring Ruby on Rails code following the 37signals philosophy — vanilla Rails, CRUD controllers, rich domain models, concerns, no service objects, Hotwire, Turbo, Stimulus, Solid Queue, Solid Cache, Solid Cable, multi-tenancy, Minitest, custom auth, or DHH conventions.
Acceptance Pipeline Catalog
228pproenca/dot-skills
Use when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing. Covers parser, JSON IR, generator, runtime, step handlers, test runner, mutator, value mutation rules, execution, result classification, reporting, project layout, conformance, and agent setup. Based on Uncle Bob's Acceptance Pipeline Specification. Trigger even when the user mentions Gherkin parsing, acceptance test generation, mutation testing for acceptance tests, or building a portable test pipeline.
Gitea Coordinator
191jwynia/agent-skills
Orchestrate multiple worker agents to implement groomed tasks in Gitea repositories. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work with Gitea. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous, gitea, tea.
Email Validator
150guia-matthieu/clawfu-skills
Validate and clean email lists. Use when: cleaning email lists before campaigns; validating signup emails; removing invalid addresses; checking for disposable emails; improving deliverability
Gitea Workflow
191jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.