Document Ops
Professional documents in one pass.
Five skills and one config. You describe a process; you get a document that looks like your organization made it on purpose. The brand-kit intake runs once and the other four read it, so you configure your logo, palette, and header style a single time and never answer for them again.
The buy button goes here on November 10. Until then, subscribe and you will hear when it opens.
Five components, one config.
Run-once. Captures logo, colors, fonts, header style into a config every other skill reads. The keystone.
brand: full intake · brand: check validate the installed kit, report only · brand: recheck <path> validate a specific brand.jsonAny process → a branded SOP with step cards, role color coding, alert and info boxes.
Any SOP or process doc → a one-page job aid.
Recurring-meeting agenda builder with a minutes-to-next-agenda flow.
Structured requirement and decision records for sign-off workflows.
reqdoc: at the start of a message, read as the change to document · or the descriptive phrases ("req doc", "document this change", "I need the doc for the business owner")Trigger strings and hard-fail lists are printed from the shipped skill files, not drafted for this page.
A brand kit in, a finished SOP out.
The kit the document on the right was built against, trimmed to the fields you can see on the page:
The accent started as the orange C25E28. White text on it measured 4.26:1, under the 4.5:1 contrast floor, so brand-kit darkened it to B45724 — 4.85:1, same hue — before any document was built.
The file manifest.
Every skill ships with its own setup-guide section and at least one worked example. That is not a bonus; it is half the build.
Requires: Node 18 or newer, and npm. brand-kit has no dependencies at all; the four document skills each depend on one package, docx. Nothing is hosted by me and there is no API key.
Tested on: Claude Code 2.1.239, and Claude on the web and desktop apps. Every skill is run end to end on each before it enters a pack. Older Claude Code versions are not tested, and nothing in these skills depends on a recent one — they install by dropping a folder into your skills directory, not through a marketplace.
Portable, untested: these are standard Agent Skills — a SKILL.md with name and description frontmatter plus supporting files — and Anthropic also supports that format on the Claude API and on Claude through AWS and Microsoft Foundry. Those surfaces are not tested here and are not covered by support. They will probably work. "Probably" is why they are listed separately.
If the format changes: a skill format change is an update, not a new purchase. See updates.
Is this just prompts in a folder?
No. Each skill has a deterministic trigger, hard-fails backed by checks that run before anything is written, and named exits at every scope boundary. The floor those are measured against is published at /standards/, including the parts of it that are unflattering. If a pack shipped here failed a gate, the gate would be the thing to fix, not the wording.
What do I need to run it?
A Claude plan that supports skills, either Claude Code or the Claude web or desktop app, and Node 18 or newer with npm — the four document skills build .docx files with the docx package, installed by running npm install once inside each skill folder — four times in practice, since brand-kit has no dependencies and reports nothing to do. Beyond that, nothing: no API key, no server, no subscription to anything of mine. Full statement at /policies/.
Do I have to use the brand-kit skill?
Yes, once. It is the keystone: it writes the config that the other four read. Skip it and every skill will ask you for your logo, palette, and header style every time. Running it takes a few minutes and you never do it again.
Can I change the skills after I buy them?
Yes. They are markdown and Python; edit them, fork them, strip the parts you do not want. You keep your modifications. What you cannot do is resell or redistribute them — see the license.
Can my team use it?
One purchase covers one person. For a team, a flat team license covers up to five people at one organization for $237 — three solo licenses. More than five, buy another team license; each covers five. Producing documents for a client is your own use; installing the skills for the client's people to run is the client's use. Sold as a separate listing from November 25, 2026. Details at /policies/#license.
What happens when Anthropic changes the skill format?
It gets fixed and the fix ships to you as an update at no cost, within the major version. Format churn is the expected weather for this product category, and handling it is a large part of what separates a maintained system from a folder someone uploaded once.
Why is this $79 when prompt packs are $9?
Because a prompt pack is text and this is a tested system with documentation, a published quality floor, and a maintenance commitment. If what you want is text, the $9 option is a real option and you should take it. The price is a signal, not a tax.
Can I get a refund?
Gumroad is the merchant of record and handles refunds under its own terms; I cannot issue one directly. If a pack does not work as documented, email hello@happypath.works first — I will either get it working or back your refund request. Details at /policies/.