How do I install the Document Feature skill?

Run npx skillmds@latest add whatifwedigdeeper/document-feature in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Document Feature skill do?

Generate technical and user documentation for a feature It is listed under Docs & Writing on SkillMD.

Is Document Feature safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Document Feature?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Document Feature free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Document Feature?

WhatIfWeDigDeeper (@whatifwedigdeeper) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Document Feature by whatifwedigdeeper

Name: Document Feature
Author: WhatIfWeDigDeeper

File contents

Document Feature: $ARGUMENTS

Generate comprehensive documentation for a feature in both developer and user-friendly formats.

Process

Phase 1: Feature Analysis

Identify feature type: Frontend, Backend, or Full-stack
Gather technical context: Files, types, dependencies, data flow
Analyze user interaction: UI elements, step-by-step journey

Search in: /components/, /app/, /lib/, /types/, /contexts/

Phase 2: Developer Documentation

Create: /docs/dev/$ARGUMENTS-implementation.md

IMPORTANT: Always use /docs/ folder (not repository root) for all documentation.

Required sections:

Overview and quick reference
Architecture (component structure, data flow, types)
Implementation details (core logic, state, events)
Code examples (basic and advanced)
Testing (coverage, manual checklist)
Integration guide (config, dependencies)
API reference (if applicable)
Maintenance (known issues, future work)

Phase 3: User Documentation

Create: /docs/user/how-to-$ARGUMENTS.md

Required sections:

Overview (what it does, benefits)
Getting started (prerequisites, access)
Step-by-step instructions with screenshot placeholders
Common use cases/scenarios
Tips and best practices (do's, don'ts, pro tips)
Troubleshooting (common problems + solutions)
FAQ
Related features

Phase 4: Screenshot List

Create: /docs/screenshots/$ARGUMENTS-screenshots-needed.txt

List all screenshots needed with:

Filename
What to show
What to highlight

Phase 5: Cross-References

Update main documentation index
Add links to related docs
Update CLAUDE.md if new patterns introduced

Naming Conventions

Type	Pattern	Example
Dev docs	`[feature]-implementation.md`	`dark-mode-implementation.md`
User docs	`how-to-[feature].md`	`how-to-dark-mode.md`
Screenshots	`[feature]-[context].png`	`dark-mode-toggle.png`

Quality Standards

Developer docs: Technically accurate, includes file paths and line numbers, proper terminology

User docs: Non-technical language, visual aids, clear actionable steps, scannable formatting

Output Checklist

Dev doc at correct path with all sections
User doc at correct path with all sections
Screenshot placeholder list generated
Code examples syntactically correct
Cross-references added
Technical accuracy verified against code

---name: document-featuredescription: Generate technical and user documentation for a feature---# Document Feature: $ARGUMENTSGenerate comprehensive documentation for a feature in both developer and user-friendly formats.## Process### Phase 1: Feature Analysis1. **Identify feature type**: Frontend, Backend, or Full-stack2. **Gather technical context**: Files, types, dependencies, data flow3. **Analyze user interaction**: UI elements, step-by-step journeySearch in: `/components/`, `/app/`, `/lib/`, `/types/`, `/contexts/`### Phase 2: Developer DocumentationCreate: `/docs/dev/$ARGUMENTS-implementation.md`**IMPORTANT**: Always use `/docs/` folder (not repository root) for all documentation.**Required sections:**1. Overview and quick reference2. Architecture (component structure, data flow, types)3. Implementation details (core logic, state, events)4. Code examples (basic and advanced)5. Testing (coverage, manual checklist)6. Integration guide (config, dependencies)7. API reference (if applicable)8. Maintenance (known issues, future work)### Phase 3: User DocumentationCreate: `/docs/user/how-to-$ARGUMENTS.md`**Required sections:**1. Overview (what it does, benefits)2. Getting started (prerequisites, access)3. Step-by-step instructions with screenshot placeholders4. Common use cases/scenarios5. Tips and best practices (do's, don'ts, pro tips)6. Troubleshooting (common problems + solutions)7. FAQ8. Related features### Phase 4: Screenshot ListCreate: `/docs/screenshots/$ARGUMENTS-screenshots-needed.txt`List all screenshots needed with:- Filename- What to show- What to highlight### Phase 5: Cross-References- Update main documentation index- Add links to related docs- Update CLAUDE.md if new patterns introduced## Naming Conventions| Type | Pattern | Example ||------|---------|---------|| Dev docs | `[feature]-implementation.md` | `dark-mode-implementation.md` || User docs | `how-to-[feature].md` | `how-to-dark-mode.md` || Screenshots | `[feature]-[context].png` | `dark-mode-toggle.png` |## Quality Standards**Developer docs**: Technically accurate, includes file paths and line numbers, proper terminology**User docs**: Non-technical language, visual aids, clear actionable steps, scannable formatting## Output Checklist- [ ] Dev doc at correct path with all sections- [ ] User doc at correct path with all sections- [ ] Screenshot placeholder list generated- [ ] Code examples syntactically correct- [ ] Cross-references added- [ ] Technical accuracy verified against code

Frequently asked questions

Document Feature