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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfeature-specExecute the skills CLI command in your project's root directory to begin installation:
Fetches feature-spec from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate feature-spec. Access via /feature-spec in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
95
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
95
stars
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.
Reference these guidelines when:
| 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- |
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 scopereq-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 traceabilityprio-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 classificationaccept-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-specificationstake-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 metricstech-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 considerationschange-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 logdoc-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 terminologyMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
pproenca/dot-skills
pproenca/dot-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added feature-spec from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend feature-spec for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
feature-spec reduced setup friction for our internal harness; good balance of opinion and flexibility.
feature-spec fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: feature-spec is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in feature-spec — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for feature-spec matched our evaluation — installs cleanly and behaves as described in the markdown.
feature-spec is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: feature-spec is focused, and the summary matches what you get after install.
Useful defaults in feature-spec — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 33