document
Generate concise feature documentation from implemented changes. Use after completing a feature to capture what was built for future reference.
What this skill does
# Generate Feature Documentation
Generate concise markdown documentation from implemented changes.
## Variables
- `adw_id`: $1 - Workflow identifier (optional)
- `spec_path`: $2 - Path to original specification (optional)
## Purpose
Documentation answers: **"How does it work?"**
Generate reference documentation for implemented features that future agents and developers can use.
## Instructions
### 1. Analyze Changes
Understand what was implemented:
```bash
# See summary of changes
git diff origin/main --stat
# List changed files
git diff origin/main --name-only
# See detailed changes for significant files
git diff origin/main -- path/to/file
```
### 2. Read Specification (if provided)
If spec_path is provided:
- Understand original requirements
- Frame documentation around "what was requested vs what was built"
- Note any deviations or enhancements
### 3. Generate Documentation
Create documentation file: `docs/feature-{descriptive-name}.md`
## Documentation Format
```markdown
# [Feature Title]
**Date**: [Current date]
**Specification**: [spec_path or N/A]
## Overview
[2-3 sentence summary of what was built]
## What Was Built
- [Component/feature 1]
- [Component/feature 2]
- [Component/feature 3]
## Technical Implementation
### Files Modified
- `path/to/file.ts`: [Brief description of changes]
- `path/to/other.ts`: [Brief description of changes]
### Key Changes
- [Important implementation detail 1]
- [Important implementation detail 2]
## How to Use
1. [Step 1 for using the feature]
2. [Step 2 for using the feature]
## Configuration
[Environment variables, settings, or options if applicable]
## Testing
[How to test this feature]
## Notes
[Any additional context, known limitations, or future considerations]
```
### 4. Update Conditional Docs (if applicable)
If conditional documentation exists, add entry for new documentation:
```markdown
- docs/feature-{name}.md
- Conditions:
- When working with [feature area]
- When implementing [related functionality]
```
## Output
Return ONLY the path to the documentation file created:
```text
docs/feature-export-to-csv.md
```
## Best Practices
1. **Concise**: Documentation should be scannable
2. **Accurate**: Reflect what was actually built
3. **Actionable**: Include how to use the feature
4. **Current**: Keep it updated as features change
5. **Linked**: Reference related documentation
## Documentation as Feedback Loop
> "Documentation provides feedback on work done for future agents to reference in their work."
Good documentation enables:
- Future agents to understand the codebase
- Developers to onboard faster
- Consistent patterns to be followed
- Knowledge to persist across sessions
## Integration with Workflow
Documentation typically follows review:
```text
/plan → /implement → /test → /review → /document (THIS COMMAND)
```
Documentation is the final step that captures what was built.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.