feature-to-assetslisted

Turn one shipped feature into the full set of adoption assets that make it discoverable and usable — reference docs, a how-to guide, a runnable example, a changelog entry, an MCP tool definition, a troubleshooting entry, and the announcement copy. Reads the actual implementation so the output describes what the code does rather than what a ticket claimed. Drafts each asset and reports which ones the feature genuinely needs. Use after shipping a feature, when asked to document or announce a new capability, to produce launch or release content, or when a feature exists in code but nowhere else.
agentrel/skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill agentrel/skills

# Feature to assets A shipped feature that only exists in code is not adopted. This expands one feature into the artifacts each consumer surface needs, derived from the implementation rather than from a description of it. Unlike the other skills in this plugin, this one **writes files**. Everything is a draft, written to a staging directory, and nothing existing is overwritten. ## Applies to | | | |---|---| | **Project types** | Any product shipping user-facing features — APIs, SDKs, platforms, applications | | **Stage** | After merge, before announcement. This is a continuous-use skill rather than a one-off audit; run it per feature | | **Needs** | The diff, pull request, or implementation. It reads code, not tickets | | **Skip if** | The change is internal-only with no user-facing surface. It will detect this and write only a changelog entry | Most useful on features that introduce a new capability rather than adjust an existing one. A bug fix needs a changelog line, not twelve artifacts, and the skill will say so. ## How to use ``` /agentrel:feature-to-assets use the current branch's diff /agentrel:feature-to-assets "invoice scheduling" name the feature explicitly /agentrel:feature-to-assets #482 use a pull request ``` Writes drafts to `./feature-assets/<feature-slug>/`, one file per asset, and prints what it wrote and what it deliberately skipped. **This is the one skill that writes files.** It never writes into `docs/` or any