Generate Comprehensive Feature Documentation

This skill produces comprehensive, user-focused feature documentation spanning technical specs, user guides, API references, and cross-functional communication. Its content framework structures every feature doc into four layers: an overview (purpose, target users, key benefits), how it works (core functionality, user flow, system integration), implementation (technical requirements, configuration, code examples), and a reference section (parameters, error handling, performance limitations). Structure follows purpose-first organization, progressive disclosure from overview to implementation detail, multiple entry points for end-users, developers, and stakeholders, and cross-references to related features and prerequisites.

Use it when documenting a feature for multiple audiences at once - end-users, developers, and stakeholders - not a single narrow API reference. It is not meant to duplicate code as documentation: every code example must be tested and functional, and version-specific information must be clearly marked rather than left implicit.

Given a feature to document, it produces scenario-based examples (a full worked case - context, numbered steps, an expected outcome, and a working code snippet), a task-oriented structure (a quick start reaching first success in under 5 minutes, common tasks covering roughly 80% of use cases, advanced usage for power users, and troubleshooting with specific anticipated fixes), API documentation in OpenAPI format (rate limits, typical response time, and a full request-body schema), and configuration documentation as a JSON reference (feature flags, cache TTL, result limits, and named relevance weightings). It also produces cross-functional artifacts: a stakeholder summary (business impact metrics, development effort in sprints, dependencies, success metrics, and named risks with mitigations) and a release-notes entry (what's new, a developer-facing code snippet for new parameters, and explicit breaking-changes and migration-required fields).

### Feature Name

### Overview
- **Purpose**: What problem does this solve?
- **Target Users**: Who benefits from this feature?
- **Key Benefits**: Primary value propositions

### How It Works
- **Core Functionality**: Technical behavior description
- **User Flow**: Step-by-step interaction patterns
- **System Integration**: How it connects with existing features

### Implementation
- **Technical Requirements**: Dependencies, versions, constraints
- **Configuration**: Setup and customization options
- **Code Examples**: Practical usage demonstrations

### Reference
- **Parameters**: Complete specification details
- **Error Handling**: Common issues and solutions
- **Performance**: Limitations, optimization tips

Documentation carries version-control metadata as frontmatter (version, last-updated date, reviewers, related features, a deprecated flag) and a running changelog categorizing each entry as Added, Improved, Fixed, or Deprecated, paired with a migration guide noting whether a version bump is breaking or fully opt-in.

Technical writers and engineers documenting features for mixed audiences, guided by a review checklist covering accuracy (all examples tested and functional), completeness (happy path, edge cases, and error scenarios), clarity for both technical and non-technical readers, maintenance (version-specific content clearly marked), and accessibility (proper heading structure, image alt text, clear link text) - plus discoverability practices like a real user-search-term keyword strategy, internal linking between related concepts, a table of contents, and searchable code identifiers.