Individual skill

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.

skills/.experimental/feature-spec/SKILL.md

Read pinned source

Source commit cf93c57cac89d6fc3e4194686000411567f5caf3

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 222
Repository last updated: Aug 15, 2026
License: MIT

Observed agent integration: codex

engineering Derived category
writing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

AGENTS.mddoc · 9,095 bytes
README.mddoc · 4,451 bytes
SKILL.mdcore · 4,411 bytes
SKILL.mdcore · 4,411 bytes
assets/templates/_template.mddoc · 596 bytes
metadata.jsonasset · 1,199 bytes
references/_sections.mddoc · 1,891 bytes
references/accept-avoid-over-specification.mddoc · 2,216 bytes
references/accept-definition-of-done.mddoc · 2,240 bytes
references/accept-edge-cases.mddoc · 2,337 bytes
references/accept-given-when-then.mddoc · 2,540 bytes
references/accept-testable-criteria.mddoc · 2,081 bytes
references/change-defer-log.mddoc · 4,957 bytes
references/change-formal-process.mddoc · 4,870 bytes
references/change-impact-assessment.mddoc · 4,444 bytes
references/change-scope-freeze.mddoc · 5,448 bytes
references/change-version-tracking.mddoc · 3,703 bytes
references/doc-accessible-format.mddoc · 4,072 bytes
references/doc-consistent-templates.mddoc · 4,051 bytes
references/doc-decision-records.mddoc · 4,556 bytes
references/doc-glossary-terms.mddoc · 4,752 bytes
references/doc-single-source.mddoc · 3,643 bytes
references/prio-dependencies-first.mddoc · 2,057 bytes
references/prio-kano-model.mddoc · 2,634 bytes
references/prio-moscow-method.mddoc · 2,092 bytes
references/prio-rice-scoring.mddoc · 2,047 bytes
references/prio-value-vs-effort.mddoc · 2,738 bytes
references/req-avoid-solution-language.mddoc · 2,150 bytes
references/req-consistent-terminology.mddoc · 2,404 bytes
references/req-functional-nonfunctional.mddoc · 2,229 bytes
references/req-specific-measurable.mddoc · 1,901 bytes
references/req-traceability.mddoc · 2,344 bytes
references/req-user-stories.mddoc · 2,123 bytes
references/scope-define-boundaries.mddoc · 1,542 bytes
references/scope-define-mvp.mddoc · 1,948 bytes
references/scope-document-assumptions.mddoc · 1,929 bytes
references/scope-stakeholder-signoff.mddoc · 2,026 bytes
references/scope-work-breakdown.mddoc · 1,970 bytes
references/stake-communication-plan.mddoc · 2,308 bytes
references/stake-conflict-resolution.mddoc · 2,469 bytes
references/stake-early-feedback.mddoc · 2,237 bytes
references/stake-identify-stakeholders.mddoc · 2,552 bytes
references/stake-success-metrics.mddoc · 2,381 bytes
references/tech-api-contracts.mddoc · 3,792 bytes
references/tech-data-model.mddoc · 6,001 bytes
references/tech-error-handling.mddoc · 5,443 bytes
references/tech-performance-requirements.mddoc · 4,585 bytes
references/tech-security-considerations.mddoc · 4,885 bytes
references/tech-system-context.mddoc · 5,413 bytes

Read excerpt


# 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