Docify help

Skills that help AI coding agents create, edit, and review the documents engineering teams produce.

Install

npx -y skills add juff17/docify --skill docify-help

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Quick-reference card for the docify plugin — every skill it provides, what each one writes, and how publishing works. One-shot display, not a persistent mode. Use when the user asks how to use docify, what docify can do, what docify skills or commands exist, or invokes /docify-help.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, as published. Nobody here has run it

Docify Help

Display this reference card when invoked. One-shot: answer, then stop. Do NOT start writing a document, change any state, or persist anything — the user is asking what docify does, not asking you to run a skill.

docify teaches your agent to write, review, and maintain the documents engineering teams produce every day — and to publish them to your documentation providers instead of leaving them as loose Markdown.

Skills

Skill	Trigger	What it does
trd-write	"write a TRD", "plan this epic", "turn this PRD into a technical plan"	Create or update a Technical Requirements Document — the epic-level plan for how a PRD gets built, broken into buildable stages.
ticket-write	"write a ticket", "file this as a ticket", "update ticket ABC-123"	Create or update engineering tickets — user story → requirements → verifiable acceptance criteria.
readme-write	"write a README", "restructure this README", "document this project"	Create or restructure a project README, written for a developer seeing the project for the first time.
gitlink	"send me a link to these lines", "get a permalink to this code"	Build commit-pinned, shareable web permalinks to specific lines of code on GitHub or GitLab.
docify-help	`/docify-help`, "how do I use docify"	This card.

Skills trigger automatically from what you ask — just describe the document you want. You can also invoke one directly by name, e.g. /trd-write.

Publishing

trd-write and ticket-write publish for you. Each detects a connected MCP and writes there, falling back to a local Markdown file if none is connected:

TRDs → the connected doc-store MCP (Confluence, Notion, Google Docs, …).
Tickets → the connected issue-tracker MCP (Jira, Linear, GitHub, …).

Connect a provider's MCP and docify uses it; connect nothing and you get a Markdown file. You don't pick the provider by name — it's detected from what's connected, and you're asked once if several match.

Install & Update

/plugin marketplace add juff17/docify
/plugin install docify@docify

Send those as two separate prompts. On the desktop app (no /plugin command), install from the UI: Customize → the + by personal plugins → Create plugin and add marketplace → Add from repository → enter the repo URL.

To update: /plugin marketplace update docify, then /reload-plugins. If /plugin isn't recognized, update Claude Code (npm install -g @anthropic-ai/claude-code@latest, or brew upgrade claude-code) and restart.

Full docs: https://github.com/juff17/docify