new-doc
Skill0 starsChanged 6 months agoMITView on GitHub
Scaffold a new documentation file (PRD / RFC / ADR / SPEC / TDD / AUDIT / POSTMORTEM / README) with the canonical frontmatter and section skeleton from docs/harness/doc-pattern.md.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- pero3dev/ai-agent-librarytheir own version, first seen Nov 4, 2026
- OffchainLabs/arbitrum-docstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- OffchainLabs/arbitrum-docs★ 252same name
- pero3dev/ai-agent-library★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-docs-semanticSkill
- audit-docsSkill
- audit-harness-coverageSkill
- budget-statusSkill
- cavemanSkill
- configurationSkill
- critic-reviewSkill
- doc-patternSkill
- error-taxonomySkill
- grill-meSkill
- grill-with-docsSkill
- python-failure-modesSkill
- review-changesSkill
- review-docSkill
- rust-failure-modesSkill
- verification-before-completionSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Pre-check: If the target file already exists, STOP.
- Very specific: line 45
Generate body: Use the section template for that type from docs/harness/doc-pattern.md §4.
- Very specific: line 47
Write the file: Create parent directories as needed (mkdir -p).
- Distinctive: line 62
Backfilling an RFC: after the decision is made — that is revisionism.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scaffold a new documentation file following the doc-pattern matrix in docs/harness/doc-pattern.md. Read that file first if you have not already — it is the source of truth for all doc-type structure rules; this skill only operationalizes it.
Argument format: /new-doc <type> <topic>
<type>: one ofPRD,RFC,ADR,SPEC,TDD,AUDIT,POSTMORTEM,README(case-insensitive).<topic>: short slug. Used for both the file path and (often) the doc title.
Steps when invoked
- Parse args. Normalize
<type>to uppercase. If the type is not one of the eight, list the valid types and stop. Determine path. Apply these defaults; ask the user if any rule is ambiguous in the current context. Default paths shown below; consuming repos may configure different conventions (e.g.,
docs/adr/for ADRs). The skill writes to the path your project has set up.Type Default path PRD docs/harness/components/<topic>/PRD.mdRFC docs/harness/components/<topic>/RFC.mdADR docs/decisions/<YYYY-MM-DD>-NNN-<topic-slug>.mdSPEC docs/harness/components/<topic>/SPEC.mdTDD docs/harness/components/<topic>/TDD.mdAUDIT .claude/audits/<YYYY-MM-DD>-<topic>.mdPOSTMORTEM docs/postmortems/<YYYY-MM-DD>-<topic>.mdREADME If <topic>names a directory, use<topic>/README.md. Else ask.For ADR specifically: scan
docs/decisions/for existing files, take the highestNNN, increment by one. Use today's UTC date.- Pre-check. If the target file already exists, STOP. Report the path and ask whether the user wants to overwrite (default: no).
- Generate frontmatter. Apply this template, filling in fields:
For ADR, also include empty--- type: <TYPE> status: draft owner: <git config user.email or 'unowned'> last-reviewed: <YYYY-MM-DD> ---supersedes:andsuperseded-by:keys. - Generate body. Use the section template for that type from
docs/harness/doc-pattern.md§4. Write the section headers with one-line placeholder beneath each — body text is for the user to fill in. - Write the file. Create parent directories as needed (
mkdir -p). - Report.
- Echo the created path.
- Show the first ~10 lines so the user can verify frontmatter.
- State next-step reminders, applicable to the type:
- All: "Add an index line to
CLAUDE.md(Principle 7 — Index Discipline)." - ADR: "If this supersedes an earlier ADR, set
supersedes:here and update the older ADR'ssuperseded-by:." - SPEC: "If the output of this spec is consumed by automation, plan an AUDIT trigger."
- POSTMORTEM: "Link from any related ticket / incident, then schedule the action items."
- All: "Add an index line to
Anti-patterns to avoid
- Creating a doc with no frontmatter — frontmatter is required per
doc-pattern.md§3. - Accepting a
<type>not in the canonical eight — push back and refer the user todoc-pattern.md§1. - Backfilling an RFC after the decision is made — that is revisionism. Tell the user to write an ADR instead and link the prior context informally.
- Creating a POSTMORTEM speculatively — only after an actual incident.
- Silently overwriting an existing file. Always pre-check.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

